How to resubmit a rejected Twilio A2P campaign.
For an editable rejection, correct the existing campaign and resubmit it from Twilio Console. Preserve the campaign record instead of deleting it as your first troubleshooting step.
1. Confirm that a retry is appropriate
Open Messaging → Regulatory Compliance → Campaigns and select the failed campaign. Read the complete failure reasons. Some content-related rejections cannot be corrected through a routine resubmission; use the appeal or other route Twilio specifies. Twilio’s troubleshooting instructions explain the distinction.
2. Fix the customer-facing evidence
Use the rejection decision table to locate the issue. Update the actual opt-in page or policy first, then prepare working URLs or redacted screenshots. Keep the old and new versions in your own change record.
3. Make the campaign internally consistent
Check these four elements together: campaign purpose, message-flow description, sample messages, and public website. Each should tell the same story about the sender and the texts recipients chose to receive. A spelling change in one field will not fix a conflicting use case.
Purpose
Harbor Bike Repair sends appointment confirmations and reminders to customers who choose SMS reminders when booking a repair. This campaign does not send promotions.
Opt-in journey
A customer opens our booking page, enters a mobile number and selects the separate, initially unchecked reminder checkbox. The adjacent disclosure describes our reminder frequency and stop/help instructions and links to our SMS terms and privacy policy. The customer submits the booking and sees a confirmation.
Before using this: replace the fictional details and attach your actual page and policy URLs. Describe any additional consent path rather than copying a flow you do not operate.
Sample messages
Harbor Bike Repair: Your service appointment is confirmed for October 8 at 10 AM. Reply STOP to opt out.
Harbor Bike Repair: Reminder: your bike service is tomorrow at 10 AM. Questions? Contact the shop. Reply STOP to opt out.
4. Review the changed fields and submit
Open the campaign’s edit controls, correct the relevant description, sample messages and opt-in details, then use Update to request another review. Save a dated copy of the submitted values and campaign SID. Twilio currently says the vetting fee is assessed once per campaign; editing the same record avoids a second fee from creating a replacement. Check the current Twilio instructions before acting.
Keep a before-and-after submission record
Download the evidence worksheet (CSV). Put each rejection reason in its own row and attach its correction. Save a dated copy of the old and new application so a later rejection can be compared with the actual changes.
Need a fuller example? See purpose, message flow and sample messages side by side.
5. Track the result
- Record submission date, campaign SID and current status.
- Check the campaign’s status in Console.
- If rejected again, compare the new reason against the previous evidence sheet.
- If the reason cannot be reconciled with your evidence, contact Twilio with the SID, explanation and redacted screenshots.
A resubmission is a new review, not an instant approval. Avoid promising a launch date while the result is outstanding.
Final checklist
- Every reported failure reason has a documented response.
- Website, sender and sample messages match.
- All actual consent methods are explained.
- Evidence and policy links work without your login.
- No screenshots contain customer data or credentials.
- A copy of the corrected submission is saved.
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.