Phone System

The Problem: Currently, when a contact calls or texts one of our tracking numbers (or a number from a website pool), any manual outbound call or SMS made from the Conversations Tab defaults to the location's Main Default Number. To call the customer back from the same number they interacted with, agents have to manually click the dropdown menu and change the "Call From" number every single time. If they forget, it ruins the tracking data, confuses the customer with a new caller ID, and breaks the communication thread. Building complex branching workflows just to tag contacts and remind agents is a messy workaround. The Proposed Solution: Introduce a "Dynamic Match" or "Sticky Number" setting for the Conversations Tab dialer and SMS window. When enabled, GHL should automatically detect the specific phone number the customer last used to call or text the business, and automatically set that exact number as the outbound caller ID/sender ID for manual replies. How it should work: Lead visits the website and calls/texts Tracking Line B. The agent opens the contact in the Conversations Tab to reply. GHL automatically defaults the outbound Call/SMS to Tracking Line B instead of the location's default number. If the contact has no prior history, only then does it fall back to the main default number. Why this is important: Simplicity for the User: Agents don't have to think, check tags, or manually change dropdowns before every single call or text. It just works. Better Customer Experience: Customers always see the exact same phone number on their caller ID that they originally dialed, preventing missed callbacks due to "unknown numbers." Cleaner Tracking: Keeps attribution and conversational threads completely seamless without needing messy, multi-step workflow workarounds.

LC Phone needs stronger spam protection before spam calls pollute Conversations, create fake contacts, or reach Voice AI and other paid features. I am a new GHL user and started receiving more than 40 spam calls per day on an LC Phone number. These calls are creating noise in Conversations, adding fake contacts, and making it harder to see real prospects and customers. After reviewing the Ideas Board, it looks like many users have reported similar spam problems for years. This does not seem isolated to one account or one number. The current workarounds are not enough. IVR quarantine adds friction for real callers. Buying a new number adds cost and does not guarantee a clean number. Manual blocking and DND are after-the-fact cleanup. The possible protections that could help users include: Phone number reputation checks before LC Phone numbers are assigned. A visible phone health score inside GHL. A clear SLA or fast replacement process for polluted numbers. Carrier-side escalation when a number is already spam-polluted. Caller spam blocking and quarantine. A “mark as spam” option for callers and contacts. Future calls from marked spam numbers dropped or hidden. Spam contacts archived or moved to a separate blacklist area. Automatic removal of spam contacts from funnels, pipelines, workflows, opportunities, and automations. Better filtering in Conversations, including filtering by inbound phone number. Voice AI spam detection and quick hang-up. Billing protection for spam-related Voice AI usage, transcription, summaries, recordings, and Voice Intelligence when spam is identified. From an agency perspective, this is also a serious concern. I would be hesitant to port a client’s main business number to LC Phone if GHL cannot confirm number reputation or provide stronger spam controls. A safer approach may be to keep the client’s main number with their current carrier and forward calls to LC Phone instead. The main concern is that spam should not be allowed to reach Conversations, workflows, Voice AI, or paid features without better controls.

Extremely difficult to import numbers when we have phone numbers in a google sheets/excel in different columns. We would think we could just select additional phone in the import for each column and it would merge them all for us (especially since the column would be labeled mobile or landline or work). Vs. us or clients having to try to figure out how to put all their phone numbers into one column and then you can't even label what they are. If it's landlines, mobile, work, etc.. So then they have to go contact by contact to edit that??

Would be amazing if we could display our client's business names as the outbound caller ID so leads see the business name instead of a random number.

Please add a Zadarma Integration, many of my clients use it to call their customers.

This would be game changing for anyone who is making recorded sales calls. Similar to Zoom and Otter.ai recorded and summarized meeting notes, having transcribed calls and post call summaries in a format controlled by the user would be amazing. This is a feature that everyone can find value in especially sales people on the road making calls while we are driving between appointments.

When calling, you can add custom call status buttons to the phone calls finish screen. Then calls can be customized for specific clients that do different things. Then triggers can be used for call statuses across the board instead of just where the default "Call Status" fields apply HIGHLVL-I-1149

You should be able to download a csv list of phone numbers that have bounced or have any errors with them just like you should be able to do that with emails. If they arent showing up on the bulk actions it should be in the analytics.

Twilio is one of the most expensive platforms! Here is one that is 1/3 the price on outbound texts, and free inbound. We need to have different options in GHL. https://telnyx.com/pricing/messaging HIGHLVL-I-1776

Can you please add an integration for RingCentral, so it can be possible to add phone numbers from that app to our sub-accounts. We have several phone numbers with RingCentral that we would like to use in our sub-accounts