U.S. Business Texting Now Starts With Permission

Business texting remains useful for reminders, service updates and carefully targeted offers, but a U.S. campaign can no longer be treated as a simple broadcast list. The enduring advantage is timely, direct communication; the practical change is that permission, opt-out handling and sender registration now shape the campaign before its wording or schedule does.

The requirements are not identical for every message or phone number. Businesses need to define why they are texting, establish how each recipient joined, separate operational communication from promotions and identify which approval system applies to the selected sender type.

Business texting is a permission channel

A phone number in a customer database is not automatically permission to send marketing texts. Someone may have supplied it for delivery coordination, account security or one appointment without agreeing to recurring promotions. Reusing the number for a different purpose can create legal risk and undermine the trust that makes texting useful.

The applicable U.S. consent standard depends on the technology, message and circumstances. The FCC’s January 2026 order notes that the TCPA generally requires prior express consent for covered robocalls and robotexts unless an emergency purpose or applicable exemption applies; it also extends the narrower rule for applying one revocation across unrelated message categories until January 31, 2027.

That distinction matters. The extension does not turn every business text into a consent-free communication, nor does it eliminate the need to honor a valid withdrawal within the program to which it applies. A business should review its particular campaign instead of assuming that a purchase, email subscription or earlier conversation authorizes recurring SMS marketing.

Useful consent records show the phone number, collection date, collection point, disclosure presented and program the person joined. The stored evidence should include the relevant version of the form, checkbox language or keyword flow. A database field marked only “subscribed” cannot demonstrate what the customer accepted if the message purpose later changes.

Opt-outs must work through the underlying systems

An unsubscribe instruction has little value if a reply never reaches the suppression process. Marketing, billing and support tools may maintain separate customer records, so an opt-out received by one system can be missed by another. The operational task is to connect revocation events to every system that sends messages within the affected program.

Businesses should retain a timestamped record of the request and test more than a perfectly formatted STOP reply. A clear natural-language request to stop may also need handling, depending on the circumstances. Automated classification should therefore have an escalation path for replies it cannot interpret safely.

A brief non-promotional confirmation can tell the recipient that an opt-out was processed. Further messages should stop within the relevant program unless the person affirmatively subscribes again or a separately reviewed legal basis applies. A service notification should not be used as cover for an appended sales offer.

Registration and consent solve different problems

Consent addresses whether the business should contact a person. Sender registration identifies the organization and declared messaging use case to the carrier ecosystem. A campaign can have willing subscribers and still face filtering or other delivery restrictions if it uses an unregistered or mismatched route.

For Twilio customers, its current A2P 10DLC documentation requires registration when an application sends SMS or MMS to U.S. recipients over a ten-digit long-code number. The registration has separate Brand and Campaign components: the first identifies the sender, while the second describes the message purpose and the methods recipients use to opt in, opt out and request help.

This requirement does not make a ten-digit long code the correct choice for every sender. Toll-free numbers and short codes use different approval systems and may suit different traffic patterns. The route should be selected before the campaign is built so that its real brand, use case and consent journey can be submitted through the appropriate process.

Registration is also not a substitute for permission. Approval of a brand and campaign does not transform an unrelated customer list into an eligible SMS audience. Conversely, a documented opt-in does not remove the need to register a route where the provider and carrier system require it.

Public disclosures are part of campaign infrastructure

Privacy and terms pages should describe the program customers actually encounter. They need to identify the business, align with the consent language and remain publicly accessible when a provider uses them during vetting. Brand names, message examples and stated purposes should be consistent across the website, registration submission and production traffic.

The requirement has become more explicit for one major provider. Twilio’s April 2026 registration notice requires valid public privacy-policy and terms-and-conditions URLs for new A2P 10DLC campaigns submitted through its Messaging REST API from June 30, 2026; existing registered campaigns are not affected by that change.

This provider-specific rule illustrates why campaign ownership rarely belongs to marketing alone. Legal or compliance staff may control the disclosures, engineering may manage suppression events, customer support may receive ambiguous replies, and operations may own registration. One accountable owner still needs to keep those parts aligned with the live customer journey.

Use texting where timing justifies the interruption

Texting fits situations in which immediacy and brevity help the recipient: appointment reminders, delivery changes, account alerts, service interruptions and short support exchanges. Promotional messages require more restraint because they appear beside personal conversations and can quickly exhaust the permission a customer granted.

A well-scoped program has one recognizable purpose and one clear action. A reminder can offer confirmation or rescheduling; an order update can provide the current status; an offer can state its benefit and deadline without pretending to be a service notice. Combining unrelated programs merely to simplify list management makes consent evidence and opt-out scope harder to defend.

Transactional flows: keep the content tied to the event that triggered the message and avoid unrelated promotional additions.
Marketing flows: use recipients who joined that specific program, identify the sender and provide a practical way to leave.
Two-way support: route replies to a monitored queue and set accurate expectations when a human response is unavailable.
Internal alerts: maintain employee contact records and escalation procedures separately from customer-marketing lists.

Measure the intended result, not message volume

Delivery is not the same as attention, and attention is not the same as business value. Widely repeated claims that nearly every text is read or that SMS universally outperforms email often lack comparable audiences, campaign types and measurement methods. Those figures are too weak to justify a budget without evidence from the business’s own use case.

The relevant outcome might be confirmed appointments, completed pickups, resolved support conversations, qualified purchases or reduced call volume. Delivery failures, opt-outs, complaints and replies that received no support response belong beside conversion metrics. A campaign that generates short-term sales while rapidly losing subscribers may be consuming the permission it needs to remain viable.

Before launch, verify that each recipient joined the specific program, the consent evidence is retrievable, the sender route is registered where required, opt-outs propagate through connected systems and live messages match the promises made at sign-up. Business texting can still be direct and useful, but its advantage depends on treating permission and delivery infrastructure as core campaign requirements.

Business Texting Is No Longer Plug-and-Play: Permission Comes First