Display called number / number label on incoming call screen in LC Mobile App and Web Dialer (pre-answer)
L
Luc Pachan
Currently, when an inbound call arrives in the LC Mobile App or Web Dialer, there is no way for the agent to see which GHL number was dialed before answering. The incoming call screen shows the caller's number only. This has been confirmed as a feature gap by the GHL support team.
For sub-accounts with multiple inbound numbers (separate lines for different brands, departments, or campaigns), agents have no pre-answer context to know which line is ringing. This makes it impossible to answer with the correct greeting, brand, or script without building workarounds.
This gap hits smaller teams especially hard. When staff wear multiple hats and cover calls across different lines or brands, knowing which number was dialed before picking up is not a nice-to-have. It is the information that determines how they answer, whether they answer at all, or whether they intentionally let a call go to voicemail. Some lines are lower priority and can safely go to VM when a staff member is occupied. Others are high-priority lines where calls must be taken regardless of what else is happening. Without pre-answer visibility into which number was called, agents cannot make that call in real time. They are either picking up blind or letting everything go to voicemail to be safe, neither of which is a good outcome for the business or the caller.
The requested feature is a simple label on the incoming call screen showing either the called number or the number's configured name (the "Number Name" field that already exists in phone settings). Both the LC Mobile App and Web Dialer should surface this.
Whisper messages are not a substitute here. They fire after the call is answered, not before, so they cannot solve the pre-answer identification problem.
This would be immediately useful for any sub-account running multiple branded lines, ring groups by department, or call tracking numbers where agent context matters at the point of answer.
Log In
L
Luc Pachan
One more thing worth noting before someone suggests forwarding calls to personal cell phones as a workaround: yes, that does allow you to pass the called number as caller ID, so staff would see which line is ringing. But you lose call recording, accurate call status tracking, and reliable automation triggers off call outcomes....which for most sub-accounts defeats the purpose of having the numbers in GHL in the first place. A native pre-answer label in the app is the right fix, not pushing calls outside the ecosystem to compensate for a UI gap.