User Replied Trigger | Voters

User Replied Trigger

Jacob Radcliffe

We need a trigger for when a user replies so it can help stop automations.

April 26, 2024

Brandon Burris

Went to go create this trigger, and found out it doesn't exist. How does this not exist? This is needed ASAP, and is needed for all communication channels. Probably would take a dev 1-2 days to build and would be a massive win. Especially with all of the AI automations coming into play.

Taha Kazmi

100% NEEDED. IT Could be used to train the bot, summarize the conversation, and perform limitless actions, make notes, etc etc

Mike Hochwald

I made the same request before seeing this one. I can't tell you how important a trigger on "User sending message" is.

Tommy Mutchler

Yes, This should also include manual/automated outbound messages as trigger options.

Rohan Williams

Tommy Mutchler also messaging channel as a filter so we can fine tune our

automations.

Myles Walsh

I agree - trigger to be fired when a human / user replies to the contact is VITAL so we can stop the automated replies.

Rohan Williams

Myles Walsh this was a problem we had with DRIP campaigns. A user would send a message to someone and then the DRIP automation would send another message soon after confusing the contact.

If we had a user reply trigger we would simply remove them from drip campaigns or at minimum restart the drip timer so they don't get bombarded with messages both manual and automated.

Johnny Scott

I agree a trigger for when users reply would be amazing for stopping A.I. Bots as well instead of manually adding a tag

Rohan Williams

This is a very important need and a huge oversight. Right now I am forcing my sales reps to use tags manually when they reply to leads, but this needs to be done automatically because sometimes they forget.

James Campbell

As a workaround, can a Marketplace webhook be set up with an outside automation that would accomplish this?
Contact reply -> use workflow to add tag
Marketplace webhook -> start 24 hour wait timer that triggers a "no reply" notification at T-0. 
If there's an outgoing sms to that contact, the webhook removes the contact from the 24 hour wait and removes the tag.

Jacob Radcliffe

James Campbell Yes you can. I think that it's more about giving this as a common action since it is an api thing already: https://highlevel.stoplight.io/docs/integrations/028dcf92ee0b9-outbound-message

Rohan Williams

James Campbell we get charged 0.01 for every run on that webhook, and it is so basic to add an outbound reply trigger that we need to push for it.

Robert Lemmens

we also need a trigger when they reply with non-text media: location, voice notes or image. currently, workflows are not aware of those replies. just the media type and url of the media would suffice.

Wilber Peralta

We are in the process of automating our responses to leads via WhatsApp. However, we have identified a critical need: our current tool does not have internal notifications when the company's internal users do not respond to a lead.
Therefore, I propose the development of an automation that works as follows: we need a trigger that activates when a lead is waiting for a response and the internal user has not replied. In this case, the system should send a notification to the user informing them that the lead requires an urgent response.
Due to the high volume of messages received daily, it is possible that a response to a lead may get lost or forgotten. Therefore, it is crucial that responses are timely. To improve and ensure this process, the system should send an internal notification to the user when a lead needs a response after a reasonable waiting period that has been programmed.

Rohan Williams

Wilber Peralta the way we currently do it is we tag the lead when the contact is created and assign the lead to a user. If the tag remains after 5 minutes the lead is reassigned to another user and that user is notified. Rinse and repeat until someone removes the tag and replies to the lead. 
We also created a custom number field and increment the times the lead is reassigned by 1, so we know how many times the lead was reassigned before someone got to it.
We want to eliminate the need to remove a tag and simply perform that untagging when a user replies to the lead, because sometimes the user forgets to remove the tag, which is annoying for admin.

→