Piet BaudoinBy Piet Baudoin, updated September 26, 2026

How does the service reminder email for an annual inspection go out on time?

A service reminder email for an annual inspection starts with a deadline that is written down somewhere; your AI finds the customer details and the agreements Bombos keeps and gets the invitation ready for you to review and send.

Works with your own scheduling software, calendar and accounting package.

The maintenance cycle is the first task; contracts, receipts and history stay in one shared memory.

Book your half hour

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.

Now

Annual inspections and service visits get squeezed in and fall behind; revenue that was already there evaporates.

Today, the deadline sits in three places and no calendar: the contract, the receipt from the last visit and the head of the most experienced technician. If you use Jobber, recurring jobs from maintenance contracts are already scheduled there. The lookup work sits outside that schedule: which deadline applies to this customer, where is it recorded and what do you write to them?

Withbombos

The recorded maintenance appointment surfaces and the invitation is ready.

Well before the deadline, the invitation is ready. Your AI brings together the customer details and the maintenance agreements Bombos keeps, reads the documents you identify and prepares the text. The proposal shows which agreement was used and what the old receipt says about the previous visit. You review the text and deadline and send the invitation yourself. After your approval, if your AI has a connection to your schedule, it puts the visit there.

After three months

After three months, no inspection passes without the customer receiving an invitation. Bombos keeps the register and your office team approves each proposal. Service revenue that used to evaporate now comes in, and you see which contract or receipt each invitation rests on.

What's ready for you then

  • No service visit quietly passes its deadline
  • The invitation is ready well before the deadline
  • Contracts, receipts and history in one proposal
  • Revenue from customers you already have

Where do you see that?

On the list of proposals, the invitation sits with the customer details and the appointments found. The reason shows which recorded agreement is behind this maintenance invitation. You read the deadline next to that agreement and adjust the draft message for this customer. The deadline and the proposed visit time sit separately at the proposal, so you can see which agreement was used for the text. Your contracts do not have to be open beside it.

At "ready for you", the text is waiting for review. "Waiting on your input" means your AI is asking, for example, which agreement should lead when the documents contradict each other. That question sits with the maintenance visit it is about. With every proposal you see where it came from.

How does it start?

It starts with your contracts and old maintenance receipts, in a conversation of about an hour in the first week. We look at where contracts and receipts are kept, which inbox belongs to maintenance and which package holds the appointments. You decide which recorded deadline applies. We go through a maintenance agreement to see which details you need for the invitation.

Your AI then starts the lookup and preparation work with proposals. You keep your own scheduling package and your existing documents, nothing moves and no training is needed; we fill in the settings together. If you correct the agreement used or the wording of an invitation, that correction is the rule from then on. Bombos keeps those corrections as the rules for which maintenance agreement belongs in the invitation. 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 a message to a customer even then; you set that in the AI or agent itself.

The maintenance rhythm is 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. We would rather you did not keep coming back to us. After three months, no inspection goes by without the customer being invited.

More from your customers, from one shared memory.

Inviting customers for maintenance is work nobody misses until something goes wrong. The knowledge it needs sits in contracts, old receipts and people's heads.

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

  1. 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.

  2. 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.

  3. 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.

Which maintenance deadline applies is for you to decide; your AI does not read that out of an unclear contract today. An old visit does not yet say when the next one is due. If the technician keeps to a different interval from experience than the contract gives, that is written down nowhere. That is why your AI asks you once which interval he keeps to, and after your review Bombos keeps the answer for the next proposal. If a visit is already in your package from the contract, an invitation proposal is no reason to schedule that same visit again.

A detail that was found can be misread or incomplete. When in doubt, your AI puts the question to you instead of guessing a deadline, and the proposal needs your check before it goes into the schedule. You approve before an invitation goes to a customer, on every channel. You set that in the AI or agent itself. The next maintenance visit starts with an agreement you can find again.

The first half hour · free

What does your AI forget?

  1. 01You tell us which AI you use and where it keeps starting over.
  2. 02We show what a shared memory changes there, on your own examples.
  3. 03You keep the plan, with or without Bombos.
Piet Baudoin
Piet BaudoinYou talk to Piet, from the Bombos teamDutch team from Utrecht and Nijmegen · data in Europe
We reply the same working day.