Start with the exact provider reason. One rejection can expose a second mismatch, so repair the evidence and reread the complete campaign before taking the next action.
Read every reason
HighLevel exposes required-fix details for rejected campaigns. Twilio publishes code-specific guidance. Record every code and category before editing, and do not resubmit a campaign that the provider marks ineligible.
Match the category to proof
Common correctable categories include an invalid or inconsistent website, an incomplete opt-in description, a vague campaign description, missing policy links, unrealistic sample messages, and a mismatch between brand records and campaign identity.
- Website issues: make the business identity and consent path public and reviewable.
- Opt-in issues: show who consents, where, how, and what follows.
- Description issues: match the selected use case and actual message content.
- Sample issues: name the sender, reflect the use case, and avoid unsupported link behavior.
Repair the public evidence
A text edit inside the portal is not enough when the cited website still disagrees. Open every submitted URL in a private browser, confirm the legal business identity is visible, and verify that consent, privacy, and terms can be reviewed without login.
Resubmit only when eligible
Correct all listed issues, then review the entire campaign. Some fields can be locked and some rejection categories cannot be resubmitted under the same campaign. Follow the provider’s required-fix instructions rather than creating blind duplicates.
Work through the filing
- 01
Capture every rejection reason
Record the provider code, category, explanation, and requested correction for the campaign.
- 02
Fix the underlying proof
Update the live website, consent flow, policy pages, or business records that caused the mismatch.
- 03
Regenerate aligned copy
Update the description, message flow, samples, and policy URLs so they all describe the corrected evidence.
- 04
Review eligibility and resubmit
Confirm the provider allows resubmission, resolve every reason, and follow the displayed workflow.
Questions
Should I create a new campaign immediately?
No. Read the required fixes first. A pending campaign should be left for review, and some rejected campaigns can be corrected and resubmitted.
What if the provider reason looks wrong?
Use the provider’s appeal or support path and include the campaign identifier, business name, error details, and supporting evidence.
Can A2PReady review the rejection notice?
Yes. Send the full notice through the contact page. A2PReady can help organize a repair, but cannot override a carrier decision.
Provider sources
- HighLevel: A2P Campaign Rejections, Required Fixes & Vetting Errors
- HighLevel: Campaign Rejection Reasons and Resolutions
- Twilio: Why Was My A2P 10DLC Campaign Registration Rejected?
Source links point to HighLevel and Twilio provider documentation. Check the current version before filing.