Start with the actual sending configuration
Keyword behavior depends on the provider and sender configuration. Review the current messaging policy and the settings for the number you plan to use. Record who is responsible for changes.
Twilio's messaging policy requires an accessible way to withdraw consent. Use its current documentation and your organization's advisers when reviewing the applicable requirements.
Test the recipient experience
Use an approved test contact to review the initial message, a help request, and an opt-out. Confirm the response and the resulting state in the workflow; do not rely on a label in a settings screen.
Check the path for a reply that does not exactly match a campaign keyword. A recipient still needs a useful way to ask a question or reach a person.
Keep the review connected to campaign operations
Document the test outcome and the team that owns the process. Revisit it when changing providers, numbers, or campaign flows.
Software configuration does not settle every legal obligation. Review your audience and use case with the appropriate advisers, and retain the records your organization needs.
Apply this topic to your next campaign
Check the current provider policy and review how the actual sender handles permission and preference requests. A historical article does not establish the requirements for your current program.
Questions for your campaign review
- Assign ownership for consent records and campaign review.
- Check the applicable provider requirements for your use case.
- Review preference handling and document the path for questions.
Use the guide as a starting point, then document the decision, the person responsible, and the result you will measure. Confirm product capabilities for your specific account before planning a rollout.
Primary provider reference: Twilio Messaging Policy. Review applicable legal obligations with a qualified adviser.