Service call in, proposal ready

After three months, not only is your schedule ready each morning. Your whole team works more efficiently, that is our promise. We start with your service calls: your AI checks your Outlook calendar and Jobber, with what Bombos remembers about your technicians, suggests who should go, and you approve.

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 →

Rob messages that his boiler keeps cutting out. The AI proposes a technician and a time with what Bombos remembers; Puck corrects the time once.

Who Schedules This Service Call, and When?

Right now the scheduler does that, as soon as he reads the email. No hot water, and the client is asking if someone can come by today. Your technicians are out on the road and you have another client on the phone, so the service call sits still until someone opens that email. An email is not yet a scheduled visit. First you work out which unit is involved, who knows that boiler and whose schedule still has room. Your scheduling needs those details before you can offer the client a time.

Doesn't Jobber Already Handle This?

Online booking in Jobber handles the requests where the client picks a time slot himself. A request from the client hub can be converted into a quote or a job, and maintenance that is already under contract can run as a recurring job with repeating visits. The client in this email just hasn't picked a time slot; he is simply asking whether you can come. The step from that loose question to a proposal for your schedule is the work your AI prepares, with what Bombos remembers about your clients and units. Your own schedule stays the place where the approved visit ends up.

Using different software? Bombos gives your AI what is in the software you already have, for example:

What Is Ready Before You Do Anything?

A proposal for the visit, with the reason attached. Your AI reads the email, looks up the client and the unit and checks the technicians and their schedules: this technician knows this type of boiler and has room after his scheduled job. The draft message to the client sits underneath, with the proposed appointment.

You read the reason and see that the suggested technician has room, but you pick the colleague who already knows this unit. You pass that choice along: for this client, suggest the regular technician first. Bombos keeps that correction as the rule for next time. That is how your AI learns to schedule the way your scheduler does. Service calls are the first task, and every correction stays in the team's shared memory.

If the key address is missing, the proposal carries the question of who lets the technician in. So in one list you see what is still needed for this visit, next to the unit details that were found and the message to the client. You review that message and approve the appointment. After that, if your AI has a connection to your schedule, it puts the visit there and sends the message to the client. You never had to open your scheduling software for this.

What Else Can Your Team Do Next?

Service calls are where it starts. An HVAC company has plenty of similar work: scheduling maintenance, closing a work order, preparing a quote. Someone finds the details and prepares the next step in Jobber. All of it leans on the same knowledge about your clients, your agreements and how you work.

Bombos is the memory layer under the AI your team already uses. Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents all draw on 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.

It runs in the cloud or standalone on your own server. One person can try the plugin with their own agents first, before the whole team joins.

How Do You Start, and What Does It Cost?

In the first week we sit with you and watch where service calls come in. We take a report, from the email or as a logged phone note or a message. Where is the unit? Which technician do you send? Your AI asks about the agreements it needs to build a proposal, and Bombos keeps what only you know, such as who the regular technician is. We write that down. You do not get a new software package on top of what you have.

First the service calls. Every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed. On the same unit a proposal is waiting later on: there are earlier service calls on record, do you want a checkup added to the next maintenance visit? The pilot runs three months for €3,000 €2,000, after that it is €1,000 a month, excl. VAT.

Price as of .

What Doesn't Go Out Without Your Approval?

You approve before anything is scheduled for good or a message goes to the client, even for a regular client; you set that in the AI or agent itself. A proposal can be wrong; when something is unclear your AI asks for the missing information, and Bombos keeps the answer. If the email turns out to be a quote request, no price goes to the client without your approval: you decide what you offer that client. The hours you get back are in the legwork between the report and the visit.

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.