To automate customer follow-up text messages, begin with a verified event and a clearly defined purpose. Separate service messages from promotions, check eligibility and consent evidence before every send, identify the sender, process replies and revocations, suppress promptly, and route exceptions to a person. Service and promotional workflows may require different evidence, controls, wording, and escalation, so classify the message before building the sequence.
This is practical operational information, not legal advice. There is no universal consent rule, quiet-hours rule, frequency cap, opt-out keyword list, or retention period for every text. Requirements depend on the message content, purpose, technology, recipient, and jurisdiction. Make those variables configurable and have qualified counsel approve the policy matrix before launch.
Define the event and purpose
Start with one event that can be verified, such as an appointment ending, an order shipping, a quote expiring, a support case closing, or a customer requesting information. Record the event source, timestamp, customer identifier, and the business owner responsible for the follow-up.
Then define one purpose for the message. “Confirm the appointment outcome” is a purpose. “Follow up with the customer” is too vague. A precise purpose lets the workflow decide whether the text is necessary, whether the customer is eligible, what data may appear, and what should happen after a reply.
Make the trigger idempotent. Give every event a unique key so a CRM retry, webhook replay, or manual update cannot create duplicate texts. Add cancellation conditions too. A payment received, appointment rescheduled, ticket reopened, or human reply may make a queued message obsolete.
Separate service from promotional content
Create separate campaign types, templates, consent logic, and suppression scopes for service and promotional messages. A delivery update, requested quote, or appointment reminder may be operational. A discount, upsell, referral offer, or invitation to buy is promotional. A message that mixes both should enter the promotional review path unless your legal team approves another classification.
Do not assume that an existing customer relationship creates permission for every promotion. The UK ICO says unsolicited electronic marketing to individual subscribers normally requires consent, subject to limited soft opt-ins whose conditions must all be met. Its examples also distinguish an order confirmation text from later marketing texts in the current PECR electronic-mail marketing guidance.
Keep detailed scripts and cadence outside this automation architecture. The follow-up cadence and outreach sequence explain those adjacent concepts. Copy choices cannot repair a workflow that misclassifies the purpose or sends to an ineligible number.
Establish eligibility, consent, and evidence
Run an eligibility decision immediately before each send, not only when the customer enters the sequence. Check the recipient, phone number, jurisdiction, message purpose, sending technology, consent or other approved basis, source of that evidence, consent scope, prior revocations, suppression status, account state, and recent messages.
Store a decision snapshot with the message record. It should show the rule version, evidence consulted, result, timestamp, provider request ID, and reason for any block. This makes audits and incident reviews possible without pretending that a provider dashboard is your compliance system.
The CTIA Messaging Principles and Best Practices, May 2023 are voluntary industry guidance, not law or worldwide messaging rules. The document primarily addresses the U.S. wireless ecosystem using 10-digit North American Numbering Plan numbers across SMS, MMS, and RCS, with separate material for short codes. It recommends clear calls to action and records such as the consent timestamp, acquisition method, capture experience, campaign, phone number, and consenting identity. It also says an opt-in should apply to the campaign and sender for which it was obtained.
Choose a provider that supports the approved sender type, two-way replies, webhooks, delivery events, registration requirements, error codes, and suppression controls. Using an API or aggregator does not transfer responsibility away from the sender. The ICO notes that an organization asking another party to send its marketing may remain responsible as the instigator while the other party may also be responsible.
Set delay, timezone, and frequency controls
Configure the delay from the event, recipient-local sending window, purpose-specific frequency cap, and collision rules across active campaigns. Do not hard-code one global quiet-hours window or cadence as if it were legally universal.
If the timezone is reliable, schedule against it. If it is missing or disputed, hold the message or use a conservative rule approved for that workflow. Stop queued follow-ups when the customer replies, completes the requested action, becomes ineligible, or enters suppression.
Use a shared contact timeline so two departments do not send competing texts minutes apart. Detailed wording and cadence should be tested only after eligibility and stop conditions work correctly.
Write identity, purpose, and opt-out language
Identify the business early in the text and make the reason for contact understandable without requiring the recipient to open a link. Use the approved legal entity, brand, or program name consistently with the consent record and sender registration.
For recurring campaigns, disclose the nature of the program and provide an appropriate way to stop messages. CTIA’s voluntary guidance recommends that recurring-message confirmations name the program or product, provide customer-care information, explain how to opt out, describe recurrence or frequency, and address applicable charges in the Messaging Principles and Best Practices.
Do not hide identity behind a generic short link, vague sender label, or unexplained number. Do not add promotional copy to an opt-out confirmation. Keep templates versioned so the system can show exactly what the recipient was sent.
Process replies, STOP-like requests, and suppression
Treat every inbound reply as a workflow event. Preserve the original text, normalize case and punctuation for classification, and route it into categories such as revocation, positive response, question, wrong number, complaint, sensitive issue, or ambiguous intent.
A closed keyword list is not enough. For covered U.S. robocalls and robotexts, the FCC says consent may be revoked through any reasonable method that clearly communicates the desire to stop. It recognizes certain standard reply words as reasonable by themselves, but it also says other wording can be valid when a reasonable person would understand it as revocation. Requests can also arrive through methods beyond a reply text, including voicemail or email in appropriate circumstances. See the FCC’s 2024 TCPA Consent Order.
Apply suppression as soon as the request is recognized, before sending any permitted confirmation. For covered requests, the FCC rule generally sets an outside limit of a reasonable time not exceeding 10 business days. Covered exempted package-delivery notification calls and texts instead have a limit of no more than six business days. Do not use either outside limit as an operational waiting period.
For covered U.S. requests, the FCC permits one narrowly limited confirmation after a revocation. It must be the only additional message, may only confirm or clarify the request, and cannot contain marketing. A confirmation sent within five minutes is presumed to fall within the recipient’s prior consent; five minutes is a presumption, not an absolute deadline. For a later confirmation, the sender must show the delay was reasonable. If the sender asks which of several informational categories may continue, consent-required calls and texts must stop unless the person affirmatively identifies what may continue.
The July 2026 timeline is narrow and important. The FCC’s January 6, 2026 extension order, DA 26-12 extends only the waiver for the cross-program portion of section 64.1200(a)(10). That provision would require a revocation made in response to one type of informational message to apply to all future robocalls and robotexts from that caller on unrelated matters. The narrow rule did not take effect on April 11, 2026 and is extended through January 31, 2027.
The April 2025 limited waiver order had moved only that same requirement to April 11, 2026 and stated that the other affected rules remained required as of April 11, 2025. The January 2026 order says its extension does not alter the status quo for any other prior FCC rule or ruling on revocation.
Model suppression with several possible scopes, such as campaign, purpose, channel, sender, entity, and phone number. A clear request to stop everything should not be ignored because the narrow cross-program rule is waived. Route uncertain scope to a trained human and pause affected sends while it is reviewed.
Route escalation, ambiguous replies, and delivery errors
Send ambiguous revocations, complaints, legal requests, threats, account-security issues, and sensitive health or financial questions to a human queue with a response deadline and owner. The automation should pause messages that could worsen the issue.
Classify delivery errors as permanent, temporary, or unknown. Suppress or quarantine invalid, deactivated, or wrong-party numbers according to approved policy. Limit retries for temporary failures, and never turn repeated provider errors into repeated customer contact.
A unified operating view helps teams avoid parallel replies. The unified inbox glossary defines the routing concept, and BrandJet’s article on tracking campaign replies in one inbox provides related workflow context. Neither is legal authority.
Measure delivery, response, opt-out, and conversion responsibly
Track provider acceptance, delivery status, reply rate, positive response, opt-out rate, conversion, suppression latency, duplicate prevention, escalation volume, and unresolved errors. Segment results by trigger, purpose, provider, sender, jurisdiction, and template version.
Do not treat a delivery receipt as proof that a person read the message, and do not treat a conversion as proof that the earlier eligibility decision was correct. Never improve a visible opt-out rate by making the opt-out harder to find.
Test only within an approved eligible population. A useful experiment compares timing, message clarity, or routing while holding consent and suppression rules constant. Stop tests when complaints, wrong-number responses, or delivery anomalies indicate risk.
Checklist to automate customer follow-up text messages
- [ ] Define one verified event, one purpose, one owner, and cancellation conditions.
- [ ] Classify the message as service, promotional, or mixed before enrollment.
- [ ] Build a send-time eligibility check with versioned evidence and suppression.
- [ ] Configure timezone, delay, frequency, collision, and duplicate-send controls.
- [ ] Identify the sender and explain the purpose in every approved template.
- [ ] Ingest replies from text and other monitored revocation channels.
- [ ] Suppress promptly, preserve scope, and route ambiguous cases to a human.
- [ ] Log provider events, decision reasons, errors, escalations, and key metrics.
- [ ] Review the workflow with legal, privacy, security, support, and operations before activation.
Frequently asked questions
What should an SMS consent record contain?
Store the phone number, consenting identity, timestamp, acquisition method, exact capture experience and disclosure, sender, campaign or purpose, scope, source system, and evidence artifact. Also retain the applicable policy version and later revocation history under a counsel-approved retention schedule. A checkbox without its surrounding disclosure is weak evidence.
What if the customer’s timezone is unknown?
Do not guess from an area code and treat the result as certain. Hold the text, obtain a reliable timezone, or apply a conservative workflow-specific rule that counsel has approved for the relevant jurisdictions. Record the source and confidence of timezone data so disputed or stale values can be reviewed.
How should automation handle a reassigned or wrong-party number?
Stop the affected workflow, suppress or quarantine the number under the approved policy, preserve the evidence, and route any uncertainty for review. Do not assume a successful delivery receipt proves the intended customer still controls the number. Use an approved reassigned-number and identity-verification process for the jurisdiction and use case.
How do I prevent duplicate texts after a webhook retry?
Create a stable idempotency key from the source event, recipient, purpose, and sequence step. Store it before the provider request, reject repeated keys, and reconcile the provider request ID afterward. A retry should resume the same state transition, not create a new enrollment or a second message.
What if a reply asks a question and also says to stop?
Honor and suppress the revocation first, preserve the full reply, and route the substantive question to a human without restarting automated promotion. Any response must follow the approved policy for that message type and must not turn an opt-out confirmation into a marketing message.