When GoHighLevel calls stop working, it's usually a setting, not an outage. Calls go to the wrong person because of the routing order, go to voicemail because of the timeout, don't ring the app because a checkbox wasn't saved, or drop in the browser because of a microphone or extension problem. Here's how to find the cause, in the order I check it for clients.
1. First, rule out an outage
Check status.gohighlevel.com. If phone services are affected, wait it out. If not, test with a simple call from your own mobile to the GoHighLevel number and note exactly what happens: no ring, wrong person, straight to voicemail, or a drop. Each points to a different setting. More in GoHighLevel errors and outages.
2. Where the phone settings live
Most fixes are in Settings > Phone System > Phone Numbers. Click the three dots next to the number and choose Edit Configuration. User-level settings are in Settings > My Staff: edit the user and open the Call and Voicemail Settings tab.
3. Understand the routing order
HighLevel sends an inbound call through these steps, and the first one that applies wins:
- IVR, a workflow or Voice AI set to answer calls directly.
- Owner-based routing: "Prefer forwarding calls to" the contact's owner or the phone number's owner.
- Team members, including anyone added under Ring More Team Members.
- The forwarding destination: an external or business phone number.
- The backup after the timeout: voicemail or Voice AI.
Most "calls going to the wrong person" problems come from step 2. If the caller is a contact with an assigned user, the call can go to that user instead of the person you expected.
4. Calls not ringing anyone
- Check that an IVR or Voice AI agent isn't answering first.
- Check the number is assigned to a user, or that Ring More Team Members includes the right people.
- In the user's Call and Voicemail Settings, check which devices are enabled: web app, mobile app, phone number or VoIP desk phone.
- Check the user has calling permissions.
5. Calls not ringing in the mobile app
- Go to Settings > My Staff, edit the user and open Call and Voicemail Settings.
- Under Forward Calls to, tick Mobile app and click Save. Unsaved changes are the most common cause.
- On the phone, allow microphone and notification permissions and let the app run in the background.
- On Android, turn off battery optimisation for the app.
The number must belong to the sub-account and be assigned to the user. Calls can ring on up to 10 devices logged into the same user, and answering on one stops the others. See the GoHighLevel mobile app guide.
6. Calls not ringing or dropping in the browser
- Allow microphone access for the GoHighLevel site in your browser.
- Open the dialer's Audio Settings and choose the right main speaker, microphone and optional additional ring device, then test and save. These settings are saved per browser, so set them on each computer.
- Temporarily turn off browser extensions and any VPN, then test again.
- Keep the GoHighLevel tab active. Browser memory-saving features that put tabs to sleep can stop incoming calls ringing, so exclude the GoHighLevel site from them.
7. Calls going straight to voicemail, or to the wrong voicemail
The Incoming Call Timeout controls how long the call rings before the backup takes over. HighLevel suggests about 20 seconds as a starting point:
- Too short and nobody has time to answer.
- Too long when forwarding to a mobile, and the mobile carrier's voicemail picks up before HighLevel's backup does.
- Very short (1 to 4 seconds) sends callers almost straight to the CRM voicemail, which some businesses do on purpose.
If your personal voicemail keeps answering, lower the timeout and test how quickly your carrier's voicemail kicks in. Also check that the backup is set to Voicemail or Voice AI, and that a voicemail greeting has been uploaded as an MP3 or WAV file.
8. Missed-call text-back not firing
This is the most expensive phone problem, because the missed caller never gets a reply. When calls forward to a mobile and the carrier's voicemail answers, the call can count as answered, so the missed-call workflow never runs. The fix is Call Connect (Edit Configuration > Advanced). It asks the person answering to press a key before the call connects, so only real human answers count. HighLevel recommends it for missed-call text-back. Then check the workflow itself: trigger, filters and that it's published. See missed-call text-back and workflow not working.
9. Calls that drop as soon as they connect
- Check the whisper message. A whisper message containing a broken custom value can make incoming calls drop. Simplify it or remove the custom values and test.
- Turn off extensions and VPNs if the drop happens in the browser.
- Calls disconnect automatically after two hours. That one is by design.
10. Outbound calls failing or showing as spam
- Check the Calling From number in the dialer and that the user has permission to call.
- Check the Outgoing Call Timeout isn't so short that calls end before anyone answers.
- If US calls show as "Spam Likely", complete the Trust Center steps (SHAKEN/STIR, CNAM caller name and Voice Integrity) and avoid high volumes of short calls from a single number. See what is 10DLC.
If calls work but texts don't, that's a separate problem: see GoHighLevel SMS not sending.
11. When to contact HighLevel support
If the settings above are right and the problem continues, contact support with the number, the time of a failed test call, the caller's number and what happened. Specific examples get answers much faster. See GoHighLevel support.
Want your phone system set up properly?
I'm Arslan Mumtaz, a software engineer who fixes and builds GoHighLevel phone systems: routing, timeouts, voicemail, Call Connect, IVR and Voice AI, with missed-call text-back that actually fires. An HVAC and plumbing company I built for recovered 89% of missed calls (case study). Start with a $97 audit, see GoHighLevel expert services, or check pricing.
Frequently asked questions
Why are my GoHighLevel calls going straight to voicemail?
Usually the Incoming Call Timeout is too short, the intended user or device isn't available, or an IVR or Voice AI is answering first. Start with a timeout of about 20 seconds and check which user and devices the call routes to.
Why isn't my GoHighLevel missed-call text-back working?
If calls forward to a mobile and the carrier's voicemail answers, the call can count as answered, so the missed-call workflow doesn't run. Turn on Call Connect in the number's advanced settings so only human answers count, then check the workflow is published.
Why don't calls ring in the GoHighLevel mobile app?
In Settings > My Staff, edit the user, open Call and Voicemail Settings, tick Mobile app under Forward Calls to and save. Then allow notifications, microphone and background activity on the phone, and turn off battery optimisation on Android.