Texting customers works because people read texts. It also comes with rules, and the rules exist because texts are personal. A business that texts someone who did not agree to it, ignores a request to stop, or sends at midnight is not just annoying a customer. It is exposed. The usual worry about AI is that it will make this worse by sending more messages faster. In a Staffhand build the opposite is true, because every text passes through an approval queue and a set of rules before a person decides to send it. This article explains how.
The four things texting compliance comes down to
Rules differ by country, state and carrier, and your build follows the stricter reading that applies to you. Underneath the detail, compliance for a business texting customers comes down to four practices:
- Consent. The person agreed to receive texts from you, and you can show when and how.
- Opt-out. A reply of STOP, or any plain request to stop, ends the messages immediately and is honored everywhere.
- Timing. Messages go out within reasonable hours in the recipient’s time zone, never in the middle of the night.
- Records. You can show what was sent, to whom, when, and on what basis.
Most compliance failures in small businesses are not deliberate. They are a staff member texting from a personal phone, a marketing blast sent to the whole contact list, or a tool that fires on a trigger with nobody checking the list. The approval queue closes each of those gaps.
Consent is checked before a draft exists
Each desk that can text checks the consent record before it drafts anything. A phone number collected for an appointment confirmation is not consent for a promotion. The build keeps those categories separate in your systems. If a desk has a reason to message someone and no record of consent for that kind of message, it does not draft a text. It flags the contact so a person can ask for consent properly, or it uses a channel the customer did agree to.
The approver in the queue sees the consent basis next to the draft. If something looks wrong, the message is held and the record is fixed first.
STOP is honored by every desk at once
When a customer replies STOP, or “please stop texting me,” or anything that plainly means the same, the opt-out is recorded against the contact and every desk sees it. The lead follow-up desk, the review request desk, the reminder desk and the campaign desk all stop at the same time. There is no second list that forgot.
The confirmation of the opt-out is the one message that still goes out, because the customer should know it worked. Everything else stops.
Quiet hours are a rule, not a preference
Each build sets quiet hours for outbound messages. A draft created outside those hours waits in the approval queue until the next allowed window. This applies to the first text back after a missed call, to follow-up messages, to reminders and to review requests. No desk sends outside the window the business set, and the window is set to the recipient’s time zone where the business has customers in more than one.
For an owner, quiet hours also protect the brand. A text at 11pm tells a customer you are automated. A text at 8am tells them you are open.
The approval step catches what rules miss
Rules handle the clear cases. The person in the approval queue handles the rest. Every customer-facing text is drafted by a desk and waits for a staff member to approve it, edit it or hold it. The approver sees who the message is to, why the desk drafted it, the consent basis, and the wording. A message that is technically allowed but tonally wrong, or sent to someone who complained yesterday, gets held.
After a few weeks, an owner may choose to let certain routine messages run on templates approved once: appointment confirmations, for example. That is a decision made after watching the queue, and the consent, STOP and quiet-hours rules still apply to every templated send. One approval queue describes the queue in detail.
Records you can produce
The live action log records every message sent, the time, the recipient, the desk that drafted it and the person who approved it. Consent and opt-out records live in your systems. If a customer or a regulator asks what was sent and why, you can answer from your own records, because everything was set up in your accounts and stays there. The compliance and records desk keeps these records tidy and flags gaps. See Example builds for the full desk list.
Frequently asked questions
Does approval slow texting down too much to be useful?
The draft is instant. The approval takes a tap. A text that goes out ten minutes after a missed call, read by a person, beats one that goes out in ten seconds and should not have been sent.
What about texts customers send us first?
A customer who texts the business has opened a conversation, and replying is expected. The desk still drafts the reply for approval, still honors STOP, and still does not answer price or financing questions.
Who sets the quiet hours?
You do, during the build, and you can change them. The default is conservative.
Can the AI text from a staff member’s personal phone?
No. All messages go through the business number connected to the build, so every message is logged and every opt-out is honored in one place.
The digital audit includes a look at how your business texts customers today, including consent and opt-out handling. Start with a digital audit.
