Goal events and stop on reply
End a sequence when a goal is reached or the contact replies.
Why it matters
Customers who booked stop getting reminders to book.
The HLB difference
Goals and exit rules are set per workflow.
How it works
Stop a follow-up sequence automatically once the contact books, pays or replies.
Goal events and stop on response end or redirect a sequence once a contact has done what you wanted, so they stop getting messages that no longer apply.
A goal event sets a goal for a workflow. From the moment a contact enters, the system watches for that event, whichever step the contact is on, including outside business hours. When the goal is met, the contact moves straight to the goal step and skips the steps in between.
Add the Goal Event action and choose one of these goals:
- Received an email event, such as clicked, opened, complained or spam
- Clicked a trigger link
- Added or removed a contact tag
- Appointment status
Each workflow can currently have one goal event. Goals only cover actions a contact takes, so you cannot set a goal for not opening an email. Once a contact meets an email goal, repeat opens do not trigger it again. You also decide what happens if a contact reaches the goal step without meeting the goal: end the workflow, continue anyway or wait until the goal is met.
Stop on Response is a workflow setting. When it is on, a contact leaves the workflow as soon as they respond to a message the workflow sent, whether by SMS, email or call. It does not apply to manual messages or to other workflows.
For automated calls, voicemail detection is on by default, so a call that goes to voicemail does not count as a response and the contact stays in the workflow. If you turn on Disable Voicemail Detect in the Call action, set the call timeout to 20 seconds or less so the call does not reach voicemail.
Ready to put this to work in your business?
Start onboarding with the Max Digital Edge team and get set up on Hot Local Business.