- 01
Market
Saudi Arabia
- 02
Written for
COO, Head of CX
- 03
Decision
Automate appointment booking over the phone
- 04
Languages
EN · AR
The booking
Six steps, and a hold in the middle
The hold is what separates a booking agent from a form that speaks. Without it, two callers are offered the same slot and one of them arrives to nothing.
A booking flow: identify the caller, establish the service, offer availability, hold the slot, confirm and write, keep the thread — with handover to a person for anything unusual.
- 01
Identify the caller
Matched against the record by phone number, then confirmed by one detail. New callers are created rather than forced into an existing record.
- 02
Establish what they need
Service type and duration, because those decide which slots are even offerable. Getting this wrong produces a booking that has to be moved.
- 03
Offer real availability
Two or three options rather than a list, read in the way people say dates — "Tuesday morning" before "the fourteenth at nine".
- 04
Hold the slot
A short lock while the caller decides, released automatically if they do not confirm. This is the step most implementations skip and the one that keeps the diary honest.
- 05
Confirm and write
Read back in full, written to the calendar of record, and confirmed by message on the number that called.
- 06
Keep the thread
Reminders, reschedules and cancellations run on the same identity, so a change never creates a second appointment beside the first.
To a person
Anything unusual — a clinical question, an eligibility or payment question, a caller who needs a slot that does not exist — goes to a human with the conversation attached. The agent does not negotiate exceptions.
Where diaries break
Four failures that are integration, not language
- 01
Two callers, one slot
Without a hold, availability read at the start of a conversation can be gone by the end of it. The fix is a lock with a timeout, and it has to exist in the calendar system rather than in the agent.
- 02
Relative dates
"After the weekend", "next month", "the day after Eid" — all ordinary phrasing, all requiring a calendar the agent can reason against, including the local working week and public holidays.
- 03
The record that does not match
A caller in the system three times under three spellings gets a booking on the wrong record, and the reminder goes to a number they no longer use. Deduplication is booking work, not data hygiene work.
- 04
Cancellations that never arrive
If cancelling is harder than not turning up, people do not cancel. An agent that handles cancellation on the same thread as booking recovers slots that would otherwise be lost, which is usually where the commercial case sits.
Measurement
Count the slots recovered, not the calls handled
Call volume handled is the easiest number to produce and the least useful. A deployment that answers every call and books nothing has automated a queue, not a business process. The numbers worth instrumenting from day one are bookings completed without a person, slots recovered through cancellation, and the proportion of calls that reach handover.
The handover rate is the one to watch rather than to minimise. A rate that falls while satisfaction falls with it means the agent is completing conversations it should have escaped. Reading the two together is the only way to tell a good deployment from a stubborn one.
Our role
What we build, and against what
- 01
Integration with the calendar of record
Whatever the practice management or scheduling system is, the booking is written there rather than to a copy that has to be reconciled later.
- 02
Slot rules as they actually are
Duration by service, buffers, who can see whom, the slots kept back for urgent cases — encoded from your rules rather than from a default the vendor shipped.
- 03
A tested cancellation path
Built at the same time as booking, because it is where the recovered revenue is and it is routinely left for a later phase that never arrives.
Clinical, eligibility and payment decisions stay with your own people and the agent routes to them; what we own is that the diary the organisation runs on stays accurate.
Common questions
What buyers ask
Can it work with our existing scheduling system?+
If the system exposes an API for availability and booking, yes, and that is the normal case. Where it does not, the honest options are a supported integration path from the vendor or a change of system; screen automation against a scheduling interface is fragile in a way that shows up as double bookings rather than as errors.
What about patients or customers who prefer a person?+
They ask, and they get one. A stated preference is a handover trigger, not something to talk somebody out of. In practice the proportion who ask drops once the agent demonstrably books correctly, but the option has to remain unconditional for it to be trusted.
Does it reduce no-shows?+
Reminders and easy cancellation both help, and we will not quote a figure for your practice before running it. What we can say is where the mechanism is: a caller who can cancel in fifteen seconds on the same channel they booked on frequently does, and every cancellation is a slot that can be refilled.
In this cluster
Map it to your booking system
A booking agent running against a test calendar with your own slot rules, before it is pointed at the live diary.
Start the conversation
