How Do I Set Up Automated Follow-Up Messages for My Business?
By Bill Stilwell · Last reviewed October 17, 2026
The short answer
Section titled “The short answer”A follow-up sequence is a set of messages your system sends on a schedule after something happens, like a new estimate. Define what starts it, who can enter, each message and its timing, and the person in charge. Make it stop the moment someone replies, books, buys, or opts out, and send replies and complaints to a real person. Log every message and result.
Why it matters
Section titled “Why it matters”Most leads that don’t buy right away never hear from the business again. A good sequence fixes that without you remembering every follow-up. A bad one sends the wrong message to the wrong person, keeps going after a sale, or breaks text and email rules at scale.
18.5.1 Trigger
Section titled “18.5.1 Trigger”What it means: the event that starts the sequence.
How to do it: pick one clear event, like “estimate sent,” “job marked complete,” or “form submitted.” Make sure that event is recorded the same way every time in your system (see 15.6 Customer Lifecycle Stages).
Common mistake: a trigger based on a tag people forget to add, so half the customers never get the messages.
18.5.2 Audience
Section titled “18.5.2 Audience”What it means: who can enter the sequence.
How to do it: set rules for who’s in and who’s out. For example, “estimates over $500, not already booked, with email consent.” Exclude people with open complaints, opt-outs, or no consent for that channel (see 12.6 Communication Consent Records).
Common mistake: a review request going to a customer who just filed a complaint.
18.5.3 Message sequence
Section titled “18.5.3 Message sequence”What it means: each message, its channel, and when it goes out.
How to do it: write out every message and the delay before it. A roofer’s estimate follow-up might be: thank-you email the same day, a check-in text on day 3 if they agreed to texts, and a last email on day 10. Keep each message short and useful. Use approved wording (see 25.7.2 below).
Common mistake: seven messages in five days.
18.5.4 Ownership
Section titled “18.5.4 Ownership”What it means: one named person responsible for the sequence.
How to do it: write down who owns it, who checks it, and who fixes it when it breaks. That person reviews the results at least monthly (see 18.11 Monitoring Automation).
Common mistake: a sequence the former office manager built that nobody else understands.
18.5.5 Exit conditions
Section titled “18.5.5 Exit conditions”What it means: what makes someone leave the sequence.
How to do it: stop the sequence after a reply, purchase, booking, opt-out, or the last message. Test each exit before you turn it on (see 18.10 Testing Automation). Federal Communications Commission (FCC) rules require honoring a text opt-out within a reasonable time, no more than 10 business days, and the Federal Trade Commission (FTC) sets the same limit for email opt-outs.
Common mistake: a customer books on day 2 and still gets “Are you still thinking about it?” on day 10.
18.5.6 Failure handling
Section titled “18.5.6 Failure handling”What it means: catching delivery failures, duplicates, and messages sent to the wrong person.
How to do it: turn on bounce and failure alerts. Block duplicate entries so one person can’t be in the same sequence twice. Check that the right owner gets each reply. Route errors to the owner (see 18.9 Internal Notifications).
Common mistake: a contact entered twice who gets every message twice.
25.7.1 Trigger (automated customer follow-up)
Section titled “25.7.1 Trigger (automated customer follow-up)”This is the same as 18.5.1. When an AI tool or automation platform starts follow-up, the trigger still needs to be one clear, recorded event.
25.7.2 Message
Section titled “25.7.2 Message”Use only approved content. If an AI tool drafts or personalizes messages, set limits on what it can say and review samples before turning it on (see 25.3 Human Review of AI Output). Never let it make promises about price, timing, or results.
25.7.3 Consent
Section titled “25.7.3 Consent”Confirm permission for each channel before any automated message goes out, as in 18.5.2.
25.7.4 Stop condition
Section titled “25.7.4 Stop condition”Stop after a reply, purchase, booking, opt-out, or completion, as in 18.5.5.
25.7.5 Escalation
Section titled “25.7.5 Escalation”Send replies, questions, and complaints to a person, not back into the automation. Set a response time, like one business day (see 16.2.2 Lead Response Time).
25.7.6 Logging
Section titled “25.7.6 Logging”Record each message sent, when, by which tool, and the result, such as reply, booking, opt-out, or failure. Keep the log with the contact record so anyone can see what the customer received.
When to get help from a pro
Section titled “When to get help from a pro”A customer relationship management (CRM) or automation specialist can build and test sequences. If your sequence includes marketing texts, have an attorney review the consent and wording. Questions to ask:
- Do my exit conditions catch every reply, booking, and opt-out?
- How will I know if a message fails or goes to the wrong person?
- Does this sequence need different consent for texts than for email?
Bill’s note
Section titled “Bill’s note”[Bill: add a short note. For example, the follow-up sequence SiteSmarty uses after sending a proposal, or a client whose broken sequence kept emailing customers after they bought.]
How I did this for SiteSmarty
Section titled “How I did this for SiteSmarty”- [Date I did this:]
- [What I actually did, step by step: one SiteSmarty sequence with its trigger, messages, delays, and exits]
- [What it cost and how long it took:]
- [What surprised me or what I’d do differently:]
- [Screenshot or photo to add, with private info blurred: the sequence in the automation tool]
- [Result so far:]
Questions people ask
Section titled “Questions people ask”What should start a follow-up sequence? One clear event recorded the same way every time, like an estimate being sent or a job being marked complete.
How many follow-up messages should I send? Usually 2 to 4, spread over one to two weeks, with the last one making it easy to say no.
When should a sequence stop? As soon as the person replies, books, buys, opts out, or reaches the last message.
Who should handle replies? A named person, with a set response time. Replies shouldn’t go back into the automation.
Audit check
Section titled “Audit check”| Outline line | Question | Pass looks like | Fail looks like | Evidence to collect |
|---|---|---|---|---|
| 18.5.1 Trigger | Is each sequence started by one clear recorded event? | Reliable trigger | Manual tag often missed | Automation settings |
| 18.5.2 Audience | Are entry and exclusion rules set, including consent? | Rules exclude opt-outs and complaints | Everyone enters | Entry rules |
| 18.5.3 Message sequence | Is every message and delay written out? | Documented sequence | Unknown or excessive messages | Sequence map |
| 18.5.4 Ownership | Does each sequence have a named owner? | Owner listed and reviewing | No owner | Automation inventory |
| 18.5.5 Exit conditions | Do replies, bookings, purchases, and opt-outs stop the sequence? | Tested exits | Messages after booking | Test results |
| 18.5.6 Failure handling | Are failures and duplicates caught and routed? | Alerts and duplicate blocking | Silent failures | Alert settings |
| 25.7.1 Trigger | Are automated follow-up triggers documented? | Same as 18.5.1 | Same as 18.5.1 | Automation settings |
| 25.7.2 Message | Is automated or AI content approved? | Approved templates and limits | Unreviewed AI messages | Template approvals |
| 25.7.3 Consent | Is consent checked by channel? | Consent filter on | No filter | Entry rules |
| 25.7.4 Stop condition | Do stop conditions work? | Tested | Failing | Test log |
| 25.7.5 Escalation | Do replies and complaints reach a person? | Routed with response time | Replies lost | Routing rules |
| 25.7.6 Logging | Is each message and result logged? | Log on contact record | No log | Contact history |
Where this fits
Do this first: 18.3 Email Marketing Rules, 18.4 Text Message Marketing Rules
Do this next: 18.7 Referral Programs
Related pages: 16.7 Follow-Up Procedures, 14.6.1 Review Request Timing, 15.6 Customer Lifecycle Stages, 18.10 Testing Automation, 18.11 Monitoring Automation, 12.6 Communication Consent Records
Sources
- Electronic Code of Federal Regulations, 47 CFR 64.1200, Delivery restrictions (checked October 17, 2026)
- Federal Trade Commission, "CAN-SPAM Act: A Compliance Guide for Business" (checked October 17, 2026)
- Google Business Profile Help, "Tips to improve your local ranking on Google" (checked October 17, 2026)
This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.