Master Sub-Account + Snapshot + A2P
Create a practice workspace, load its assets, and prepare applicable messaging registration.
Why this matters
A snapshot is a template. Numbers, payments, calendars, business facts, and public pages still need configuration. A2P 10DLC concerns business SMS/MMS through standard US local numbers to US recipients. Voice calling and website chat can be configured and tested separately.
Before you begin
- Agency access and an available location slot.
- Snapshot eligibility, or native templates to build from.
- Real sender details and public website/consent information if messaging is included.
Finish with this
Loaded practice assets, accurate public pages, and a recorded messaging status.
Use the checks below to record actual work. They do not certify third-party approval or client results.
Do this and verify
Loading your checklistβ¦
Check an item after you do it or document why that channel is outside your agreed scope. Reading a phase does not complete it.
This bonus is only available if you signed up for your GoHighLevel account through our link above.
Matching tools
Use these to prepare drafts and estimates. Complete actual configuration in the correct HighLevel location.
Instructions and examples
Import, load, customize, verify
| Action | Where | Success check |
|---|---|---|
| Import | Agency snapshot library via shared link | Named snapshot appears in library. |
| Load | Agency β Sub-Accounts β Manage β Actions β Load Snapshot | Expected assets appear in intended location. Review overwrite/conflict selections. |
| Customize | Location settings, pages, agents, calendars, workflows | Real values replace placeholders; needed integrations are connected. |
| Verify | Public pages and test interactions | Correct facts plus actual contact, booking, and notification outcomes. |
Check the selected location and whether you loaded the snapshot after importing. Look under that location's Sites/Funnels. Record missing assets and ask for help before overwriting existing work.
Custom values do not always populate imported pages. Preview every public page and remove bracketed placeholders, raw {{custom_values}}, wrong business names, and demo contact details. Save and publish edits, then test the public links. A legal template does not guarantee approval or compliance.
Register the actual messaging sender
- Check number type and destination country. A2P 10DLC does not apply universally to toll-free numbers, every country, voice, or web chat. Other routes can have separate verification.
- Use the real sending business and the provider route matching its actual status. Do not register every Trust Center option by default. Do not substitute an SSN for a required business registration identifier.
- Prepare accurate public business/contact details, appropriate policies, and a clear opt-in flow describing sender, purpose, frequency, applicable charges, and opt-out/help instructions.
- Follow the location's current Phone System/Trust Center brand/campaign process, with real sample messages and a truthful explanation of consent. Check fees before submission.
- A preliminary AI review is not carrier approval. Record status, read rejections, correct the issue, and use the documented resubmission route.
- Keep dependent SMS paused while pending. A practice registration does not approve future client brands. Approval does not give permission to cold-text a prospect list.
- For approved messaging, test with an opted-in recipient. Check delivery, STOP suppression, and owner notifications.
Register the real business and actual use case. Do not use a fictional or unrelated website to disguise restricted activity. If unsupported, follow the platform's documented guidance rather than changing the business identity.
Common places to get stuck
- Loading blindly into an active client location.
- Assuming a library import makes assets live.
- Using fictional or unrelated business details to obtain approval.
Your next action
Build and test in Phase 5. Keep SMS paused where approval or consent is outstanding.
If blocked, note this phase, account view, location, expected/actual result, and a redacted screenshot. Use your available community/support channel. Menu names can change; confirm the right view before changing a plan.
Written instructions reviewed October 8, 2026. Official links are the reference for current prices and requirements. Older recordings may show different menus or terms.