Prepare SMS marketing around a defined audience, a clear reason for contact and an opt-out route the recipient can use. Keep the permission record connected to the intended message subject and sending arrangement. Use the worksheet below to review copy, suppression handling and responsibility before authorising a campaign or changing an automated messaging workflow.
Who should receive this particular message?
Write the campaign purpose in a sentence and identify the people for whom it is relevant. Separate a promotional audience from an operational notification list. Ask which record establishes the intended recipient and which evidence supports contact for the proposed subject and channel.
For promotional messages, Twilio requires prior express written consent from the recipient. Documentation. Twilio requires retaining evidence of recipient consent. Documentation. Treat these as provider requirements alongside the applicable obligations for the actual business, destination and sending arrangement. Have the responsible organisation establish those requirements before configuring the workflow. Keep the relevant evidence reference with the audience selection rather than relying on a general assumption that an existing telephone number is usable.
Twilio requires prior express consent for informational messages about an action or transaction the recipient has taken or agreed to. Documentation. Twilio informational messages must not market or promote a product, service or cause. Documentation. Twilio treats an individual’s inbound message as consent and proof of consent for the direct exchange. Documentation. That inbound exchange does not provide consent for ongoing recurring engagement. Documentation. Twilio requires consent from each recipient for each sender and message subject. Documentation. Keep the written-consent evidence for a promotional audience tied to this sender and subject; do not reuse a service receipt or a reply to an hours enquiry as marketing permission.
Twilio prohibits buying, selling, renting or transferring consent. Documentation. Review the source of an imported list and the meaning of its permission fields. If a record is unclear, assign it for resolution before audience selection. A cleaned spreadsheet can improve formatting without establishing the original person’s choice or the intended scope of contact.
What should the message make clear?
Twilio requires clear sender identification except for follow-ups in an ongoing conversation. Documentation. Start with a recognisable sender and a relevant purpose. Write the message so the recipient can understand why it arrived and what the proposed next action is. Keep claims about offers, availability or deadlines tied to the business’s actual approved information.
Twilio requires a straightforward, single-step opt-out process. Documentation. Twilio requires the initial message to include “Reply STOP to unsubscribe” or an equivalent standard opt-out keyword instruction. Documentation. After opt-out, Twilio permits one final confirmation and prohibits subsequent messages. Documentation. Messaging an opted-out recipient again requires their subsequent express written consent. Documentation. Include the explicit initial-message instruction in the approved copy and review the entire recipient journey. Ask what happens when someone follows the instruction and how that choice reaches the system selecting the next audience. Keep the copy and the technical handling in the same acceptance discussion.
Review links and destination content together. If the message points to a service or booking page, make the destination consistent with the message’s promise. Ask a colleague to follow the proposed route using controlled test details and identify any confusing change of context before release.
An original campaign-permission worksheet
Use this practical checklist for a proposed campaign. Fill it with actual audience rules and evidence references. The table helps the business owner and implementer review the same decision before any recipient is contacted.
| Campaign boundary | Information to record | Question before authorisation |
|---|---|---|
| Purpose | Specific subject and intended outcome | Why is this message relevant to the audience? |
| Recipient evidence | Message type, sender, subject and consent record | Is prior express written consent evidenced for this promotion? |
| Sender | Business identity and configured sending route | Will the recipient recognise who contacted them? |
| Copy | Approved wording and linked destination | Are the promises accurate and understandable? |
| Opt-out | Initial STOP instruction and actual handling route | Is final confirmation followed by suppression until renewed written consent? |
| Suppression | Preference record used during audience selection | What excludes an opted-out recipient? |
| Ownership | Approver, operational contact and investigation route | Who resolves an exception before another send? |
Add the exact campaign version and audience-definition reference. Keep the recipient evidence separate from the message content so a revised campaign can be reviewed without losing the basis for the selected audience. Preserve the decision that authorised the particular send through the organisation’s normal process.
Define the point at which the audience is checked against the latest preferences. Ask how the proposed system handles a withdrawal arriving after an initial audience export. Keep that question explicit rather than assuming that a list prepared earlier remains appropriate indefinitely.
How should automated opt-out handling be assessed?
Twilio Advanced Opt-Out supports custom opt-in, opt-out and help messages. Documentation. Twilio matches Advanced Opt-Out keywords without case sensitivity. Documentation. Use the actual provider and sender configuration when preparing a controlled rehearsal. Include the intended keywords and the confirmation text, then record what the recipient and the application each receive. Keep case variations and ordinary wording in the proposed test cases where relevant.
Twilio adds a number to a blocked list when it receives an opt-out keyword. Documentation. Twilio can report matched keyword events using OptOutType in the configured webhook request. Documentation. Follow the preference event into the application’s own record and the next audience-selection decision. Ask the implementer to show which component receives the event, how it is processed and who investigates a failure. The useful question is whether the next intended contact decision uses the current preference.
Enabling Twilio Advanced Opt-Out applies its configuration to every sender in that Messaging Service’s sender pool. Documentation. List every affected sender and review the shared keyword and confirmation settings with their owner before activation.
Disabling Twilio Advanced Opt-Out after enabling it requires contacting support. Documentation. Review the configuration and change route with the authorised account owner before activation. Keep the proposed settings and acceptance checks ready for approval, including the person responsible for contacting support if the arrangement later needs to change.
Hypothetical example: a recipient opts out after the list is exported
Imagine the marketing team prepares an audience file, then a recipient sends the configured opt-out keyword before the campaign is dispatched. The sending workflow now needs to use the current preference rather than only the earlier export. This hypothetical case tests the boundary between audience preparation and actual sending.
Prepare a controlled recipient with recorded permission for the test sender and subject. Include the initial STOP instruction in the test copy. List all senders affected by the selected Messaging Service configuration, then record the sequence of events. Follow the keyword response, any single final confirmation, the application preference and the proposed final audience check. Confirm that the proposed campaign excludes the opted-out recipient and that a route for later contact requires subsequent express written consent. Write the expected outcome before running the rehearsal, then retain the actual observation against the workflow version.
If a handover fails, identify where the preference stopped progressing. Assign the exception to a named owner and keep the affected recipient outside the proposed campaign while the record is resolved. The recovery decision should be understandable from the event and campaign references without reconstructing the whole workflow from memory.
Which measures make the next campaign more useful?
Choose measures tied to the campaign’s actual purpose and the recipient experience. Record delivery observations, relevant responses, opt-out handling and the quality of the resulting enquiries using the provider’s actual definitions. Keep a delivered status distinct from a claim about what a person read or understood.
Review recurring confusion in replies alongside the message copy and destination. If recipients repeatedly ask the same basic question, improve the information or audience rule before increasing volume. Retain the evidence supporting that change so later comparisons remain interpretable.
For channel selection, see WhatsApp Business. Discuss the audience journey and destination through web development and get started with the campaign purpose, permission records and suppression handover you need to assess.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.