How do you rebuild the schedule for twelve technicians after a sick call at 6:58, with the messages to customers ready alongside it?
After a sick call at 6:58, your AI reads the logged call, finds the affected appointments and gets an adjusted day plan with customer messages ready; you decide on the schedule and send them.
Works with your own scheduling software, calendar and accounting package.
The 6:58 sick call is where it starts; skills, schedules and agreements stay in one shared memory for every AI your team uses.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
This is how it goes now, and how it goes with Bombos.
One phone call and the whole day has to change: who takes over the jobs, which customer needs a call, and the paperwork falls behind in the meantime.
At 6:58 am, a technician calls in sick and you have twelve scheduled. You record who is missing, open the day plan, find their jobs and decide which coworker can take over. If the call only exists as a phone conversation, you first write down the consequences. For every rescheduled appointment, you find a new time and prepare a matching customer message.
The adjusted plan for the day is ready, with messages to the customers it affects.
Your AI reads the sick call as soon as it is available as text and pulls in the affected appointments and customer details. It prepares a revised day plan, with the reason for each change. Draft messages for affected customers sit beside the proposed changes. You decide what goes ahead and send the messages. After your approval, if your AI has a connection to your schedule, it puts the proposal there.
After three months, your schedule is ready each morning instead of being built from scratch, even when someone calls in sick. Your dispatcher reviews a proposal instead of solving a puzzle, and customers hear about changes in time. The time this frees up goes to work that currently gets left behind. You see where every proposal came from.
What's ready for you then
- The new day plan is ready before the crew leaves
- Who takes over, based on schedules, skills and travel distance
- Every affected customer has a message ready
- Your dispatcher no longer starts the day firefighting
Where do you see that?
The day plan sits on the same list as the customer messages that go with it. You see which appointments are affected by the sick call and why a change is proposed. You read the affected jobs next to the suggested replacement and adjust the division. The draft message at the moved appointment shows what you are putting to the customer. The appointment details that were found stay with the work you are reviewing.
A proposal with the status "ready for you" is waiting for your review. "Waiting on your input" means there is an open question, for example which appointment is allowed to move. That status belongs to the day plan you are looking at right now. With every proposal you see where it came from. The customer messages sit clearly marked as drafts next to the proposed changes for that day.
How does it start?
For the first task we discuss how an absence report reaches the schedule. In the setup conversation in the first week we spend about an hour looking together at the inbox, the logged reports and the scheduling software. You tell us which appointments are allowed to move and who reviews the consequences for customers. If the report comes in by phone, we agree where you write it down so Bombos can keep it.
After that, the first task starts with proposals. Your AI puts the proposed changes in front of whoever knows the crew and the day plan. Your own schedule stays in use, nothing moves and you do not need training. If you correct the choice at an appointment, that correction becomes the rule for a similar report next time. Once a task type has gone well for a while, you decide how much autonomy you give your AI, with Bombos as the memory underneath. You approve final scheduling and customer contact; you set that in the AI or agent itself. The next time a sick call is logged, the adjusted day plan is ready for review.
Sick calls are the first task, not the whole offer. We take you along on that first step, and after that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed. After three months, your schedule is ready in the morning instead of you having to put it together.
Fewer fires, one shared memory.
A sick call shows how tight your schedule is. The faster you grow, the more often one phone call turns the whole day upside down, and the knowledge needed to fix it sits in your dispatcher's head.
Bombos is the memory layer under the AI your team already uses: Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents. One plugin gives them all one shared memory: your team's knowledge, the rules it learns from your corrections, and what is already in your email, documents and business software.
You see where every answer came from. Bombos runs in the cloud or standalone on your own server, and one person can try the plugin with their own agents first.
The pilot runs three months for €2,000 instead of €3,000, then €1,000 per month, excl. VAT. Book your half hour to talk through your situation.
What Bombos does, in three steps
It reads what comes in
An email, a message, a photo or a PDF: your AI reads it, finds the client and the details through Bombos in the systems you already have, and sees what is missing.
It drafts the work, you approve it
The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.
It remembers what you decide
Every correction becomes the rule for next time. Once it has gone well for a while, you give your AI more autonomy step by step, with Bombos as the memory underneath.
What does Bombos not do here?
Bombos does not act here itself: it gives your AI the memory. Without a connection between your AI and your scheduling software, it stays a proposal.
A sick call does not come with a guarantee that every job that day still happens. Bombos only knows the appointments, details and rules that are available. A verbal promise from a technician that is written down nowhere cannot be included in the proposal. That is why your AI asks you once who can take over which work during an absence, and Bombos keeps the answer, so that shows up in the proposal next time. Which customer has to wait is your decision. The day plan can be wrong or incomplete; the consequences need checking before the schedule changes.
When uncertain, your AI puts the choice in front of you. You approve before messages go to customers or other third parties, on every channel, even during a sick call. You set that in the AI or agent itself. An approved day plan is also not proof that a customer has accepted the new time. Rebuilding the day is about the appointments that shift, including for the people waiting on a technician.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
