ASG setup philosophy: get the gateway online, verify GHL routing, test inbound and outbound messages, confirm opt-outs, then warm up and scale gradually.
1. Before you start
- A compatible Android phone running Android 8.0 or newer. A newer dedicated device is preferred for production.
- An active carrier SIM with SMS service and a plan appropriate for legitimate business messaging.
- Stable Wi-Fi or mobile data plus continuous power.
- GoHighLevel account access with permission to connect the intended locations.
- Your ASG onboarding credentials and assigned plan/device capacity.
2. Connect the Android gateway
- Use a dedicated Android device whenever possible.
- Install the ASG companion/gateway app supplied during onboarding.
- From the ASG dashboard, open the device connection screen and pair the phone using the provided connection method.
- Allow the permissions required for SMS transport and device connectivity.
- Disable aggressive battery optimization for the gateway app so Android does not suspend it.
- Confirm the dashboard shows the device online before continuing.
Tip: keep the phone on a quality charger in a ventilated location. For permanent deployments, consider a small UPS for short power outages.
3. Connect GoHighLevel
- Open the Integrations area in your ASG account.
- Choose the GoHighLevel connection option and authorize your GHL account.
- Confirm the locations you intend to support.
- Map the intended phone/SIM resource to the supported location configuration.
- Do not assume a specific dual-SIM-to-location layout until it has been tested.
4. Run launch tests
✓ Manual outbound SMS
✓ Inbound reply
✓ GHL workflow SMS
✓ Conversation reply routing
✓ STOP opt-out
✓ START resubscribe
✓ Device reboot/reconnect
✓ Wi-Fi loss/recovery
5. Configure the messaging toolkit
Depending on your deployment, you can use scheduled campaigns, message templates, contact groups/tags, custom variables, drip sequences, keyword data collection, automatic link shortening with click tracking, missed-call text-back, AI-assisted replies, knowledge-base content, REST API access, and webhooks.
Keep client-facing workflows simple at first. Add advanced features after your core send/reply path is stable.
6. Dual-SIM guidance
Compatible Android hardware can expose more than one SIM resource. The platform can support SIM selection, but exact routing and GHL location mapping should be tested before you promise a specific client topology. Treat dual SIM as added flexibility, not an automatic “two clients per phone” guarantee.
7. Production checklist
- Device name and physical location documented.
- SIM/mobile number and carrier documented.
- GHL location assignment documented.
- Opt-out handling verified.
- Carrier acceptable-use terms reviewed.
- New number warmed up gradually.
- Daily/weekly device health check assigned.
- Support escalation path known by the agency team.
Need help with a specific problem?Open Knowledge Base