Twilio 30909: fix an unverifiable opt-in before resubmitting.
For error 30909, compare your submitted explanation with the consent journey a reviewer can actually verify. Start with the evidence gap, then correct the description or the live flow.
Build an evidence map before editing
Open a blank worksheet. Give each signup route its own row. In one column, write what the application claims. In the next, record what a new visitor can see. A mismatch between those columns is your investigation list.
| Your route | Evidence to prepare | Question to answer |
|---|---|---|
| Public web form | Exact form destination and initial state | Does this URL open the promised form? |
| Signed-in experience | Redacted captures covering the journey | Can the reviewer understand it without a customer login? |
| Text keyword | Invitation, keyword and actual replies | What happens after the person texts the keyword? |
| Paper or other offline route | Blank collection material and explanation | What does the person agree to, and how? |
Twilio’s 30909 reference explains accessible evidence and message-flow requirements. If another specific code appears, check it too; a clear description does not repair a broken form.
Worked example: the evidence exists, but the link is wrong
Submitted: “Customers choose reminders on our website.” The evidence link opens a homepage with no booking form.
Actual experience: the customer opens a repair-booking page, chooses a slot and separately selects reminder texts.
Correction to prepare: identify the exact booking destination, record the consent step and confirmation, then describe that sequence. Attach the evidence destination you just checked.
This example demonstrates how to investigate a mismatch. It is not an approved application to copy. Your business may use different collection methods, message purposes and disclosures.
Run a signed-out review
- Open the submitted evidence in a fresh browser session.
- Start at the first step a new customer sees. Record any redirects or login prompts.
- Capture the complete relevant text at a readable size. A close-up of a checkbox may omit the sender or surrounding promise.
- Follow the linked policies. Check that they belong to the same business.
- Compare the resulting evidence with the actual application, line by line.
Use dummy details for demonstrations. Do not expose customer names, phone numbers, account identifiers or credentials in public evidence. Keep your private investigation notes separate from material submitted for review.
When there is more than one route
A complete web-form explanation should not stand in for a separate keyword or paper process. Inventory each route the campaign really uses, then check Twilio’s guidance on multiple opt-in methods.
Prepare the next submission
Download the evidence worksheet (CSV). Record each reported concern, your correction and its evidence. Use our message-flow example for structure and the resubmission checklist for the next step.
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.