Devices & Agency · ASG Help
White-label and custom-domain setup
Plan a branded client experience without hiding the operational requirements of the underlying mobile gateway.
Before making production changes: exact screen names and platform behavior can change as GoHighLevel, Android, carriers, and the underlying messaging platform evolve. Test changes on a controlled deployment first.
Before changing DNS
Confirm the supported custom-domain instructions for your account and keep a record of existing DNS values.
Recommended rollout
- Configure branding first.
- Add the custom domain/CNAME exactly as instructed.
- Wait for DNS/SSL provisioning to complete.
- Test login, device connection, and client sub-account behavior under the custom domain before inviting clients.
If SSL or device recognition fails
Do not delete working DNS records at random. Capture screenshots and current DNS values, then contact ASG support so the custom-domain path can be validated.
Still not working? Contact ASG with the device name, carrier, GHL location, approximate timestamp, and the exact step that failed.