GoHighLevel incoming call settings determine what happens when someone calls a business number. From the phone number configuration screen, you can choose who should receive the call, whether it should be forwarded elsewhere, and what should happen when nobody answers.
The important part is not simply enabling forwarding. The number, destination, timeout and fallback behavior should reflect a real business process. A sales number may need to reach an assigned representative, while a support number may need a shared answering process and a clear voicemail owner.
To manage these settings, open the correct sub-account, go to Settings, select Phone Numbers, edit the relevant number, and review its Incoming Calls configuration. Save the change, then test the complete call path from an external phone.
What GoHighLevel incoming call settings control
Incoming call settings are configured for an individual phone number inside a GoHighLevel sub-account. They define the first handling decision for calls placed to that number, such as routing the call to a user, forwarding it to an external number, or sending it to voicemail.
The available fields can vary by account configuration, permissions and product updates. Treat the visible settings as the current control surface for that number rather than assuming every sub-account has identical options.
A phone number should represent a clear business entry point, not an unexplained destination in the CRM.
How to open the correct phone number configuration
- Sign in to GoHighLevel.
- Open the relevant sub-account.
- Select Settings from the left navigation.
- Open Phone Numbers.
- Find the number that callers use and select its edit option.
- Locate the Incoming Calls section.
Before changing anything, verify the full number and its intended purpose. An account may contain separate numbers for sales, support, campaigns, locations or individual team members. Editing the wrong number can create a configuration that appears correct while having no effect on the calls being investigated.
How to configure incoming calls in GoHighLevel
1. Define the intended call outcome
Start by writing down what should happen when the call arrives. Avoid beginning with the available dropdowns. The operational question comes first:
- Which team or person owns the call?
- Should the caller reach a person immediately or leave a message?
- What should happen if the first destination does not answer?
- What information must be available after the call?
This distinction matters because a technically valid route can still produce a poor customer experience. For example, forwarding every number to one mobile phone may work during business hours but create unclear ownership, missed follow-up and no dependable fallback outside those hours.
2. Select the primary handling option
In the Incoming Calls settings, choose the option that matches the intended first action. Depending on the account and current interface, this may include routing to a GoHighLevel user, forwarding to an external phone number or sending calls to voicemail.
- GoHighLevel user or agent: Use this when the call should be associated with a specific user or internal answering responsibility.
- External number: Use this when a mobile phone, landline or another telephony destination must receive the call.
- Voicemail: Use this when callers should leave a message rather than wait for a live answer.
Do not choose a destination solely because it is convenient to configure. Choose the destination that has a named owner and a defined next action.
3. Configure forwarding details
If the selected option requires forwarding, enter or select the destination carefully. Review the number for typing errors and confirm that the intended recipient can answer calls from the relevant region and provider.
Some configurations may expose additional controls for ringing behavior or timeout. If those controls are available, use them to describe a deliberate sequence. For example, a call may ring the assigned representative first and then move to a shared fallback destination. The exact controls depend on the account, so verify the behavior with a live test rather than relying on the field labels alone.
A forwarding rule is incomplete unless the team knows who owns the call after the initial recipient misses it.
4. Configure voicemail and fallback behavior
Unanswered calls need an explicit outcome. If voicemail is enabled, check the greeting, confirm that the message is recorded, and identify where the team will review it. If the account provides a fallback setting, make sure it aligns with the working hours and ownership model for that number.
A fallback is not just a technical safety net. It is part of the service process. A support caller who reaches an unmonitored inbox has technically completed the call flow but has not received a reliable route to help.
5. Save and test the complete path
Save the configuration, then place an external test call. Test more than the first ring. Confirm the destination, the caller experience, the timeout behavior, the voicemail greeting and the location of any resulting message or call record.
Designing a reliable GoHighLevel call flow
Good call routing is a small operating system for inbound conversations. It connects a public number to a responsible team, a fallback and a follow-up action. The settings should therefore be documented in business terms, not only as technical values.
Number points somewhere
The number forwards to a person, but nobody knows why that person receives it, what happens when they are unavailable or who reviews missed calls.
Number represents a process
The number has a purpose, an owner, a fallback and a follow-up expectation that the team can explain and test.
Separate numbers by meaningful responsibility
Use separate numbers when callers have different needs or when different teams own the next action. Sales, support and location-specific calls may require different destinations and reporting. However, adding numbers without assigning ownership can make the system harder to understand.
For each number, record its purpose, primary destination, fallback destination, voicemail owner and last test date. This simple register helps prevent changes from becoming dependent on one administrator’s memory.
Connect call handling to CRM ownership
If a call creates or updates a contact, the follow-up process should identify who is responsible. A call route and a CRM assignment are related but not identical. The person who answers may not be the person who owns the opportunity, support issue or follow-up task.
Review this relationship when designing your wider CRM architecture and lead management process. The objective is not to automate every call event. It is to make the transition from conversation to accountable next step visible.
Call routing answers who receives the conversation. CRM ownership answers who is responsible for what happens next.
Common incoming call problems and how to diagnose them
The wrong person receives the call
Confirm that you edited the correct number and the correct sub-account. Then review the selected user or external destination. If several numbers exist, compare the caller’s dialed number with the number shown in the configuration screen.
The call never reaches the intended destination
Check the destination for transcription or entry errors. Confirm that the receiving user or device is available and that the external number can accept the call. If the route still behaves unexpectedly, repeat the test from a different external phone and record exactly where the flow stops.
Unanswered calls disappear
Review whether voicemail or another fallback is enabled. Confirm that the greeting plays, the message is saved and the team knows where to find it. A fallback that nobody monitors should be treated as unavailable.
The configuration works but the process still fails
This usually indicates an ownership or handoff problem rather than a routing problem. Ask who reviews missed calls, how quickly they act, where the outcome is recorded and what happens when the assigned person is absent.
- The correct sub-account and phone number have been verified.
- The number has a documented business purpose.
- The primary destination has a named owner.
- The fallback route has been enabled and tested.
- The voicemail greeting and message location are understood.
- A missed call has a defined follow-up action.
- The configuration has been retested after major workflow or team changes.
When to improve the wider system
If call settings keep changing because teams, locations or ownership rules are unclear, adjusting individual phone numbers will not solve the underlying problem. Map the call states first: new inbound call, answered call, missed call, voicemail received, follow-up assigned and outcome recorded.
Then decide which steps belong in GoHighLevel, which require a human decision and which can be automated safely. Automation should support an agreed process, such as creating a follow-up task after a missed call, rather than hiding uncertainty behind more notifications.
For broader routing, pipeline and integration work, systems, CRM and automation implementation services can help connect the phone process to the wider operating model. More tools do not automatically create better call handling. Clear states, visible ownership and tested handoffs do.
Frequently asked questions
Where are incoming call settings located in GoHighLevel?
Open the relevant sub-account, go to Settings, select Phone Numbers, edit the phone number you want to change, and review the Incoming Calls section.
Can GoHighLevel forward incoming calls to an external phone?
Depending on the account configuration, an incoming call can be forwarded to an external phone number. Verify the destination and test the route after saving the setting.
How should I test GoHighLevel call routing?
Call the number from an external phone, confirm the primary destination, allow the call to go unanswered, verify the fallback or voicemail behavior, and check where the call or message is recorded.
What should happen when nobody answers an incoming call?
The number should have an intentional fallback, such as voicemail or another responsible destination. The team should also know who reviews missed calls and what follow-up action is required.
Why is call ownership important in GoHighLevel?
Routing determines who receives a call, but ownership determines who is responsible for the next action. Without visible ownership, calls and voicemails can be missed even when the technical route works.
Make your call handling process easier to manage
If incoming calls, CRM ownership and follow-up tasks are becoming difficult to coordinate, ConsultEvo can help map the process, clarify responsibilities and improve the connected system.
