On this page
1. Confirm the account and ownership
- Identify the client subaccount and actual sending business.
- Record whether the setup uses LC Phone or direct Twilio.
- Assign an owner for client facts, website changes, and submission.
- Record whether the chosen workflow is Chat Widget Setup or Manual Setup.
For missing client facts, use the agency intake checklist.
2. Check the evidence as one record
| Item | Pass condition for your team's review |
|---|---|
| Business facts | Source records identified; unanswered identity questions resolved |
| Public website | The submitted address opens and represents the sender |
| Enrollment | The declared journey is the journey people actually use |
| Policies | Current, accessible, and consistent with the business practices |
| Campaign | Purpose and examples agree with the actual message plan |
| Feedback | Every known rejection reason has an owner and resolution record |
- Item
- Business facts
- Pass condition for your team's review
- Source records identified; unanswered identity questions resolved
- Item
- Public website
- Pass condition for your team's review
- The submitted address opens and represents the sender
- Item
- Enrollment
- Pass condition for your team's review
- The declared journey is the journey people actually use
- Item
- Policies
- Pass condition for your team's review
- Current, accessible, and consistent with the business practices
- Item
- Campaign
- Pass condition for your team's review
- Purpose and examples agree with the actual message plan
- Item
- Feedback
- Pass condition for your team's review
- Every known rejection reason has an owner and resolution record
These are team review gates. The provider still performs its own review.
3. Test the behavior
Submit a controlled inquiry without choosing SMS. Inspect whether the workflow respects that choice. Test the intended consent category separately and confirm that the right automation is selected. Use your own test records and remove them from production lists afterward.
For platform-generated widget flows, follow the relevant current instructions rather than replacing generated fields with a copied manual-form template. Also inspect other live forms that collect messaging consent.
4. Save the submitted version
Keep the submission date, campaign description, sample messages, evidence URLs, setup method, and a dated review record. If a rejection follows, you can compare what was submitted with what is now live.
5. Verify readiness after approval
Record the approved campaign and relevant sender status. Check the actual number used by workflows and conduct a limited consented delivery test. Treat a successful test as evidence of that test, not a universal deliverability guarantee.
Worked handoff example
A team member marks the website reviewed but has only checked the homepage. The next person submits a popup URL. Prevent this by recording the exact URL beside every completed check and naming the person who checked it.
Questions
Is this the same as the client intake checklist?
No. Intake collects facts and evidence; this checklist evaluates the assembled submission and behavior.
What if an item is unresolved?
Assign an owner and pause the dependent submission step. Do not fill the gap with invented facts.
Can I reuse the checklist?
Yes, as a process. Recheck each client's facts, URLs, and actual program instead of copying the answers.
Request GoHighLevel help or a website and consent audit.
Official references
Provider rules change. Always confirm against the current official documentation.
Get a clear next step for your A2P 10DLC issue
Whether you are troubleshooting one rejected campaign or trying to create a more reliable A2P process across multiple GoHighLevel sub-accounts, start with the evidence and the actual failure point.