Warm transfers to LC Phone numbers? | Voters

Warm transfers to LC Phone numbers?

planned

Brian Pappalardo

Hey there! You all just released warm transfers, which is great - but why can't we transfer to a LC phone number? The only option when we're transferring to a user is to transfer to their personal cell phone that they put in their profile settings. We really need to be able to transfer to their dedicated LC number instead.

Thanks!

May 8, 2025

Robert Segelquist

yeah, I have a team right now that's not very happy that the only transfer is to a cell phone, not to another web app user.

Brandon Allred

Please oh please!!!

Kelley Muro

NEED THIS! Once this is available we can stop using Open Phone.

Brian Del Terzo

This limitation creates real workflow challenges. Right now, the LC Phone number isn’t tied to the user record in a way that allows automations or workflows to reference it dynamically.
Using Custom Values as a workaround is cumbersome and error-prone, especially for appointment-related automations. For example, if an appointment is reassigned to another user, the workflow continues under the original Custom Value and ends up sending messages with the wrong phone number.
What’s really needed is a system-level field (or merge field) that allows the LC Phone number assigned to a user to be referenced anywhere {{user.phone}} can be, including automations, call routing, and warm transfers. This would resolve both transfer limitations and dynamic routing issues without having to hardcode numbers.
Excited to see this come to fruition!

Michael Taylor

Please prioritize this asap. This seems like a no brainer.

Ryan Kabel

Michael Taylor 100% agree.

Rosebell Bicar

Please vote for this post, will gather more community members to flood there to make GHL team realize they've been neglecting crucial privacy concerning features.

https://ideas.gohighlevel.com/lcphonesystem/p/enable-call-transfers-warm-and-blind-to-internal-user-in-the-same-subaccount-wit

Rosebell Bicar

Their phone system configuration is just for the lack of better term, sucks. imagine not being able to transfer a call within the same subaccount to another user on that subaccount because you would need to assign their personal number on their profile, which of course, would result to not just paying for 2 phone services, but if that personal phone assigned to the user's profile is not on the computer, they would have to pick up the call on a hard phone or mobile phone, which is extreme suffering for businesses that are customer service reliant AKA, contact centers.

In addition to this, you cannot even add all active users to received inbound calls using the default phone number, as there's a limit of 6 users only, which is not really a good limitation, and I don't see no benefits with them restricting us this much.

Brian Del Terzo

Rosebell Bicar  - I believe this can be addressed (at least temporarily) through the use of Custom Values for the scenario you described.
Create static Custom Values:
{{custom.LC_Phone_User_1}} = +12345678944
{{custom.LC_Phone_User_2}} = +12345678945
{{custom.LC_Phone_User_3}} = +12345678946
Use conditional logic in automations:
Calls for each user can then be routed or transferred to their respective Custom Value — for example, {{custom.LC_Phone_User_1}}, {{custom.LC_Phone_User_2}}, and so on.
Avoid referencing {{user.phone}}:
That field always pulls from the profile and can’t reference the LC number due to potential call loop conflicts. Instead, rely on the predefined LC Custom Values.
This workaround should cover most needs until GHL adds a true merge field for the assigned LC Phone number.

Ryan Kabel

Please prioritize this feature. Not having internal extensions and Ques Is challenging to use the phone feature as a complete replacement to other business phone systems.

CHEK Tech

Any update or ETA's on this?

Wagner Vieitas

Please get this prioritized. much love ghl team

→