Guide · Appointment reminders

Design reminders around clarity, choice and a workable exception route.

A reminder should help the customer prepare, confirm or change an appointment. The right channels and timing depend on the service, customer expectation, sensitivity, operating hours and connected calendar.

Subscribe to 121 CRM Seller, billing and cancellationExplore appointment workflows

Customer Thread

A reminder journey that can change course

Illustrative example

Book
Remind
Reply
Resolve
Record

Book
Details confirmed
Remind
Approved message
Reply
Customer context changes
Resolve
Person handles exception
Human decision
Record
Outcome visible

121 practical guidance. No universal schedule or reduction in missed appointments is claimed.

Reminder journey

Connect the appointment to confirmation, change and exception handling.

The booking view demonstrates state changes without prescribing a universal reminder schedule.

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.

CRM building blocks

Connect the advice to day-to-day CRM work.

These are the practical tools behind the guide, with enough context to decide where they can help and where people still need to take responsibility.

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

External calendar sync

Connects supported external calendars for availability and event synchronisation, with behaviour varying by calendar type.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Reduces double booking when the connection and conflict rules are correctly configured.
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 04

Workflow builder

Combines a start event with an ordered sequence of configurable actions.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Turns a repeatable customer process into a visible, reviewable flow.
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.

Capability 05

Messaging and calling compliance

Requires number verification, applicable registrations, consent, sender identity and opt-out handling for each channel and region.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes channel setup a governed operational task rather than just a technical connection.
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.

Start with the appointment

Make the source, status and authoritative calendar clear.

Reminders cannot be reliable if availability, time zone, location, service or cancellation state is ambiguous.

Authoritative booking

Name the calendar or practice system that controls date, time, duration, team member and status.

Accurate details

Include only the information the customer needs, with a clear way to check or change the appointment.

Identity and sensitivity

Use proportionate identity checks and avoid exposing sensitive service detail in an inappropriate channel.

Choose timing and channel

Use the customer journey, not a copied reminder sequence.

A same-day service and an appointment booked months ahead need different communication patterns.

Purposeful timing

Choose each reminder because it gives the customer a useful opportunity to prepare, confirm or make a change.

Approved channel

Check preference, consent, deliverability, operating hours, cost and the sensitivity of message content.

Stop duplication

Prevent multiple calendars, staff actions or connected workflows from sending conflicting reminders.

Reply-aware sequence

Stop routine messages when the customer changes the context.

Confirmation, cancellation, ambiguity and sensitive replies need distinct routing and ownership.

121 CRM · Workflow sequence

Enquiry received

Capture source and customer

Acknowledgement

Set a clear response expectation

Human review

Check fit, consent and exceptions

Owner assigned

Name the person responsible

Follow-up due

Remind the owner, not the customer blindly

Illustrative exampleA conceptual workflow. Triggers, messages, delays and exceptions need configuration and testing.

Handle replies and changes

A response should change the workflow immediately.

Confirmation, cancellation, rescheduling, questions and distress are different events and need different ownership.

Confirm

Record the customer response where appropriate without assuming silence means attendance.

Change or cancel

Update the authoritative system, expose unavailable alternatives honestly and stop obsolete reminders.

Human review

Ambiguous or sensitive reply

Pause the routine sequence and route the message to an authorised person with the appointment context.

Test and review

Prove delivery, state changes and failures before relying on automation.

A workflow that looks correct in the builder can still use the wrong time, duplicate a message or ignore a cancellation.

Representative tests

Cover new, changed, cancelled, duplicate, cross-time-zone, failed-delivery and opted-out appointments.

Operational monitoring

Review rejected messages, expired connections, replies without owners and records whose source systems disagree.

Outcome boundary

Measure usefulness and exceptions without promising that reminders eliminate non-attendance or improve revenue.

Questions about this page

Useful answers, without the sales fog.

1. What is the best appointment reminder schedule?

There is no universal schedule. Consider how far ahead people book, what preparation is needed, how easily capacity can be reused and what customers have been told.

2. Should reminders use text, email or both?

Use the approved channel or combination for the service and customer, considering preference, consent, sensitivity, deliverability, accessibility and cost.

3. What should happen when a customer replies?

The reply should update or pause the routine workflow and reach an owner where judgement or a booking change is needed.

4. Do reminders guarantee fewer missed appointments?

No. They may support clearer communication, but customer circumstances, service design, timing, access and many other factors affect attendance.

Read all CRM questions

Continue the journey

Appointment workflows Workflow automation Follow-up automation guide

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