An AI agent for appointment booking

A form collects requests. An agent books.

Most companies of this size already have a booking form, and most are disappointed by it. The reason is structural: a form produces a request, and a request still needs a person to check the calendar, confirm, and email back. The customer experiences that gap as the booking process.

The measurement that matters is the gap itself — from request arriving to slot confirmed. Before automating anything, look it up for last month. It is usually several hours, and overnight requests routinely wait until the next working day.

What the agent does

• Reads live availability from the calendar that actually holds it, including the blocks people put in for travel and admin.
• Offers slots and confirms one inside the same conversation, by phone, chat or email.
• Handles the reschedule when someone replies that Tuesday no longer works, rather than leaving the message for a human to read.
• Fills gaps from cancellations. A slot freed at short notice gets offered to whoever is waiting, within seconds.

That last one is worth pausing on. Nobody does it manually — not because it is hard, but because by the time a person notices the cancellation, the slot has already passed. It is the clearest example of an agent doing work that was never being done rather than work someone is doing today.

Where it gets difficult

Multi-resource scheduling. One person and one calendar is straightforward. A specific specialist plus a room plus a piece of equipment, each with its own availability rules, is a scheduling problem rather than a conversation problem. It can be solved, but it is not the process to start with, and anyone quoting it as trivial has not built one.

Availability that is not in the calendar. If the real answer to “can we fit them in Thursday” lives in a colleague’s head or a paper book, the agent will confirm slots that do not exist. Fix that first; it is often the more valuable half of the project and costs nothing but a decision.

Appointments that need qualifying. Some businesses should not book every request — the enquiry has to be assessed first. In that case the booking agent belongs behind qualification, not in front of it.

What it connects to

The calendar, with write access, is non-negotiable. Read-only access produces an agent that can suggest but not confirm, which reintroduces exactly the gap the project was meant to close.

The CRM matters if appointments belong to customer records. The phone system matters if requests arrive by phone, which for most businesses of this size is still where the majority come from.

How to tell whether it worked

• Time from request to confirmed slot, before and after.
• Share of bookings made outside office hours.
• Double bookings and manual corrections per week.
• Cancelled slots that were refilled rather than lost.

The last one is the number most companies have never measured, and often the one that pays for the build.