10 Chatbot Scripts for Appointment Confirmation

A reminder several days ahead catches clients who booked long in advance and forgot entirely.

4. The week-ahead reminder

Reminder: [service] with [practitioner] on [day, date] at [time]. Still works? If not, easiest to change it now while there's availability.

Options: Still coming · Change · Cancel. Framing early change as easier is what prompts action.

5. The preparation reminder

Your [service] is on [date]. Before then you'll need to [preparation], which takes about [duration]. Anything unclear, just ask.

Timed so the client has enough time to actually complete the preparation, which the confirmation alone rarely achieves.

6. The series reminder

Next in your [course] is [day, date] at [time]. That's [number] of [total]. Still suits?

Showing progress through a series improves completion, which matters clinically and commercially.

The payment or documentation reminder

Before [date], we need [payment or document]. Takes a couple of minutes and means nothing holds up your appointment.

Separating this from the confirmation means it arrives when there is time to act rather than being forgotten at booking.

The day-before message is the single highest-value one, because it converts uncertain bookings into either confirmations or freed slots.

7. The reconfirmation

Tomorrow: [service] at [time] with [practitioner] at [location]. Just tap to confirm, or change it if something's come up.

Options: Confirm · Reschedule · Cancel. The one-tap confirm is what produces the high response rate.

8. The reconfirmation with detail

Tomorrow at [time]. Bring [items], allow [duration], and parking is [detail]. Tap to confirm you're coming.

Repeating the practical details here matters, since the original confirmation was read once and forgotten.

Why making cancellation easy works

A client who cannot easily cancel simply does not attend, which loses the slot entirely rather than freeing it.

One-tap cancellation is counterintuitive and consistently produces better outcomes than making it difficult.

An unconfirmed appointment is a risk, and how it is handled determines whether the slot is recovered.

9. The follow-up nudge

Haven't heard back about tomorrow's [service] at [time]. Still coming? If I don't hear by [time] I'll assume not and free the slot.

Stating the consequence is what converts non-response into a response, and it should then be honoured.

10. The release notice

I've released tomorrow's slot since I didn't hear back. Happy to rebook whenever suits — here's what's available: [options].

Framing it as rebookable rather than as a penalty keeps the relationship intact.

Deciding whether to release

Releasing unconfirmed slots only makes sense where there is demand to fill them, and it damages relationships where there is not.

This should be a deliberate policy rather than a default behaviour, and clients should know it applies.

A cancellation is only neutral if the slot gets refilled, which depends entirely on speed.

The waitlist offer

A slot's just opened for [day, date] at [time] with [practitioner]. First to reply gets it.

Sent to waitlisted clients whose preferences match, which frequently refills within minutes.

The bring-forward offer

Your [service] is booked for [date], but [earlier date] has just opened if you'd rather come sooner.

Clients booked further out are frequently glad to move earlier, and this fills slots the waitlist cannot.

Timing the outreach

A slot freed the day before needs immediate outreach, since the window to fill it is measured in hours rather than days.

Automating this is the only realistic approach, as it depends on speed rather than on anyone noticing.

Confirmation messages drift long as teams add detail, and length reduces the chance the important parts are read.

The essentials

Date, time, location, practitioner and duration are the five things every confirmation needs, plus a reference and an action route.

Anything else should earn its place by preventing a contact that would otherwise arrive.

What belongs in a separate message

Preparation instructions, joining links and lengthy policy statements all work better as their own timed message than appended to the confirmation.

This also lets each be sent at the point it becomes relevant rather than all at booking.

Avoiding policy dumps

Cancellation terms, late arrival policy and payment conditions in a confirmation make it long enough that the date and time get skimmed past.

Summarise in a clause and link the detail rather than including it.

Naming the practitioner

Including who the appointment is with reduces anxiety for first visits and matters considerably for returning clients with a preference.

Where cover is arranged, telling the client proactively prevents a poor experience on arrival.

Chatboq sends confirmations and reminders from the scheduling system with one-tap confirm, reschedule and cancel actions.

Driven by the schedule

Messages fire from the actual appointment record, so a rescheduled booking cancels the old sequence and starts a new one automatically.

Reminders arriving for a cancelled appointment are a common failure that this removes entirely.

Actions rather than notifications

Confirm, reschedule and cancel are one tap and take effect immediately in the schedule rather than creating a request for someone to process.

This is what makes easy cancellation practical, since a request-based cancellation is not actually easy.

Waitlist outreach on release

A cancellation triggers immediate outreach to matching waitlisted clients, which converts a lost slot into a refilled one.

Track confirmation response rate, no-show rate and slots refilled, since these three together show whether the sequence is working.

Choosing the channel

Confirmations suit email for the record and reminders suit a faster channel, since the two serve different purposes.

Honouring a stated channel preference matters here, as appointment messages are among the most useful a business sends.