Conversations

I'd like to see a normal REPLY TO option when emailing from conversations, AND from automation workflows. Right now in conversations I can quasi reply, but it doesn't auto fill the subject line from what I'm replying to, and it doesn't have the body of the message I'm replying to. This also goes the same for responding back to email from an automated workflow. There's absolutely zero option to find what the subject was from the GUI, or even the API. TL-DR; Need an actual REPLY-TO email option that works.

Many bulk email platforms have a "subscription center" that people are taken to when unsubscribing. It lets the subscriber choose which campaigns to unsubscribe from, or system emails, or all. Right now it's a very aggressive DND option which leads to a lot of unintentional unsubscribes from things they still wanted such as invoices and appointment alerts etc.

Right now the conversations filtering is limited and clunky for service businesses managing multiple service lines. What I need: the ability to create and save custom contact lists based on tags/criteria, then quickly access those lists directly from the conversations tab. Use case example: I have contacts tagged as "Permanent Lighting Leads" I have contacts tagged as "Gutter Cleaning Leads" I have contacts tagged as "Snow Removal Leads" Instead of manually filtering every time I want to message a specific group or scrolling to find the right person, I want to create saved lists (like "All Lighting Leads") and click directly into that list from conversations to see only those contacts in the conversations tab. This would let me: Quickly segment and message specific service categories Avoid repeatedly setting the same filters Streamline communication workflow for multi-service businesses For service businesses juggling multiple offerings, this would make the conversations tab way more functional and save tons of time daily.

On the inbox when an opportunity is updated and an email comes in the time format is different on each

In building out a customer support team, tech support team etc, each of which contains multiple people on a team, we really need to be able to select from a list of send-as or "from" email addresses. If we have 5 people on the tech support team for example, all of them should use support@yourdomain.com , but have their own dynamic email signatures. Similarly, if that same person is also on the client support team, they should all be sending and receiving email at info@yourdomain.com , which changes that persons signature since they are acting as a different role within the business.

I've seen a few ideas suggest video chat bubbles where you can send short video clips back and forth with website visitors and while this could be cool, taking that one step further would be video call functionality. There are a couple auto dealership chat softwares (Gubagoo and DealerInspire) that allow for live video calls. This could be very powerful for certain industries.

Let's add telegram :)

Title: Allow User-Level and Account-Level Default Reply Channel (e.g., Always Default to Email) Description: In the current Conversations UI, the reply composer defaults to SMS, WhatsApp, or Email based solely on the last inbound message. This behavior cannot be overridden by the user and there is no setting—agency-wide, account-wide, or user-level—to make Email the default reply channel. This creates friction, inconsistency across teams, and increases the risk of replying on the wrong channel. Requested Enhancement: Add a configurable setting that allows users and account administrators to define a default reply channel for Conversations. For example: Proposed Settings: User-Level Default -- Default Reply Channel: Email / SMS / WhatsApp -- Optional toggle: “Always default to this channel (ignore auto-detect)” Sub-Account-Level Default -- Apply a default channel for the entire team -- Override per user if needed Agency-Level Default Enforce channel preferences across all sub-accounts Optional Safeguard Setting: “Warn before sending SMS when Email is available” This prevents accidental SMS replies that incur cost or break compliance workflows. Why This Matters Operational Efficiency Teams that primarily communicate through Email must constantly switch the composer from SMS to Email—sometimes dozens or hundreds of times per day. Prevents Accidental SMS Replies A contact may have previously texted once, and the system silently defaults to SMS—even when the user intended to send Email. This results in: -- Unintended SMS charges -- Mixed communication channels -- A2P compliance issues Consistency Across Teams Agencies want to enforce consistent communication standards (e.g., always email for client support). Better UX for Large Teams Reduces mistakes and additional steps, improving the user experience and reducing support tickets. Impact Without This Feature -- Increased risk of replying via SMS when Email was intended -- Inefficient workflows and time wasted switching channels manually -- Difficulty maintaining communication standards -- Higher SMS cost and possible A2P compliance exposure Summary Please allow users and account admins to set a default reply channel (such as Email) in Conversations, and optionally force or enforce that default unless explicitly overridden. This would immediately improve consistency, efficiency, and accuracy in messaging workflows.

Create your own video call platform where users can generate exclusive links through calendars, and within Go High Level, we can receive video calls. Furthermore, the platform should include triggers to let us know when someone has joined or is live. It should also track whether someone attended a scheduled appointment from the calendar, enabling automated follow-ups based on whether the user attended, didn’t attend, and many other functionalities.

You should create a solution like Zoom - video call, voice call, screen sharing and recording.