GoHighLevel Call Transfers: Web, Phone & SIP Tutorial

For years, transferring a live call inside GoHighLevel meant one workaround or another, and most of them ended with a staff member's personal cell number stored in the system. That changed on June 10, 2026, when HighLevel shipped call transfers to web, phone, and SIP through Labs. A receptionist, a Voice AI agent, or anyone on the line can now hand a caller to a teammate wherever that teammate happens to be working: browser, cell phone, or desk phone.

This tutorial covers enabling the feature, running warm and blind transfers, what each destination type actually does, and the operational details agencies should know before rolling it out across client sub-accounts.

What shipped, and why it matters

The June 10 release solves two long-standing problems at once.

First, the personal number problem. Previously, routing a call to a specific human usually meant call forwarding to a real phone number, which for small teams meant personal cells living inside client accounts. The new transfer system rings a teammate's configured devices directly through the platform, so no personal number is stored, displayed, or required.

Second, the single-device problem. Transfers now ring every device a teammate has configured simultaneously: the web app in their browser, their phone, and any SIP desk phone. The recipient answers wherever is convenient, and the other devices stop ringing. For hybrid teams where someone is at a desk in the morning and mobile in the afternoon, the transfer just finds them.

Both warm and blind transfers are supported, on both inbound and outbound calls.

Warm vs blind: which transfer to use

The two modes serve different moments, and HighLevel's transfer documentation draws the line cleanly:

• Warm transfer keeps the original person on the line to introduce the caller and hand over context before dropping off. Use it for sales handoffs, escalations, and any situation where the caller repeating their story would hurt the experience.
• Blind transfer hands the call off immediately and disconnects the transferring party. Use it for simple routing: wrong department, quick reassignment, high-volume front desk work.

One rule applies to both modes: once the transferring party leaves the call, they cannot rejoin it. Warm transfer buys a moment of overlap, but the handoff is final either way.

Enabling call transfers in Labs

The feature ships through HighLevel Labs, so it is off by default and enabled at the agency level:

1. Go to Agency Settings, then Labs, then the Sub-Account tab.
2. Find Transfer calls to any device a teammate uses and toggle it on.
3. Select which sub-accounts get the feature. For multi-client agencies, the bulk action applies it across many sub-accounts at once.

Two setup details determine whether the rollout actually works:

For the phone-number side of the setup (buying numbers, assigning them, and A2P registration), the phone system guide covers the groundwork this feature builds on.

Running a transfer during a live call

With the Labs toggle on, the in-call flow works like this:

1. During any active call, open the transfer control and choose warm transfer or blind transfer.
2. Pick the teammate from the list.
3. Click Hold & Call. The caller goes on hold, and every device the teammate has configured starts ringing.
4. The teammate accepts on whichever device they answer first. On the web app, they see an indicator that the incoming call is a transfer before picking up.
5. On a warm transfer, make the introduction, then drop off. On a blind transfer, the system disconnects the transferring party as soon as the handoff completes.

The three destinations, explained

Web app. The teammate takes the call in their browser through the built-in softphone. This is the zero-setup option: anyone logged into GoHighLevel on desktop can receive transfers with no hardware and no phone number. The transfer indicator shows before they answer, so they know it is a handoff rather than a cold inbound call.

Phone. A standard phone number configured on the user's profile rings alongside the other devices. This suits field staff and anyone away from a desk, and because the routing happens platform-side, the caller never sees or needs the staff member's number.

SIP. Desk phones speaking the SIP protocol join the same simultaneous ring. Offices running dedicated VoIP hardware (common in medical, legal, and home-services businesses) can keep their handsets and still participate in platform transfers.

Current limitations to plan around

The Labs release has edges worth knowing before an agency rolls it out to clients:

• No re-transfers. A call that has already been transferred cannot be transferred again. Front-desk flows should route to the right person the first time rather than daisy-chaining.
• Device configuration is the gatekeeper. Teammates without a configured device do not appear in the list. Most "transfers are broken" complaints trace back to this.
• Mobile app support is rolling out. At release, HighLevel said mobile support for both sending and receiving these transfers would arrive within weeks. The separate mobile inbound transfer feature (HighLevel or LeadConnector app v3.97.3 and up) already handles warm and blind transfers of incoming mobile calls, so mobile-heavy teams have a working path today.
• No rejoining. As with all transfers, once the handoff completes the original party is out.
• Labs means moving parts. Features shipped through Labs are production-usable but still evolving, and HighLevel iterates on them quickly. Recheck the changelog before building client documentation around exact button labels or screens, because those details can shift between releases while the core behavior stays stable.

Where this fits in an AI-answered phone stack

The transfer release matters most in combination with Voice AI. An AI agent answering inbound calls needs a clean exit ramp for the conversations it should not handle: a qualified lead who wants a human, an upset customer, a complex scheduling exception. Transfers to web, phone, and SIP give that exit ramp a destination that always rings, without hardcoding anyone's personal cell into an AI workflow.

There is also a direct cost angle. Voice AI bills by the minute, so an agent that hands qualified callers to a human at the right moment spends less than one that talks through a long conversation itself. The Voice AI cost breakdown runs those numbers; the short version is that a well-placed transfer is one of the few levers that improves the caller experience and the bill at the same time.

For teams configuring the AI side of that handoff, the Voice AI setup guide covers escalation triggers: explicit requests for a human, repeated unanswered questions, and complaint keywords all make sensible transfer conditions.

Three routing patterns that work

The front desk pattern. One person or one Voice AI agent answers everything and blind-transfers by department. Because blind transfers disconnect the front desk immediately, the desk stays free for the next call. The one requirement is accuracy: with re-transfers unsupported, a misrouted call has to be redialed rather than passed along, so the routing script needs clear qualifying questions before the handoff.

The closer pattern. For sales teams, the person who answers qualifies the lead and warm-transfers hot prospects to a closer. The warm leg matters here: the introduction ("I have Maria on the line, she runs a six-location med spa and wants to talk implementation") means the closer opens the conversation with context instead of a cold restart. Deals move faster when the caller never repeats themselves.

The specialist pattern. Service businesses route by expertise: the plumber on call, the attorney handling intake that week, the technician who knows the account. Simultaneous ring across web, phone, and SIP is what makes this reliable, because specialists rotate between the office and the field, and the transfer follows them without anyone updating forwarding rules.

Whichever pattern fits, write it down per sub-account. The feature is simple; the routing decisions are where client rollouts succeed or stall.

Rollout checklist for agencies

A practical sequence for taking this to client accounts:

1. Enable the Labs toggle for one internal or test sub-account first.
2. Configure devices for every user who should receive transfers, and verify each shows up in the transfer list.
3. Place test calls covering all three destinations, warm and blind, inbound and outbound.
4. Document the client's routing rules: who gets sales calls, who gets support, what happens after hours.
5. Bulk-enable across the remaining sub-accounts and brief client staff on the answer-anywhere behavior, since desk phones ringing alongside browsers surprises people the first time.