In this guide 6 sections
Pick the stages worth a reminder. Give each a reviewed template, set consent and one frequency cap per customer, and let any reply pause the automation and reach a person. Careless automation becomes spam. Limited automation saves hours without annoying anyone.
Define which customer stages need a reminder
Not every moment needs a message. Automate only stages where a reminder changes the outcome: a forgotten appointment, an invoice about to turn overdue, a quote nearing expiry or a subscription about to renew. Consider a hairdresser group with several branches, where a booking made two weeks ahead is exactly what a client forgets without a nudge the day before.
Give each message one purpose. A reminder says something is coming, a confirmation says something just happened, and a nudge says something expected has not happened yet. Mixing them reads like marketing. Customers then ignore the message or report it as spam, which damages the sender reputation of the number or domain you depend on.
Set exact triggers, owners and approved templates
Vague timing produces vague results. Replace “a few days before” with an exact rule, such as 24 hours before the slot, read from the booking record itself rather than from someone’s memory. Store each customer’s timezone too, because a nine o’clock reminder sent from head office lands at the wrong hour for anyone travelling or living abroad. Every stage also needs an owner, a named person accountable for the wording who rechecks it whenever the booking process or the price list changes.
Have templates reviewed first. A reminder carrying a stale price, an old branch address or a clumsy tone reflects on the business exactly as much as a letter someone typed by hand. Test every merge field, because a blank salutation or a wrong first name makes the whole message look automated and careless to a customer who may have visited yesterday. Put the legal disclaimer in the template.
Set consent, frequency limits and a clear stop rule
Confirm consent for every channel first. Keep a dated record of that consent for WhatsApp, SMS and email separately, because being a customer is not the same as agreeing to be messaged. Reminders about their own appointment or invoice are transactional and should stay apart from promotions, which face stricter consent and do-not-disturb rules that your legal adviser should confirm.
Cap messages per customer. Nobody should receive four automated messages in one day because a payment reminder, an appointment reminder and a feedback request all came due together. When two rules fire on the same day, a written tiebreaker decides which single message wins and which one waits until the following morning. Keep a suppressed list of everyone who has unsubscribed or complained, and check it before every send, including sends from forgotten older rules. Always offer a working stop. A reply keyword, an unsubscribe link or a phone number that reaches a real person all qualify, but the stop must actually halt the next message.
Handle replies, failures and handoffs to a person
Customers will answer your reminders. At minimum, a reply should stop further automated messages on that thread and flag the conversation for a person to read the same day. Never fire beside an unanswered question. Offer a snooze for busy customers.
Plan for failure too. An invalid phone number, a bounced email, a voicemail or an undelivered message should be logged, and repeats for one customer flagged for a manual check. Do not retry forever. Retry a failed message twice with a growing backoff, then flag it instead of dropping it silently, because a dead number or carrier throttling will not fix itself.
Measure completion rates and watch for complaints
Track two things weekly. First, check whether the reminder did its job: the appointment was kept, the payment arrived sooner or the quote was accepted before expiry. Second, watch opt-outs and complaints. A message that sends but changes nothing, or one that draws complaints, needs its timing, wording or frequency revisited instead of running on just because it is automated.
Review every few weeks at first. Move to a quarterly review once the numbers settle, because customer tolerance for message frequency drifts and a cadence that worked at launch may feel heavy a year later.
Reminder state diagram
One customer, traced from trigger to send. Silence leads to the next reminder under the frequency cap, a reply pauses everything and routes to a person, and a failure is logged and flagged after repeats. Design stop conditions with it first.
Open a blank worksheet to printQuestions owners ask
How do we avoid excessive reminders?
Set one frequency cap per customer across all reminder types combined. Review real send volumes monthly at first to catch any rule firing more often than intended, since three separate rules can quietly stack into three messages in one week.
Can replies pause automation?
They should, by default. A reply means the automation’s assumption that nothing has changed may no longer hold, so a person takes the thread and automation resumes only after a deliberate decision.
Which channel suits reminders best?
Use whichever channel the customer already uses with you and has agreed to, whether WhatsApp, SMS or email. Test one channel for a month before adding another.
