Twilio 30924 and 30925: fix consent wording and controls.
Check both the words and the action. Error 30924 concerns consent language; 30925 concerns affirmative consent, including a website control that starts unchecked. Correcting only the paragraph will not fix a preselected checkbox.
| Code | Inspect | Useful evidence |
|---|---|---|
| 30924 | What the person is told about the messages | Complete, readable disclosure at the consent step |
| 30925 | How the person actively chooses messaging | Fresh form state and the separate consent action |
Test wording and behavior separately
Make two passes through the form. First read it without clicking anything. Could someone explain what they are agreeing to? Then use it as a new visitor. Is the messaging choice already selected, or mixed into acceptance of general terms?
Problem A: “Keep me updated” next to an empty checkbox. The control may be clear, but the message promise needs investigation.
Problem B: a detailed messaging disclosure next to a checkbox that is already selected. More words will not fix the initial selection.
Our review method: put a separate finding in the worksheet for each issue. Assign each finding a correction and a proof image so one fix does not obscure the other.
For a language concern
Compare the message type, frequency, rate notice and stop instructions with Twilio’s current 30924 instructions. Capture the text as the visitor sees it, not only in the website editor. Then compare that promise with your campaign purpose and sample messages.
For a control concern
Open the form fresh and check its initial state. Twilio calls for a separate, affirmative messaging choice rather than a preselected control or general terms acceptance. Show the whole relevant step, including policy destinations. Follow the 30925 instructions for evidence when the flow is private.
Check the second visit too
Our practical testing checklist: try a clean browser session, a mobile screen and the alternate booking route if there is one. A corrected homepage form is not enough if the actual campaign sends people through an older embedded form elsewhere. Record which routes you checked; do not claim coverage of routes you did not inspect.
Prepare a coherent correction
- The visitor-facing promise matches the actual messages.
- The initial choice and the action are documented.
- The application describes the corrected flow.
- The evidence shows the live version, not a stale draft.
See our annotated opt-in example and campaign-field example. Download the evidence worksheet (CSV).
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.