Twilio campaign rejected? Find the fix before resubmitting.
Start with the exact rejection reason. Compare it with what a reviewer can see on your website and in your application. Correct the underlying mismatch, collect evidence, then resubmit if the rejection allows it.
First: is this a campaign rejection?
Record the campaign SID, status, error code and full explanation. A failed brand registration or a phone-number registration problem needs a different fix. Do not rewrite a campaign that is still awaiting review just because it has not been approved yet.
- BrandBusiness identity and registration details.
- CampaignMessaging purpose and consent evidence.
- NumberAssociation with the approved campaign.
Use the free diagnostic if you are unsure which path to follow. An approved campaign with a number still being configured needs a different investigation: see Twilio error 30035.
Match the rejection to the evidence
| Rejection | Check first | What to prepare |
|---|---|---|
| 30907 · Website mismatch | Does the website identify the same sender and service as the application? | A working business URL, consistent sender names and messages that fit that business. |
| 30909 · Unverifiable opt-in | Can someone follow the complete consent journey from your evidence? | The exact opt-in URL or accessible, redacted screenshots and a description of each step. |
| 30924 · Consent wording | Is the messaging purpose and disclosure visible where the person opts in? | The corrected form, including frequency, rates and opt-out information. |
| 30925 · Consent control | Is SMS consent separate and initially unchecked? | A screenshot of the untouched form and the action a visitor takes to opt in. |
| 30908 · Privacy policy | Does the policy explain messaging data handling accurately? | A public policy addressing SMS information and consent sharing. |
| 30897 · Disallowed content | Is the proposed activity allowed at all? | Review the content restriction. Do not simply rephrase and submit the same prohibited use case. |
A three-way decision
- The page is wrong: fix the real customer experience before changing the application.
- The page is right, but the application is vague: describe the actual flow and link the evidence.
- The business activity itself is restricted: check the specific restriction or appeal with Twilio. Wording changes do not make a prohibited activity eligible.
Work from one evidence sheet
Put four columns in a document: reviewer concern, current evidence, change made, and updated URL or screenshot. This makes it harder to fix the description while forgetting the live form.
Concern: the application says customers opt in on a booking page, but the submitted URL opens a homepage.
Fix: identify the actual booking form, verify its consent controls, and use that exact URL in the message-flow description. If the flow is private, prepare redacted screenshots that show the whole journey.
Download the evidence worksheet (CSV). Work through the 30909 evidence guide, privacy-policy audit or consent-control checks for a deeper correction.
Before you retry
Read every rejection reason, not only the first one. Test links without signing in. Compare the sender, purpose and sample messages side by side. Keep a copy of what you changed.
Next: use our opt-in page example or resubmission checklist. Twilio’s campaign troubleshooting guide explains which rejected campaigns can be edited.
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.