What should happen when a lead replies (and what most tools do instead)

Here is the moment every outreach team dreads. A prospect answers your email: “Thanks, let’s talk next week.” Two days later, your LinkedIn account sends them a cheerful “Just bumping this up in case you missed my note.”

They didn’t miss it. They answered it. Now you look like a machine, and in front of a client, it’s worse.

This happens more often than it should, and it’s almost never a writing problem. It’s a question of what the tool does when a reply arrives. This post sets out what we think should happen, how GrowthxAI Outreach does it, and where other tools often differ.

The rule: a reply stops everything

When a person replies, they have moved from “prospect” to “conversation”. Every automated message after that point is at best noise and at worst rude. So the rule should be simple:

A reply on any channel, to any account, stops that lead everywhere.

In GrowthxAI Outreach that is the default. When a reply comes in, every live sequence that lead is in ends with the status exited replied, and every step queued for them is cancelled. That includes:

• Other channels. An email reply stops the LinkedIn follow-up, and a LinkedIn reply stops the email.
• Other accounts. If three of your colleagues’ LinkedIn accounts are working the same lead, a reply to one of them stops the other two.
• Other sequences. If the lead was in more than one campaign, all of them stop.

The reply lands in the shared inbox, tagged with an intent such as Interested, Question or Not now, and from there a person takes over. Anything you write yourself in the inbox is always sent; the stop only applies to automated steps.

What some tools do instead

The details vary, but we see a few patterns in how outreach tools handle replies:

• The stop only covers one channel. A LinkedIn reply stops LinkedIn steps, but an email reply isn’t connected to the LinkedIn sequence, so the LinkedIn follow-ups keep going (or the other way round).
• The stop only covers one account. The account that received the reply stops; other accounts in the same campaign, which have no idea a reply happened, carry on.
• The lead is paused indefinitely. Some tools pause a lead on reply and leave it paused until somebody remembers to un-pause it. Nothing embarrassing goes out, but leads quietly pile up in limbo, and the ones worth following up get forgotten.
• Out-of-office counts as a real reply. An automatic “I’m away until the 14th” ends the sequence, and a perfectly good lead is dropped because they took a holiday.

None of these is a disaster on its own. Across hundreds of leads and several accounts, they add up to follow-ups that never should have gone out and conversations that never happened.

Out-of-office replies: pause, then resume

An out-of-office message isn’t a person saying anything. It’s a calendar. Treating it like a reply throws away the lead; ignoring it means messaging someone who can’t read it.

So by default, an out-of-office reply pauses the lead rather than ending the sequence, and resumes them after 7 days. If the auto-reply names a return date, that date is used instead. The inbox labels these messages Out of office, so you can see what happened at a glance.

You can change the delay, or switch it off in a sequence’s settings, in which case an out-of-office ends the sequence like any other reply.

Hold for review: when you want to decide

Sometimes a reply doesn’t mean “stop”. Someone writes “Send me more in January”, or “Talk to my colleague instead”. For sequences where that happens a lot, you may prefer to look at each reply and decide.

That’s what hold for review is for. Set it on a sequence, and a reply pauses the lead instead of ending the sequence. A Held reply task appears on the attention list; one click resumes the sequence or exits the lead.

The important part is the expiry. Every held lead has a deadline: the sequence’s exit held leads after setting, 30 days by default. If nobody acts, the lead exits on its own. Nobody is stuck in limbo because a task got buried.

The exceptions, and why they’re explicit

A reply stop that nobody can override is too blunt. There are real cases for keeping a step going, such as sending a meeting reminder to someone who has already said yes. So the default can be changed in three deliberate ways:

1. Turn off Stop when the lead replies for a sequence.
2. Set the sequence’s reply scope to only stop the sender they replied to.
3. Mark a single step send always, so it goes out even after a reply.

Each is a visible setting on a specific sequence or step, which means that when something does go out after a reply, you can see exactly why. The default stays: a reply stops everything. You can read the full rules in the inbox guide and the sequence settings.

A short checklist for any tool

Whatever you use, test it before a client or a prospect does. Put yourself in a sequence that runs on two accounts and both channels, then:

• Reply by email. Does the LinkedIn follow-up stop?
• Reply to the second account. Does the first account stop too?
• Send an out-of-office. Is the lead dropped, paused forever, or resumed later?
• Leave a paused lead alone. Does it ever come back out of limbo, or does it sit there?
• Check the inbox. Can you see which sequence, step and account sent the message the lead answered?

If you can answer all five without guessing, you’ll never have to apologise for a “just bumping this up”.

To see the reply stop alongside the rest of our safety rules, go to the safety page. To see how sequences, branches and settings fit together, go to sequences.