An SMS opt-in page reviewers can actually verify.
A reviewer needs to see what people agree to and how they agree. A phone field alone is not the same as an SMS opt-in. Make the sender, messaging purpose and consent action visible together.
An annotated example
The following is an illustrative appointment-reminder flow for a fictional repair business. It is not a working signup form or an approval guarantee. Adapt it to the actual messages and consent process your business uses.
EXAMPLE · HARBOR BIKE REPAIR
Get repair appointment reminders
Mobile number: __________________
□ I choose to receive appointment reminders by text from Harbor Bike Repair. Up to 3 messages per appointment. Message and data rates may apply. Reply STOP to opt out or HELP for help.
SMS terms · Privacy policy · Contact the shop
Save reminder preference
- Specific purpose: appointment reminders do not silently include promotional offers.
- Affirmative choice: the square represents an unchecked SMS checkbox, separate from general terms acceptance. See Twilio’s consent-control guidance.
- Visible disclosures: the sender, message type, actual frequency, rates and stop/help instructions sit beside the choice. See Twilio’s consent-language guidance.
- Real destinations: underlined labels in this mockup must be working policy links on a production form.
Make the application describe this exact page
A useful description answers: where does the person start, which field do they fill, which choice do they make, and what confirms submission? Name every route you actually use; a web form description does not also explain a paper or verbal signup process. Twilio documents the requirement to describe all opt-in methods.
Privacy language must reflect actual practice
Twilio flags policies that omit required SMS data protections or allow messaging consent to be shared for third-party marketing. Review your real data handling before adding a promise to your policy. Link the policy directly from the opt-in experience. Read the privacy-policy rejection guidance.
Check the initial state and the completed journey
Open your form in a clean session. Record the unselected reminder choice, then show what happens when a visitor selects it and completes the form. Repeat at mobile width so evidence does not hide clipped text. This is a practical testing procedure, not a claim that the fictional form above has been approved.
For comparison, see the difference between consent language and controls. Download the evidence worksheet (CSV).
Evidence to capture
- The initial form with the consent control unchecked.
- The complete disclosure without cropped text.
- The policy destinations and visible business identity.
- The submission and confirmation steps.
- Any additional signup method used by this campaign.
Use dummy details and remove personal information from screenshots. Reviewers need the flow, not a customer list. If the live experience is behind a login, follow Twilio’s guidance on accessible consent evidence.
Run the mismatch check
If your form promises three appointment reminders, your example messages should be appointment reminders. If you also send discount offers, revisit the use case and the consent collected for those offers rather than hiding them under service updates.
When the page and application agree, continue with the resubmission checklist.
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.