121 CRM playbook · Appointment confirmation

Confirm a genuine booking, set expectations and give the customer a clear change route.

A fictional survey practice confirms Mia’s visit with time, location, preparation and rescheduling details. This playbook turns that kind of situation into an owned sequence with explicit stop points, exceptions and measures. Use only channels, data and capabilities approved for your setup.

Subscribe to 121 CRM Seller, billing and cancellationRead the automation guide

Customer Thread

Appointment confirmation: the working sequence

Illustrative example

Verify the booking
Provide change options
Stop old messages
Human review

Verify the booking
Check customer, service, owner, time zone, location and status before communicating.
Provide change options
Explain how to reschedule, cancel or ask a question.
Stop old messages
Cancel pending communications when the booking changes.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow appointment confirmation from start to next action.

The coded interface shows an example sequence using fictional data and does not expose a live CRM account.

121

Northstar Joinery

Fictional

Make appointments easier to organise

OverviewContactsCalendarAppointmentsAutomation

Make appointments easier to organise

Coordinate availability, appointment status and the follow-up owner.

Mon

10:00

Discovery call

Rowan & Co

Tue

09:30

Site survey

Oakfield Homes

15:00

Drawing review

Marlow Works

Wed

Thu

11:30

Discovery call

Bramble Studio

Fri

13:00

Installation check

Field & Form

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

What supports the playbook

See what the CRM can coordinate — and where your team steps in.

The CRM can organise the sequence, but the business still sets the rules, checks consent and handles the moments that need human judgement.

Capability 01

Appointments

Stores scheduled customer interactions with time, attendee, owner, status and related contact context.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Makes booked work visible alongside the customer conversation and follow-up.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 02

Appointment reminders

Uses configured notifications or workflows around booking, rescheduling, cancellation and attendance events.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Keeps customers and staff informed without relying on a person to send each reminder manually.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 03

Email conversations

Sends and receives supported email messages against the customer conversation and contact record.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Keeps email context visible to authorised colleagues rather than one private mailbox.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 04

SMS and MMS

Uses a configured phone provider and compliant number to send and receive supported text and media messages.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Supports quick customer updates while preserving the thread in the CRM.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 05

Goals and exits

Moves or removes records when the configured outcome or stop condition has been met.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Helps avoid continuing follow-up after the customer has already acted.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Entry criteria

Begin with a valid trigger, enough context and one owner

A booking reaches the agreed confirmed status. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A booking reaches the agreed confirmed status.

Practical scenario

A fictional survey practice confirms Mia’s visit with time, location, preparation and rescheduling details.

Human decision retained

Accountable owner

Name the person or queue that accepts the work, monitors exceptions and can stop the sequence.

The sequence

Run the appointment confirmation playbook step by step

Each step should leave evidence a colleague can understand. Timing and channels should follow the customer context rather than a generic high-pressure cadence.

1. Verify the booking

Check customer, service, owner, time zone, location and status before communicating.

2. Send the confirmation

Use the chosen channel to state what is booked and what happens next.

3. Provide change options

Explain how to reschedule, cancel or ask a question.

4. Schedule proportionate reminders

Use timing appropriate to the appointment and customer preference.

Close the loop

5. Stop old messages

Cancel pending communications when the booking changes.

Owner, timing and exception

Make the operational state easy to review

The supporting view keeps the next action and human checkpoint visible around the automated steps.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Exception paths

Stop the normal route when the facts change

Exceptions are part of the process, not failures to be hidden. Route them to a person with the authority and context to decide what happens next.

Human review

Missing contact route

Create a staff task rather than silently assuming confirmation.

Human review

Resource or host conflict

Hold communication until a person resolves availability.

Human review

Sensitive appointment

Use approved wording and restrict unnecessary detail.

Operational review

Measure whether the work became safer and clearer

Use measures that reveal ownership, service quality and control. Counts of messages, tasks or workflow runs are supporting signals, not proof of customer value.

Confirmed bookings with successful communication

Review failures as work, not just a percentage.

Changes handled before the slot

Track whether the route helps customers act in time.

Wrong-time or duplicate messages

Treat any occurrence as a workflow defect.

Questions about this page

Useful answers, without the sales fog.

1. When should the appointment confirmation playbook start?

A booking reaches the agreed confirmed status. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action.

2. Which channels should the appointment confirmation playbook use?

Use only configured channels that suit the purpose, customer preference and consent position. Give each channel a distinct role and check provider availability and usage charges before launch.

3. When should appointment confirmation automation stop?

Stop when the purpose is complete, the customer responds or opts out, the data conflicts, or an exception needs judgement. In this playbook, pay particular attention to missing contact route, resource or host conflict, sensitive appointment.

4. How should we judge whether appointment confirmation works?

Review confirmed bookings with successful communication, changes handled before the slot, wrong-time or duplicate messages. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome.

Read all CRM questions

Continue the journey

Appointments Calendar management Appointment reminders Appointment no-show

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing