SMS onboarding checklist: what to prepare before business texting

1. Assemble a consistent business record

Start with the legal entity, customer-facing brand, store URL, business address, support contact, and the registration information your provider requests. Make legitimate relationships between legal and trading names clear. A working store and accessible policies help reviewers understand who is sending and what customers are buying.

Describe the actual products and services without disguising sensitive categories. Tell the provider where recipients are located and whether you need promotions, recovery, order updates, or support. Ask for the eligibility decision and permitted scope before purchasing a long-term plan. Acceptance of one message purpose should not be read as acceptance of every future campaign.

2. Write a concrete messaging-program description

Explain who sends, who receives, why the person receives the message, and how often messages are expected. Twilio’s onboarding guide uses these questions to distinguish a specific program from a vague claim such as ‘we text customers.’ Keep your campaign description aligned with the registered brand, selected use case, and samples.

For example, a hypothetical homewares store could describe opted-in promotional announcements separately from customer-initiated order support. A support question does not automatically authorize recurring offers. If several purposes are planned, ask the provider how they should be represented and which consent and registration requirements apply to each.

3. Capture each permission path from start to finish

Inventory every signup path and capture what the customer sees, chooses, and receives next. Include the form URL or evidence location, the invitation, disclosures, privacy and terms links, and the confirmation flow. For a private or prelaunch form, ask what evidence format the provider accepts rather than providing a link the reviewer cannot open.

Document how permission evidence will be retained and how an unsubscribe changes sending eligibility. Review imported subscribers before launch; an existing customer record or checkout phone field is not proof of permission for every message purpose. Use placeholders when sharing sample evidence so private customer details are not exposed.

• Show the sender identity and message subjects at the collection point.
• Check applicable consent choices, frequency, rates, help, and opt-out disclosures.
• Make current program terms and privacy information accessible.
• Record consent source, date, scope, and current suppression state.

4. Agree on the sender and prepare honest samples

Ask which sender type fits the permitted program and what registration or verification work is required. Confirm who supplies evidence, who submits it, which charges apply, and how status changes are communicated. A number purchase alone does not mean a sending program is ready. There is no single review timeline that applies to every business and route.

Draft representative messages with the actual brand, intended link domain, and clearly marked variables. Include the required help, confirmation, and opt-out messages for the workflow. Review segment counts on realistic final copy, including disclosures and long variable values, so the launch budget matches what you intend to send.

5. Define what happens when someone replies

Name the person or team watching conversations. Provide current store policies, approved answers, escalation contacts, and authority limits. Distinguish an agent answering a shipping question from changing an order or issuing a refund. Confirm inbox access and the handling of unanswered messages before inviting customers to text.

Your team can manage OneMoreSend text support, or discuss the additional $500/month managed option, with coverage Monday–Saturday, 8 a.m.–5 p.m. Eastern Time. Confirm conversation allowance, messaging charges, holiday handling, and scope in the quote. Publish accurate coverage information without turning a staffed window into an unagreed response-time guarantee.

6. Run a controlled launch review

Test with phone numbers your team controls and has authorized for the test. Walk through signup, confirmation where required, the permitted message, a reply, help, and opt-out. Verify that the opted-out record remains excluded from later campaign and automated audiences. Check failure reporting and confirm who will investigate an unexpected result.

If migrating, pause old automations before enabling replacements and reconcile recent opt-outs. Record the approved setup, launch owner, and stop conditions. Review the program again when products, consent forms, message purposes, or policies change. Onboarding is a documented starting point for operating the channel, not a permanent approval of every future message.

Common questions