SMS automation

SMS automation that sends reminders and updates, and reads the replies

We build the text flows for your business, from the consent on your forms to the registration, the reply rules and the opt-out list.

Scope your first text workflow
Trusted by the world's fastest-growing brands

What it is

A text that goes out on its own, and a reply that is read

SMS automation sends text messages when something happens in your business: a booking is saved, a job is ready, a lead fills in a form. It also reads what the customer texts back and acts on it. The build has three parts, and each one is written down before it runs.

Scope · text 1 of 4For your approvalBooking confirmationStarts whenAn appointment is savedGoes outAt once, inside the windowSample Bluegrass Tire & Auto: your visit isbooked for Nov 13 at 10:30 a.m. Reply C tocancel or R for new times.Reply STOP to end texts.Ends whenReply C, R or a question

The trigger

The event that starts a text: a saved appointment, a changed job status, a form entry. We choose the trigger that fires once for each real event, so a customer gets one reminder for one visit.

The message

Short copy that names your business, says what the text is for and tells the customer how to stop it. The wording sits in the scope for your approval, one entry for each text the workflow can send.

The reply

A customer who answers C to cancel, asks a question or writes “please stop texting me” gets handled by a rule. Questions reach a person at your desk with the thread attached.

Two ways to run it

Texts built into your systems, or sent from a broadcast tool

Both routes send text messages. They differ in what starts a text, what the tool knows about the customer, and where the consent record lives.

A broadcast toolSent by a personAutomation tied to your systemsTriggered by events
What starts a textA person writes a message and picks a list to send it toA booking, a status change or a form entry in your own tools
Who gets itA segment or the whole listThe one customer the event belongs to, with their details filled in
Consent recordA list membership, with the detail kept wherever the list was collectedA field on the contact showing when, where and for which texts they agreed
RepliesLand in an inbox for someone to read and sortRead by rules: a keyword is acted on, a question goes to a named person
Best forA one-time announcement or a seasonal offerReminders, status updates, follow-ups and missed-call replies
Which one do you need?

If the text follows something a customer did, such as booking, paying or asking a question, tie it to the event. If it is a single announcement to a list that agreed to promotions, a broadcast tool is the simpler fit. Some shops run both, and the audit sorts which texts belong where.

What the sources say

Six published rules we build the text flow around

Five come from CTIA and Twilio, and one from federal and state law. Beneath each rule you will find its source and the day we read it. None of this is legal advice, and your attorney sets the reading.

  1. Kinds of textInformational or promotional

    CTIA’s guidelines put appointment reminders in the informational category, and say a call-to-action added to one may move it into the promotional category.

    CTIA expects the customer to agree in writing before promotional texts. So we keep a reminder as a reminder, and a coupon, an upsell or a “book your next service” line goes in a separate text for contacts who agreed to promotions.

  2. Consent recordsSeven data points

    CTIA says senders should keep the time of consent, the form or channel used, the wording shown, the campaign, the IP address, the number and who consented.

    We add those fields to the contact record, so “when did this customer agree, and to what” has an answer you can read. Where a source has no record, as with a phone booking typed by staff, the audit lists that group for a fix.

  3. Opt-outOne confirmation, then silence

    CTIA says a sender should reply to an opt-out with one final confirmation for that campaign, and send nothing after it.

    The same section says standard STOP wording belongs in the message, and that plain-language requests such as “please opt me out” should also be read and acted on. We build the confirmation text, and a step that moves the number to the suppression list before any other workflow can send to it.

  4. RegistrationBrand and campaign

    Twilio says A2P 10DLC registration has two parts, a brand and a campaign, and that unregistered traffic on a 10DLC number draws additional carrier fees.

    The campaign states how people opt in, opt out and get help. Twilio also says registering lowers message filtering and raises throughput. We prepare both parts from your records and you approve them before they go to the registry.

  5. Keyword filtersWords a platform catches

    Twilio’s default opt-out handling covers STOP, UNSUBSCRIBE, END, QUIT, STOPALL and CANCEL, and replies in other words do not block further messages.

    Twilio’s changelog adds REVOKE and OPTOUT to the list as of May 13, 2025 and says “OPT OUT” with a space is not supported. The FCC names several wordings as reasonable, so our reply step reads the rest of the message and suppresses the number when the meaning is clear.

  6. Sending hours8 a.m. in federal and state rules

    The FCC rule bars telephone solicitations to a residential subscriber before 8 a.m. or after 9 p.m. at the called party’s location, and Florida’s statute narrows the evening limit to 8 p.m.

    Florida also caps solicitation calls at three in 24 hours on the same subject, and Oklahoma’s statute, as published on Justia, sets the same evening limit. We set one send window inside all three, in the customer’s time zone, and hold an overnight text until it opens.

The scope

What SMS automation produces

Six parts of one working text flow. The accounts are yours, and a short document describes each part.

Online booking form1 of 3 sourcesMobile number(859) 555-0123Text me reminders and ready notices fromSample Bluegrass Tire & Auto.Text me service offers. Optional.Reply STOP to end texts, HELP for help.SavedTimeForm versionWording

Consent capture

We write the sign-up wording for your booking form, tablet and phone script, name your business, say what the texts are for and how to stop them, and store when and where each customer agreed. You receive: the form wording in place, and a consent field layout for the contact record.

Carrier registration2 partsBrandApprovedSample Bluegrass Tire & AutoCampaignIn reviewReminders, ready notices, offersOpt-inForm, tablet, counter cardOpt-out, helpSTOP to end, HELP for help

Carrier registration

We prepare the brand details and the campaign description from your records, with sample messages, and submit them once you approve. If a registrar asks for a fix, we read the reason and resubmit. You receive: the registration pack, and the status of the brand and the campaign.

Message map4 textsTextGoes outBooking confirmationAt onceReminder10 a.m. day before405 sent; 15 same-day: confirmation onlyReady for pickupJob marked doneService due offerOffers box only

Message flows

We build each text from its trigger to its end: a confirmation, a reminder, a ready notice, a follow-up. Each flow lists its wait times and what stops it. You receive: a message map with the wording, the trigger and the exit for each text.

Reply log96 repliesConfirm or cancelWorkflow61QuestionsFront desk22STOP keywordSuppressed9Other wordsSuppressed461 + 22 + 9 + 4 = 9613 suppressed

Reply handling

A reply of C cancels the booking, R offers new times, and a question goes to a named person at your business with the thread attached. The test log shows each reply run on sample numbers. You receive: a reply table listing each kind of reply and what the workflow does.

Send windowTime zone by ZIP12 a.m.6 a.m.Noon6 p.m.12 a.m.FCC rule: 8 a.m. to 9 p.m.Florida: 8 a.m. to 8 p.m.Sample window: 9 a.m. to 7 p.m.Booked 11:40 p.m.Confirmation at 9 a.m.

Send window

We set the hours texts can go out, inside the federal and state limits we identified for your customer base, and hold a text that is due overnight until the window opens. The customer’s time zone comes from the ZIP code on the booking. You receive: a send-window rule with the hours, the states it covers and the hold behavior.

Suppression list13 numbers(859) 555-0131Added Nov 102:05 p.m.Reply: STOP2:05 p.m.Final confirmation, 1 of 1Sample Bluegrass Tire & Auto: youwill get no more texts from us.Nov 12ReminderNot sent: on listMay 13Service offerNot sent: on list

Opt-out and suppression list

A STOP, or any other clear request to stop, moves the number to a suppression list that each text workflow reads before it sends. The customer gets one confirmation, and the list stays in your account. You receive: the suppression list, the confirmation wording and a short guide for staff who hear a request by phone or in person.

How it runs

From a consent audit to a text flow you can read

You approve the scope first and each stage after it, and each stage hands you one document to keep. The samples follow a fictional tire and repair shop, Sample Bluegrass Tire & Auto in Lexington, KY.

consent-audit.csv

Consent audit, contact list export

Sample · Sample Bluegrass Tire & Auto, Lexington, KY
SourceNumbersRecord heldTexts it supports now
Online booking form1,150Timestamp and form versionReminders and ready notices; offers after a new unticked box is added
Front-desk tablet640Signature, no timestampReminders and ready notices once the timestamp is added
Phone bookings typed by staff380None savedNone until the customer agrees at the next visit or on a form
Total2,170
The 380 phone numbers have nothing on file showing agreement, so they are held out. The audit states what the records show. Whether a reminder needs written consent in your situation is a question for your attorney.

Our stack

The tools the text flows run on

Each one can start a text, send it or record what came back. We choose by the job and the volume, and the accounts are in your name. Webzenia is not a partner or reseller of any of these vendors.

Twilio
Why Twilio

A messaging service that sends and receives texts through an API, with number registration built into its console.

How we use it

We use it as the sending layer when a shop needs its own number and its own registration. Billing runs from your account, and Twilio’s default stop filter is switched on.

ProgrammableReliabilityChannels
TwilioAll
GupshupYes
MessageBirdYes
SaaS toolLimited

Questions

SMS automation, answered

Start here

Get a written scope for your first text workflow

Tell us which texts you send by hand today. You get a scope with the messages, the consent they need and the price side by side, and you decide after reading it.