Automations

User (Team Member) Replied Trigger Needed
Right now in GHL there is a trigger called "Customer Replied." It fires when a customer sends us a message. That part works great. But there is no trigger for when a user (a team member, a staff member, an agent) replies back to the customer. This is a huge problem. Here is the problem in simple words: A customer messages us. We are supposed to message them back. Sometimes our team does. Sometimes our AI does. Sometimes nobody does — and we don't find out until the customer gets angry and leaves. We have no way to know if a user replied or not. GHL does not tell us. What we want to build (but can't): Customer sends us a message Wait 5 minutes Check: did a user reply? If YES → great, do nothing If NO → send an alert to the owner: "Hey, nobody replied to this customer!" Step 3 is impossible right now. There is no "User Replied" trigger. What we need GHL to build: A simple new trigger called "User Replied" that fires when any team member sends a message to a contact. With filters for: Which user replied Which channel (SMS, email, WhatsApp, Instagram, Facebook, Live Chat) Which assigned user it was meant for Also please add "User Reply" as an option on the Wait action, the same way we already have "Contact Reply." Why this matters: AI agents are everywhere now. When the AI misses a message, we have no way to catch it. Sales teams need SLA tracking — "did my rep reply in 5 minutes?" is impossible to answer today. Drip sequences keep firing even after a human has already replied, which makes customers angry. Shared inboxes need this to know who is handling what. This idea has had hundreds of votes for two years. Please build it. It is the single biggest missing piece for anyone running AI or team-based customer conversations on HighLevel. Thank you.
1
·
New Feature
Workflow Trigger for Manual Outbound Messages (User Sent Message)
Currently in workflows there is no native trigger or condition that detects when a manual outbound message is sent by a user in the Conversations inbox. It would be very useful to have a trigger such as: “User Sent Message” or “Manual Outbound Message Sent” This would allow workflows to react when a team member manually replies to a lead. Example use cases: 1. Stopping automations when a human replies If a team member starts a conversation with a lead, we want to automatically remove the contact from intro or follow-up workflows to prevent automated messages from continuing. 2. Lead response SLAs Businesses often want to ensure leads are replied to quickly. Example workflow: • Assign lead to staff member • Wait 10 minutes • If no outbound message was sent by the assigned user → reassign the lead to another staff member. 3. Tracking team response times Being able to detect manual replies would allow reporting and automation based on how quickly team members respond to customers. Current limitation: The only related trigger is “Customer Replied,” which detects inbound messages but does not allow workflows to detect when a user replies manually. Because of this, many workflows require manual tags or workarounds, which are unreliable in fast-paced lead handling environments. Requested feature: A native workflow trigger or condition such as: • User Sent Message • Manual Outbound Message Sent • Filter options like: • message channel (SMS, WhatsApp, Instagram, etc.) • user who sent the message • automation vs manual message This would greatly improve lead management automation and SLA enforcement. Business impact: Many businesses using GoHighLevel rely on fast response times to convert leads. Without a trigger for manual outbound messages, it is difficult to enforce response SLAs or automatically stop automations when a human takes over a conversation. Adding this trigger would allow teams to build reliable lead-handling systems, improve response times, and ultimately increase lead conversion rates.
5
·
New Feature
Load More