Phone System

One of the most important times we need the IVR feature is when someone calls from the website which uses a number pool. Without this functionality the IVR feature loses half its value.

Can we please have the Twilio Alphanumeric Sender ID functionality within GHL? HIGHLVL-I-1207

Option for different team members to listen in on live calls to assist with sales, or support etc.

Ability to build rich conversations between more than two parties over multiple channels, such as SMS and Chat. Twilio API has its capability. And i know that LC Phone is a Whitelabel Twilio Phone Service. Please let us know if we can work on this implementation. Anyway, the link below is the twilio group texting developer guide. https://www.twilio.com/docs/conversations/group-texting?fbclid=IwAR3F8opdoKGpyHMEieJN6kyS8NBSrRVIhveM93JNmBBmjlp1v1Ig8E3UkUw

In the GHL mobile app, there is a call quality popup that happens after every call is made. our agents report that the quality popup interrupts their workflow. Please replace popups with some other functionality, perhaps a survey form that agents can optionally fill out. Alternatively, perhaps there can be an easy way to give feedback during a call, that will not be as intrusive.

For inbound calls. it would be great to have ring groups that route to multiple team members... for example Sales, Support, Service, Accounting, HR, Project Management, etc.

* Currently we can see failed and opted out in the messaging analytics * we can click on either one of these and see a little more specific, for example , maybe for the time frame I selected, I can see 489 failed * we can click on either one of these and see a little more specific, for example , maybe for the time frame I selected, I can see 298 opted out *. The issue is that this is a report, that has no or very little functionality..... who makes a report that you can not export, or download to review and further analyze the data ??? We need to be able to download and export these reports

Provide Ai generated responses for user to select Based on Emails and SMS coming in

We have a client requirement where the caller first goes through the IVR and is then transferred to a live person. If that person does not answer, the call should automatically return to Voice AI as a fallback so the AI can continue the conversation, capture the enquiry, answer common questions, or route the caller appropriately. At the moment this does not appear to be supported. This feels like a relatively straightforward call flow enhancement and would be very useful for businesses that want a human-first route with AI as a backup, rather than the call simply failing or ending when the transferred user does not pick up. Use case: • Caller enters through IVR • Caller selects the relevant option • System attempts transfer to assigned user or team • If unanswered, busy, or unavailable, call returns to Voice AI • Voice AI continues handling the call This would improve resilience, reduce missed opportunities, and create a much better caller experience.

There is currently a critical issue, system-wide gap, and major blindspot in how GoHighLevel handles phone number provisioning relative to Trust Center registrations. The Blindspot: When a sub-account has an approved A2P, SHAKEN/STIR, and Voice Integrity profile, newly provisioned phone numbers are NOT automatically bound to these registrations behind the scenes. False Security: The dashboard displays green checkmarks and shows an "Approved" status, giving agency owners zero reason to suspect anything is wrong. Silent Failure: In reality, newly provisioned numbers remain unauthenticated on the carrier level until an agency owner manually opens a support ticket to request registration per number. Immediate Damage: Because of this gap, brand-new numbers are instantly flagged as "Spam Likely" by carriers, destroying answer rates and driving client churn before anyone notices. The Critical Gap: Agency owners cannot educate themselves on or fix a problem the system completely hides from them. Asking users to submit manual support tickets just to bind new numbers to an already-approved profile is an unscalable operational failure. The Solution: Automate Binding: Automatically apply approved SHAKEN/STIR, CNAM, and Voice Integrity profiles to all newly purchased/provisioned phone numbers instantly upon creation. UI Transparency: Display the individual SHAKEN/STIR and CNAM registration status directly next to each number under Settings > Phone Numbers so agency owners can instantly verify carrier-level protection.