Piet BaudoinBy Piet Baudoin, updated September 26, 2026

Outlook appointment scheduling: how do you settle a time in one email?

Outlook appointment scheduling usually takes three rounds of email; your AI puts three times that are actually free in one proposal, travel time included, and after your approval the invitation goes out.

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

One email instead of three is the first step; travel times and customer preferences 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

Three rounds of email back and forth to plan a single appointment.

The customer emails when they will be home, and you already know it will take two more messages. You look up the address, read the surrounding appointments and work out how much time is left for the visit. Outlook does not calculate travel time between addresses, so you factor that in separately. If you wait until after the customer chooses, the back and forth starts again.

Withbombos

The appointment proposal is ready with travel time included; after your approval, the invitation goes out.

You start with a visit proposal that includes travel time. Your AI reads the email and finds the customer and calendar details, along with the recorded travel-time information. The proposal explains why that time was chosen and shows the surrounding appointments. A draft email offers that time to the customer. You check that the visit and journey fit the day and send it. After your approval, if your AI has a connection to your schedule, it puts the appointment there.

After three months

After three months, scheduling an appointment takes one email with a time that truly fits. Your dispatcher no longer puzzles over calendars and travel time, but reviews a proposal. The route works because travel time is part of the proposal, and every correction has become a rule.

What's ready for you then

  • One email with a time that truly fits
  • Travel time included, no puzzle of addresses
  • Appointments confirmed sooner, without three email rounds
  • Your dispatcher keeps time for harder work

Where do you see that?

The appointment proposal sits on the list with the customer email as its reason. You read the appointments from Outlook next to the visit address that was found and the recorded travel time, and adjust the proposed time. The reason next to the proposal shows which details were used for that choice. The draft email sits alongside it, so you can compare the time in the message with the appointment you are reviewing.

With "ready for you", the list shows that the proposal can be reviewed. "Waiting on your input" makes clear that information is still needed, such as how much time you want to allow for the drive. That question sits with the visit it concerns. With every proposal you see where it came from.

How does it start?

In the first week we set up preparing technician visits together. We take about an hour for that. Which inbox holds the requests, which calendar can your AI read, and where is the visit address? We also look at which travel time details are available and how much room you want to allow when scheduling. That way the task starts with details and rules you actually use for an appointment.

Your AI then starts the first task with proposals. You keep Outlook and your own schedule, without moving appointments or needing training. If you adjust a proposal because a certain appointment gets scheduled differently, that correction becomes the rule for 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 a final appointment and the email to the customer before they go out; you set that in the AI or agent itself. The next time you plan a visit in that same area, the proposal is ready for review with the travel time you agreed on back then.

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

Less email, one shared memory.

Three rounds of email for one appointment may seem small. Add them up across a week and your whole office team, and you can see what is holding back growth.

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 Outlook, it stays a proposal.

For this appointment proposal, your AI uses the information you make available. If the travel time is missing, you have to judge the drive yourself first. The proposal also cannot take into account an appointment that appears nowhere in the available calendar or email. An appointment like that exists only in your head, or in the head of the technician. That is why your AI asks you once about that appointment and its travel time, and Bombos keeps the answer, so the proposal can take it into account next time.

An email with a proposal does not guarantee that the customer accepts the time or that no further back and forth is needed. You approve before a message goes to a third party, whatever the channel, including a visit proposal. You set that in the AI or agent itself. When in doubt, your AI asks for information. A ready proposal can contain mistakes in the address, the time and the room allowed for the visit; those details need checking before the appointment goes ahead. A workable visit time starts with the whole drive the technician has to make.

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.