What a rebooking sequence actually says

Message one. Cycle-timed prompt

Fires at the target rebooking window for the customer's last service. Sent on the channel they booked with.

Example (six-week cycle):

• • Hi [First name]. It has been about six weeks since your last [service]. Want the same day and time this week, or a different day works better?
• • Booking link: [link]

Why message one works

It names the last service so it does not read as a mass send. It offers a specific default (same day and time) so the customer does not have to think. It closes with a real link, not a promise to call.

Message two. Soft nudge

Two weeks after message one, only if the customer has not booked. Same channel. Shorter.

Example:

• • Hi [First name]. Still holding the calendar for you. Want me to book you in? [link]

Confirmation message

When they book, the confirmation carries the last visit's context so it does not feel like a new customer flow.

Example:

• • Booked. [Service] on [date] at [time]. Same as last visit. See you then.

What to strip

Every one of these creeps into working sequences. Cut them all.

• Emojis, exclamation points, and marketing brand blocks.
• We miss you, hope you are doing well, and other filler.
• Manufactured urgency: only a few spots left, book now.
• Discount codes bundled into the ask.

Worked example. Adapting one script across three services

One base script: 'Hi {name}, you're due for your {service}. Want your usual {window}? Book here: {link}.' That single template covers a haircut, a lash fill, and a car detail if the tokens are populated correctly.

For services with variable duration, add one clause: 'or reply with a day that works.' For services that always book on the same day of the week, drop it. Do not maintain three separate copies; maintain one template and let the data control what appears.

The failure mode is not tone. It is stale tokens. When {service} says 'default' or {window} says '4-6 weeks' for a service that changed to 6-8, customers notice.