A person answers, the sending tool marks the thread finished, and the rest of the company carries on as though nothing was said. The stop has to become a fact.
The stop lives in one tool only. A reply arrives, the emails stop, and the CRM still shows the company where it stood last week. At a thirty-person software company nobody tells the pipeline that a human answered.
By hand today
“Gmail out-of-offices replies sent to Outlook inboxes aren’t recognized and therefore contacts will be unenrolled”
HubSpot, on unenrolling from a sequence, read 8 September 2026
That is a vendor describing its own stop signal getting it wrong: a machine answered, the tool read a person, and the lead left the sequence for good. The other direction is more common and costs more. A person answers, the sending tool marks the thread finished, and the rest of the company carries on as though nothing was said.
The outbound book covers the two stages this one sits between: sending without getting banned and following up without remembering to. Those chapters build the messages and the gaps between them. This chapter is about one small fact the rest of the engine needs and almost nobody writes down. This human replied, on this day, on this channel, and the sequence is over.
Ask three people in a company with a sequence running who is in conversation right now, and you will get three answers.
What it costs you each week
Ninety dollars a month, per seat, for the plan where the rules that stop a sequence can be changed at all. Stopping is free. Deciding what counts as a stop is the paid part.
Source: HubSpot Sales Hub pricing page, read 8 September 2026
The figure is the published Sales Hub Professional seat price. Sequences themselves are given away, and the free plan runs them. What sits behind the paid tier is the part that matters here: choosing which events end a sequence and which only pause it. An out of office, a bounce, a booked meeting and a two word “not now” are four different things, and they deserve four different answers.
Then count the unpaid cost in your own week. List every thread that got a reply in the last fortnight, and check how many of those companies moved a stage in the CRM the same day. For most founders the answer is none.
The build
Claude Code turns the stop into a fact. A reply is written onto the lead with its date and the channel it arrived on. The company then moves to In conversation, and every drafted step behind it is cancelled.
Work in the folder that holds your CRM access, with the sequence store from the outbound book beside it. Type:
Read the replies in my inbox and in my LinkedIn export. For each one,
find the lead it belongs to. Write the reply onto that lead as a stop:
the date, the channel, and the first line of what they said. Mark every
unsent step on that lead as cancelled, and never rewrite a step already
sent. If the reply is an automatic out of office, pause the lead until
the return date instead of stopping it. Move the company to In
conversation. Write one line per lead to stops.md, and list separately
any reply you could not match to a lead.
What comes back is two short lists. The leads that stopped, each with a date, a channel and the sentence that stopped them. And the replies with no lead, which is where a second address or a second spelling of a company name has been hiding.
Nothing is sent by this step, and that is where the pattern comes from. On the ArkOne platform, sequence steps are planned by position rather than by date, and the system sends nothing at all, at docs/crm-module.md lines 100 to 104. A draft is exported for a person to send, and only then marked pushed, at docs/mcp-log.md lines 76 to 79. The stop does the second half of its work on its own. Line 370 of the same document is where a reply changes what the company is. An answer moves it to In conversation, and that answer outranks a missing score, so a company that has spoken to you can never read as unqualified. Copy that shape and build your own version. There is no demo to download.
The setting worth arguing about is what counts as a reply. Keep it narrow at the start: a human sentence, from a person, in answer to something you sent. Out of office is a pause with a date on it. A bounce is a broken address and belongs back at the stage that found it. A booked meeting is a stop, but it belongs to the next chapter, not this one.
Run it once a day. In the first week the list of replies it could not place is the useful half, because it names every place your records hold two rows for one human.
What it feeds
A time on the calendar. A lead marked In conversation is the only kind worth offering a time to, and the next chapter does the offering. It only works if it can see who is actually talking to you.
Three numbers prove this stage. How many sequences ended because a person replied, against how many ran all the way to the last step. How many companies sit at In conversation this week. And the one that should stay flat at zero: messages that went out to a lead after it had stopped.
What stays with a person
Answering, and hearing the no. A machine can stop the sending. Only a person writes the reply that earns the meeting.
The reply is the whole point of the six stages before it, so it is not a place to save time. Read what they wrote, answer the question they asked, and offer a time only if the answer invites one.
The other half is the no. The system marks the stop; the person decides to say nothing further. No follow up improves a no, and the message that argues with one is the message that gets a domain reported.
The tools you already pay for
Nothing new to buy.
CRM holds the sequence, the stop and the station.
Your inbox is where the reply lands and gets read.
The sending tool from the outbound book only ever exports.
A text file, stops.md, keeps one line per lead, by date.
No new seat. The stop is a fact you were already given for free and were throwing away.
The reply stops the sending. Then the calendar takes over.
Ask: When somebody replies to you today, what in your system finds out?
This is chapter 7 of twelve, after making the CRM fill itself; chapter 8 puts a time on the calendar. The book, Building a real GTM engine with Claude Code and Codex, end to end, runs the whole engine in order, one chapter per stage. A free starter edition for firms under fifty people is coming through the 100k programme.