Twilio campaign description and message-flow examples.
Write the purpose, message flow and sample messages as one consistent story. Start from what the business actually sends and how people choose it. Use the example below as a structure, not an application to paste unchanged.
One business, three connected fields
Illustrative scenario: Harbor Bike Repair offers appointment reminders during booking. It does not use this fictional campaign for promotions. The URLs below use the reserved .example domain and must be replaced with real, verified destinations.
1. Campaign purpose
Harbor Bike Repair sends booking confirmations and appointment reminders to repair customers who select SMS reminders. This campaign does not send discount offers or other promotions.
2. Message flow
The customer opens https://harborbike.example/book, chooses a repair appointment and enters a mobile number. They separately select the initially unchecked SMS-reminder choice, then submit the booking. The adjacent disclosure identifies Harbor Bike Repair, explains the reminder program and its frequency, and provides rate, STOP and HELP information. The form links to https://harborbike.example/sms-terms and https://harborbike.example/privacy. A confirmation screen records the saved reminder preference.
3. Sample messages
Harbor Bike Repair: Your repair appointment is booked for Tuesday at 2 PM. Reply STOP to opt out.
Harbor Bike Repair: Reminder: your repair appointment is tomorrow at 2 PM. Need help? Call the shop using the number on your booking confirmation. Reply STOP to opt out.
What to replace—and verify
| Example element | Your investigation |
|---|---|
| Appointment reminders only | Do actual messages also contain promotions? Select and describe the genuine use case. |
| Booking form | Is that really where consent happens? Include any other active routes. |
| Unchecked reminder choice | Does the live form behave that way in a clean session? |
| Policy destinations | Replace example URLs with public links that actually work. |
| Confirmation screen | If yours differs, describe what really happens instead. |
Twilio’s business-information reference explains the campaign fields and alignment of samples with the declared use case. Its onboarding guide adds submission requirements. Check those before using the structure.
A useful mismatch exercise
Imagine adding “20% off all accessories this weekend” to the samples above. The campaign now tells two stories: its purpose promises appointment reminders, but the sample sells products. Do not hide that contradiction by renaming an offer a reminder. Revisit the real use case and consent process.
Prepare a review sheet
- Paste your actual purpose, flow and samples into adjacent columns.
- Underline every claim about the visitor’s actions.
- Attach evidence for each claim.
- Flag statements that are only planned, not live.
- Correct the actual experience and application together before resubmitting.
Use the 30909 evidence guide when the consent journey cannot be verified. Use the resubmission checklist after resolving the inconsistencies. No example guarantees reviewer approval.
Sources and review method
Official Twilio references are linked beside the instructions they support. Worked examples are illustrative, not customer outcomes. Read our editorial method or use the free diagnostic.