Messaging · ASG Help
Understand message and delivery status
Use activity status to diagnose whether a problem is in GHL, ASG, the Android phone, or the carrier.
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.
Think in layers
- GHL/workflow created the send request.
- ASG/integration passed the request to the connected gateway.
- The Android device attempted to send through the carrier.
- Carrier/network delivery information may become available depending on the supported route.
When troubleshooting
Record the contact number, timestamp, device, GHL location, and status shown at each layer. This is much more useful than reporting only “SMS did not work.”
Carrier reality
A platform success state does not guarantee the recipient read the message, and carrier filtering can occur outside ASG control.
Still not working? Contact ASG with the device name, carrier, GHL location, approximate timestamp, and the exact step that failed.