AI appointment confirmation calls: script, timing and fallbacks

Updated 2026-09-19 · 5 min read · By the Convo360 team

Why confirmation calls beat silent no-shows

A no-show costs more than the missed slot, it's a slot nobody else could take either. Sending one reminder message often isn't enough because messages get missed in a busy day. A short confirmation call adds a second, more attention-grabbing touchpoint, and unlike a message, it gets an answer in real time: confirmed, rescheduled or cancelled, rather than an unread tick.

This matters most for clinics, salons, coaching sessions and service visits, where a no-show also wastes a professional's blocked time, not just a missed sale.

The gap between 'message sent' and 'seat filled' is where most no-shows hide. A WhatsApp reminder tells you the message was delivered, it doesn't tell you whether the customer still intends to come. A confirmation call closes that gap by asking directly, which is why clinics and salons that add a call the day before often see fewer last-minute empty slots than those relying on a message alone.

The script that keeps calls short

Keep the script short and predictable.

1. Greet and identify: 'Hi, this is Convo360 Clinic calling to confirm your appointment.'
2. State the details, date, time and with whom, in one sentence.
3. Ask for a clear action: 'Press 1 to confirm, 2 to reschedule, or 3 to cancel,' or simply 'Would you like to confirm, or do you need a different time?'
4. Branch based on the answer, and close in under 10 seconds: 'Great, you're confirmed for tomorrow at 4 PM. See you then.'

Avoid adding information the caller didn't ask for, directions, parking, offers, keep the call to its one job. If they have a question, hand off with a transfer block rather than trying to answer everything on the confirmation call itself.

Speech vs DTMF, and the reschedule branch

Offer both ways to respond. Older or less tech-comfortable callers often find pressing a key easier than speaking to an AI; others find it natural to just say 'yes' or 'can we move it'. A DTMF menu block handles the keypad path, while a gather block with intent recognition handles the spoken path, run them together so either works.

The reschedule branch is the one businesses forget. If someone says 'not free tomorrow', don't just log 'cancelled', ask 'What day would work better?' and offer two or three real slots pulled from your calendar via an HTTP/API request or a connected sheet. A clean reschedule keeps the customer instead of losing them entirely.

Cancellations deserve one more question before the call ends: 'Would you like us to call you when a slot opens up sooner?'. Not every cancelling customer wants this, but the ones who say yes give you a warm lead for filling the very slot you just lost.

Building the flow on Convo360

To build this in the Flow Builder:

1. Trigger the flow from an inbound call trigger for callbacks, or launch it as an outbound campaign a day before each appointment.
2. Use a play audio or spoken block to state the appointment details, pulling the date, time and name from variables.
3. Add a DTMF menu alongside a gather block so callers can press a key or just speak their answer.
4. Add a Condition block to branch on the response: confirm, reschedule or cancel.
5. For reschedule, use an HTTP/API request to fetch open slots, or a Google Sheets lookup if your calendar lives there.
6. Log the final outcome with Save CRM lead or a Google Sheets row, and set a Send Template WhatsApp confirmation as a written record.

See the appointments docs and Flow Builder docs for block-level detail.

What to do when nobody picks up

Not every call gets answered. Rather than dialling again and again, which can read as intrusive and wastes minutes, fall back to a WhatsApp Send Template message with the same confirm or reschedule options as buttons. This respects the customer's time and still gets you a response later in the day.

Set a simple rule: one call attempt, then a WhatsApp fallback if unanswered, then a front-desk flag if there's still no response by a set cut-off before the visit. This mirrors the escalation pattern in outbound calls vs WhatsApp follow-ups, just running the other direction here since it's tied to a fixed appointment time.

Keep an eye on how often the fallback fires. If a large share of confirmation calls go unanswered on a particular time slot, say early morning, that's often a scheduling insight worth acting on, not just a messaging problem.

Timing the call and measuring results

One call the day before catches most people, but a second short call two to three hours before a same-day slot, clinics and salons especially, catches the last-minute cancellations a single reminder misses. Two calls sound like more effort than one, but both are automated campaigns, so the extra touch costs staff time only when someone actually needs to reschedule.

Track three numbers weekly rather than guessing whether the calls are worth running: the percentage of calls answered, the percentage of answered calls that confirm versus reschedule versus cancel, and the no-show rate for confirmed appointments compared with unconfirmed ones. If confirmed appointments still no-show at a similar rate to unconfirmed ones, the script or timing needs adjusting, not just the channel.

Review these numbers from Analytics and the Flow Logs for the confirmation flow once a week during the first month, then monthly once the pattern settles. A sudden jump in unanswered calls on one weekday, for instance, often points to a bad time-of-day choice rather than a script problem.

Step by step

1. Trigger the confirmation callLaunch a campaign a day before each appointment, or trigger from a booking event.
2. State the appointment in one lineSay the date, time and provider name clearly and briefly.
3. Offer DTMF and spoken confirmationAdd a DTMF menu alongside a gather block so callers can press a key or speak their answer.
4. Branch on the responseUse a Condition block to route to confirm, reschedule or cancel.
5. Handle reschedule with real slotsPull open slots via an HTTP/API request or Google Sheets and offer two or three options.
6. Fall back to WhatsApp if unansweredSend a template message with the same options instead of repeat-dialling.
7. Log the outcomeSave the result to your CRM or Google Sheets, and send a written WhatsApp confirmation.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.