Wait For Contact Reply Or Timeout
Wil Horneff
This is different from an objective that triggers a follow-up after a certain amount of time. This request pertains to allowing a contact to move from a “wait for reply” step into a Switch step—enabling internal actions to be taken if the contact hasn’t replied, without initiating additional outreach. For example, handing the contact off to a human, triggering specific HighLevel actions, setting custom fields, or adding tags.
Log In
B
Bryce DeCora
Merged in a post:
Time Delay Custom Scenario
Jake Cross
I would love the ability to have a custom scenario or other time trigger.... this is beyond just follow ups. But then being able to tag and update the contact based upon a time delay.
B
Bryce DeCora
Maybe the follow-ups could allow for different types of "follow-ups". Example, after 1 day of non-response do an AI TEXT BASED FOLLOW-UP, but after 2 days of non-response do a CUSTOM ACTION FOLLOW-UP (ADD TAG TO CONTACT)
B
Bryce DeCora
Can you draft up what you think this might look like? Where this feature would live? Would this apply to all nodes, or only want it to happen during some nodes? I see what you mean here, just trying to conceptualize an intuitive way to do it within our UI.
Wil Horneff
Bryce DeCora I like that idea too, offering variety in follow-ups makes a lot of sense. For this, I was also thinking more broadly, in terms of something that could apply to statements.
The idea I’m proposing is this: if I ask a contact something and they don’t respond within a certain window of time, they would proceed down the default "other" branch (since no response was given) vs being stuck on that statement perpetually. At that point, a tag could be added, which would then trigger a manual action in HighLevel like assigning a follow-up call which is essential in the first 5 min if a contact does not respond. So if there were a toggle directly on a Statement action—similar to how HighLevel handles reply timeouts—where you could set a time limit (or however your UI would allow this), that would give users the same benefit as an objective or calendar follow-up, but with more precise control over what's being said and how it's handled, and what can be done about it if they don't respond.
Also on a personal note thank you so much for focusing on making the core system stable first before moving on. It shows and is greatly appreciated.