Start with the account and setup method
A screenshot saying “rejected” is not enough. Identify the affected subaccount, whether it uses LC Phone or a direct Twilio connection, and whether the failure belongs to the business profile, brand, campaign, or sending number.
HighLevel's current workflow includes Chat Widget Setup and Manual Setup. The required correction may differ between them. Record which method you used before changing forms or campaign details.
What we can investigate
| Situation | Review focus |
|---|---|
| A client cannot complete registration | Exact failing stage and missing or conflicting inputs |
| Campaign rejected after website changes | Whether the submitted evidence points to the updated live journey |
| Several client accounts show similar feedback | Shared template, copied description, or intake gap worth checking |
| An approved setup still fails to send | Actual sender and message-level evidence |
- Situation
- A client cannot complete registration
- Review focus
- Exact failing stage and missing or conflicting inputs
- Situation
- Campaign rejected after website changes
- Review focus
- Whether the submitted evidence points to the updated live journey
- Situation
- Several client accounts show similar feedback
- Review focus
- Shared template, copied description, or intake gap worth checking
- Situation
- An approved setup still fails to send
- Review focus
- Actual sender and message-level evidence
A scoped review can compare the submission with the public site, identify contradictions, and organize a correction plan. Website edits, account changes, resubmission, and ongoing support should be explicitly included in the agreed scope if needed.
Example: the form was fixed, but the rejection repeated
Imagine a client has a booking form and an older footer popup. Your team updates the booking form, but the campaign evidence still references the popup. Another resubmission now contains the same mismatch.
The useful next step is a URL-by-URL comparison: which flow is declared, which page is live, and which forms can actually enroll someone in messaging? This is an illustrative diagnostic example, not a client result or a promise that one change resolves every rejection.
What to prepare
Send the subaccount name, setup method, current statuses, complete rejection text, public form URLs, and a brief change history. Redact customer data from screenshots. Do not send account passwords.
For a team preparing a first submission, start with the GoHighLevel checklist. For repeated onboarding issues, see agency support and the client intake checklist.
Questions
Where do I find the detailed rejection?
HighLevel documents Settings → Phone System → Trust Center → Brands & Campaigns → Campaigns. Open the rejected campaign's “View required fixes” details for each reason. Interface labels can vary as the product changes.
Does a green platform check mean guaranteed approval?
No. A pre-submission check and an external registration decision are different things.
Can you work inside the subaccount?
Describe the access you need help with when requesting the review. Any account work and permissions must be agreed before access is granted.
What if I only need a rejection explained?
Share the complete feedback first. A rejection review may be the more focused starting point.
Official references
Provider rules change. Always confirm against the current official documentation.