Warm transfers to LC Phone numbers?
in progress
B
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!
Log In
E
Eddy CEO WhatSnap.ai - Connect YOUR phone to GHL
Same issue here. Our team won't give out personal numbers so warm transfers are basically useless right now. Need the transfer to ring their LC app or browser, not their cell.
Ronak Jindal
marked this post as
in progress
P
Phill Crawley
Come on GHL! This feels like we are stuck in the past, this should be a standard feature I cannot simply transfer to another user's web or mobile app, I can only transfer to their personal mobile phone number, which none of our staff wants (for obvious reasons). It should also respect the users availability settings too eg don't ring the users mobile app if it is outside their work hours.
A
Alfred Hanna
BUMP. Please add an option to transfer calls internally to other staff members. We do not want to transfer to our staff mobile numbers. This is not allowed through our company policy and must be done internally. Same as how GHL added an internal chat that stays within the GHL web app, we want the same for calls.
R
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.
B
Brandon Allred
Please oh please!!!
K
Kelley Muro
NEED THIS! Once this is available we can stop using Open Phone.
P
Phill Crawley
Kelley Muro Is this a workaround? if so does it allow you to transfer to other users on the sub account?
B
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!
M
Michael Taylor
Please prioritize this asap. This seems like a no brainer.
R
Ryan Kabel
Michael Taylor 100% agree.
R
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.
Load More
→