The Pre-Send SMS Campaign Checklist

Use a release gate, not a last-minute review

A reliable SMS campaign checklist is a release gate: a documented sequence that must pass before a campaign leaves your platform. It protects more than legal posture. It catches operational failures that waste a send: a stale segment, omitted suppression rule, mismatched landing page, broken parameter, unapproved offer, or nobody assigned to watch replies. For a US business, the best checklist connects CRM data, messaging operations, customer experience, and measurement in one decision record.

Do not schedule a campaign because the copy is finished. Schedule it only after the audience, permission, exclusions, destination, measurement, owner, and rollback plan are verified together. The checklist below is designed for promotional and lifecycle sends, but transaction-focused teams can use the same controls with their own program rules.

For automated commercial texts, the FCC consumer guidance says written consent is required, while its rules also provide recipients a right to revoke consent through reasonable means. Build your workflow around those constraints, then have qualified counsel assess your specific program and state-law exposure. The FCC describes a one-time, non-marketing confirmation of revocation as permissible in defined circumstances; it is not a reason to continue the conversation. [1] [2]

Create one campaign packet before work begins

A campaign packet is the shared source of truth for the send. It prevents a marketing brief, a CRM export, and a platform configuration from drifting apart. Name one accountable owner, set a version, and retain the final packet with the campaign record. The table is deliberately compact: if a field cannot be completed, the send is not ready.

The SMS Campaign Checklist: ten pre-send gates

Run these gates in order. Early gates determine who may receive the message; later gates determine whether the experience is clear, measurable, and controllable. A green light should mean the evidence was checked, not that a stakeholder vaguely remembers seeing it.

1. Define the audience and the single job of the send

Write a plain-English segment definition before opening the campaign builder: for example, customers who purchased replenishable product X in the last 45 days, have not reordered, are opted into this promotional program, and are not in a current support escalation. Check the count against a reasonable expectation and sample actual records. Exclude employees, test numbers, recent purchasers where the offer would be irrelevant, and audiences already receiving a conflicting automation. This is where SMS engagement segmentation becomes a revenue and experience control rather than a targeting exercise.

2. Verify consent is specific, retrievable, and fit for this message

Do not equate a phone number, email subscription, or inbound customer-service text with permission for recurring promotions. Confirm the recipient's consent covers this sender and subject, and preserve the evidence. At minimum, make the source, timestamp, program or disclosure version, collection method, phone number, and later opt-out status retrievable. Twilio's policy requires prior express consent, proof of consent, and a match between consent and subject matter; its policy is not a substitute for law. [4] Use a durable SMS consent audit trail so an investigation does not depend on a screenshot.

3. Rebuild suppression at the moment of send

Suppression is a live decision, not a list you exported yesterday. Recheck global and program-level opt-outs, manual do-not-contact flags, revoked consent received through any channel, duplicates, invalid or reassigned numbers where your data process identifies them, and internal exclusions. The FCC rule says a recipient may revoke consent by any reasonable method that clearly expresses the wish to stop; it lists common reply words and prohibits a sender from designating an exclusive revocation method. Requests must be honored within a reasonable time, no later than ten business days under that rule. [1] Operationally, suppress immediately and reconcile every system before the next send.

4. Make the message recognizable, accurate, and complete

Put a recognizable sender identity where a recipient can see it without guessing. State the offer or update plainly, include material conditions needed to avoid a misleading impression, and give one primary call to action. Read the text on a phone-sized screen. Does the price, deadline, eligibility, inventory qualifier, or recurring-program language match the landing page and brief? If this is a first contact or ongoing program, apply the opt-out disclosure and program language your legal, carrier, and platform requirements call for. Twilio's policy, for example, requires initial-message opt-out language and clear sender identification, with stated exceptions for follow-ups in an ongoing conversation. [4]

5. Treat the link and landing page as part of the SMS creative

Open the final link from a mobile device or close equivalent. Confirm it resolves quickly, uses HTTPS, displays the correct offer, preserves required login or cart state, and has no location, inventory, or pricing mismatch. Preview it after final URL parameters are applied; a working base URL can still hide a broken campaign URL. Use a link domain customers can recognize and govern, rather than a mystery shortener that adds doubt. Our guide to branded links and SMS URL shorteners explains the trade-offs. Do not use a link to conceal prohibited content or a material condition.

6. Set tracking before the send, not during the debrief

Choose one primary outcome: completed purchase, booked appointment, qualified reply, or account action. Set supporting metrics: delivered volume, delivery failures, clicks when measurable, conversions, unsubscribes, complaints or negative replies, and incremental revenue where a defensible control exists. Add a unique campaign identifier to the message and destination, test that it reaches analytics, and record the baseline and attribution rule. If a discount code is the conversion key, test the code, eligibility, and redemption reporting. This is the foundation for credible ROI analysis, not a cosmetic dashboard.

7. Choose timing and cadence recipient by recipient

Set a send window using the recipient's local time when you can reliably determine it. Then check quiet periods, state-specific considerations identified by counsel, stated program expectations, contact history, and overlapping journeys. A nationwide 10 a.m. launch can arrive much earlier for part of the audience. Avoid stacking a broadcast on a cart, welcome, service-recovery, or replenishment flow unless the combined experience is intentional. Quiet-hour policies are distinct from consent, so document both decisions. Use the SMS quiet-hours guide to formalize the rule, then validate it against counsel's guidance for your footprint.

8. Run technical and rendering QA

Send a controlled test to approved internal devices and inspect the rendered message. Verify the sender, brand display, personalization fallback, character count and segmentation, encoding, link, opt-out behavior, replies, media if used, and landing-page analytics. Test edge cases: a missing first name, a segment-boundary recipient, an expired offer, an opted-out number, and a user who replies with a question rather than a keyword. Confirm the platform will not retry a rejected or suppressed recipient as a new campaign. If your program uses A2P routes, ensure its sender, use case, and campaign configuration align with carrier and platform setup before release.

9. Obtain approvals that are specific and timestamped

Approval should be a decision on a frozen artifact, not a thumbs-up in a chat thread. Route the final audience definition, count, copy, link, offer terms, planned window, and measurement plan to the accountable marketing owner. Involve legal or compliance when the program, claim, consent path, geography, or risk profile requires it; HVSMS can support implementation but does not give legal advice. Give operations authority to block a send for platform, data, or customer-experience reasons. Record who approved which version and when. For high-impact campaigns, require a second person to compare the platform configuration against the packet.

10. Assign monitoring, escalation, and a stop path

Before launch, name the person who watches delivery behavior and replies, the customer-service team that can answer questions, and the operator authorized to pause remaining messages. Set clear triggers: unexpected error rates, a broken destination, a pricing or eligibility mistake, an unusual opt-out or complaint pattern, or a message mismatch. Document the provider escalation contact and route for legal or leadership review. CTIA describes its Messaging Principles and Best Practices as voluntary industry best practices intended to protect consumers from unwanted messages; they inform deliverability and trust but are not themselves a statute. [3]

At launch, control the first hour

Do not treat the scheduled time as the finish line. Use a staged launch or representative seed group when sensible, then inspect the live experience before broader volume progresses. Keep the campaign packet, final copy, audience logic, link, dashboard, and escalation contacts open in one view. If a meaningful issue appears, pause first and diagnose second; a fast pause is cheaper than explaining a preventable error at scale.

• Confirm the sender and message body match the approved version.
• Open the live destination and verify the campaign parameters, offer, and inventory state.
• Watch delivery exceptions, carrier or platform alerts, inbound replies, and opt-outs.
• Check that customer-service owners can see the campaign context and response guidance.
• Pause, document, and escalate when a predefined trigger is met; do not improvise eligibility or consent fixes mid-send.

Turn every send into a better operating system

Complete the review while evidence is available. Compare delivered volume with the approved audience count, reconcile rejects and suppressions, inspect replies and opt-outs, and verify that link and conversion data arrive as expected. Report against the pre-stated objective and baseline, not a retrofitted success story. Then record the change for the next send: a clearer segment rule, an earlier approval deadline, a stronger fallback, a better customer-service macro, or a new exclusion.

1. Archive the final packet, approvals, audience logic, consent evidence reference, creative, and performance snapshot together.
2. Classify failures by data, policy, creative, platform, timing, or process so the remedy has an owner.
3. Update suppression and customer records promptly from opt-outs, replies, refunds, support issues, and complaint signals.
4. Feed the insight into segment and cadence rules, including routine SMS list hygiene, before the next campaign is planned.

A checklist earns its place when it is revised after real incidents and wins. Review it quarterly with marketing, CRM, support, data, and compliance stakeholders. Keep the legal floor, carrier or platform requirements, and conservative operating standards in separate fields so a policy update or counsel decision can be implemented without rewriting the process.