Overview
When a seller replies, you usually want your automation to stop so they are not still receiving scheduled messages after they have made contact.
In the previous version this was a toggle on the drip campaign. In 6.0 you build it as an Activity Trigger automation instead — which takes a few minutes to set up but gives you far more control, because you can act on what the reply said, not just that a reply arrived.
You will set this up twice: once for incoming SMS, once for incoming calls.
Steps
Step 1: Open Activity Triggers
Go to Leads, then Activity Trigger, then click Add Automation.
Step 2: Select the incoming trigger
Choose the incoming trigger you want to act on — start with incoming SMS.
Step 3: Branch on AI intent
You can branch on AI intent, so the automation behaves differently depending on what the reply actually said.
Set up two branches:
Interested — for replies the AI reads as interested
Default branch — everything else, including not interested, unclear replies, and spam
Step 4: Decide what happens on the Interested branch
In the video this branch does three things:
Adds a note — for example, "this person is interested"
Adds a tag
Stops all other automations for that lead
You can add more steps. A useful one is creating a task — "call them ASAP" — and assigning it to your Acquisition Manager so a hot reply gets picked up immediately.
Step 5: Set the default branch to stop as well
On the default branch, choose Stop other automation.
This means the automation stops whatever the reply says. Someone who replies "not interested" should stop receiving messages just as surely as someone who replies "yes".
Step 6: Repeat for incoming calls
Build the same automation again for incoming calls, with the same Interested and default branches.
When a call comes in, REsimpli transcribes it, sends the transcript to AI to read the intent, and then runs your branches against that intent — the same way it does for text.
If you only want it to stop
You do not have to use the intent branching. If all you want is the old behaviour — any reply stops the automation — set both branches to Stop other automation and add nothing else.
The automation then stops regardless of whether the person was interested.
Important Notes
Nothing stops automations by default. There is no toggle on the automation itself. If you have not built this, leads continue receiving scheduled messages after they reply.
Build it twice. SMS and calls are separate triggers. Doing only one leaves the other channel running.
Always set the default branch. If you only handle Interested, every other reply — including "stop texting me" — leaves the automation running.
Incoming calls are transcribed before intent is read. The intent comes from what was said on the call, not from the fact that a call happened.
Conversational SMS AI already stops automations on its own. If that is switched on for a lead, active automations stop when the AI replies. This article is for leads not using it.
Troubleshooting
A lead replied but kept receiving messages
Check that an Activity Trigger automation exists for that channel. SMS and calls need separate automations.
It stops on texts but not on calls
The incoming call version has not been built. Repeat the setup using the incoming call trigger.
It only stops for interested leads
The default branch is missing or is not set to stop. Every branch that should end the sequence needs its own Stop other automation step.
You want a note or task but are not getting one
Notes and tasks are steps you add to a branch. They are not automatic — add them to the Interested branch alongside the stop.
Summary
Go to Leads → Activity Trigger → Add Automation, choose the incoming SMS trigger, branch on AI intent with an Interested branch and a default branch, and put Stop other automation on both. Add a note, a tag, or a task to the Interested branch if you want the reply flagged to someone. Then build the same automation again for incoming calls.