Recall and reactivation, timed to the service

You can keep attracting new customers while total appointments remain flat. Some people complete one visit or project, receive no relevant follow-up, and disappear from the active customer journey. That is a continuity problem before it is an advertising problem: more new inquiries hide the gap for a while, but they do not establish who should return, when contact is appropriate, or who owns the response.

Recall

• Follows an expected service cycle
• A known interval, or a next-service date
• The message says you are due
• Needs a reliable due date

Reactivation

• Addresses an inactive relationship
• Overdue, stopped responding, or never returned
• The message asks whether they would like to return
• Needs context, because inactivity has many causes

Who hears from you, and who does not

A customer on the listSuppression checks run again just before sending, because booking and opt-out status change

• If they are due on the service cycleA recall message, timed to the service.The system handles it
• If they are overdueA recall message that says so.The system handles it
• If they have gone inactiveA reactivation message with a reason to return.The system handles it
• If they already have a bookingNothing is sent.Held back
• If they have an open complaintHeld for a person to resolve first. Recall waits on that.A person takes over
• If they opted out, moved, or are unsuitableHeld back.Held back
• If they reply, ask a question, or complainA person takes over.A person takes over

Start with a usable list

A usable list needs accurate contact information, permission or another approved basis for contact, service history, last-contact dates, and the fields used to decide eligibility. Incomplete data limits the campaign: a missing last-service date makes recall timing impossible, an old number causes failed delivery, and duplicate records send the same person several messages. Data cleanup does not turn unknown history into fact, so contacts with insufficient evidence are held back or reviewed by staff.

Segmentation prevents a person with a future appointment from receiving a message asking them to book again, and keeps a completed one-time project out of a recurring-service sequence. Each added rule uses a dependable field, because complex segmentation built on poor records creates precise-looking mistakes. The final audience is reviewed before the first production send.

The response path

Every message needs a next step. A reply may enter a shared inbox, an assigned conversation, a booking page or a staff queue, and the person responsible for follow-up is named before outreach begins. Booking requests update the contact stage and suppress unnecessary follow-up, opt-outs enter the suppression record immediately, and questions, complaints and wrong numbers follow documented exception paths.

The booking handoff matters as much as the message. A strong response that sits unanswered in an inbox does not restore the relationship.

Where a launch involves patient information, it requires an approved privacy design, the written agreements the jurisdiction calls for, and the practice’s written authorization. The practice remains responsible for its own privacy assessment and clinical protocols.

What gets measured

• Contacts reviewed, included and excluded
• Messages attempted, delivered and failed
• Replies received
• Booking actions, and appointments recorded
• Opt-outs, wrong numbers and exceptions for staff

Revenue is not assigned to the sequence unless a reliable record connects the contact, response, appointment, and completed transaction. A link click alone is not recorded as a sale.

Its place in your growth system

Automation & AI runs the approved sequence, while Customer Continuity defines why and when an existing customer should hear from you.

Next step

Bring a sample customer export, service cycles, exclusion rules, current messages, and the path from reply to booking. We will check whether the list, timing, reason to return, or booking handoff should be fixed first.