Most outreach tools are built to keep going. More follow-ups, more names, more activity, because activity looks like effort.
That is the behavior that makes automation feel rude. Zendoo is built to do the opposite.
The rule
The moment anyone replies — a no, a question, a "happy to chat," anything that is a real person — every future message scheduled for that job stops. Not at the end of the day. Not after you notice. On the next pass after the reply arrives.
This is not a setting you can turn off. It is the safety rule the rest of the product sits on.
If someone took the time to answer, the least you owe them is silence after that.
Why "keep going" is the expensive mistake
Picture the other version. A recruiter writes back that the role is not a fit, and your account messages two more people at that company the next morning anyway.
That is not extra effort. It is the story people repeat: the candidate whose bot kept writing after we said no. It burns the company before you have had a real conversation, and it wastes the person who already replied.
A hard stop protects two things at once:
- Your name at that company. You do not want to be the follow-up that arrived after the no.
- The person who answered. A reply, even a bad one, is them doing you a courtesy. More messages that week undo it.
How we decide a reply counts
A reply gets read quickly: rejection, interest, a real question, or an auto-reply that should not count. Getting this wrong in the "keep going" direction is the failure that matters, so ambiguous notes are treated as a stop.
An early stop costs you a message you did not need to send. A missed rejection costs you the company's patience.
What a stop does not undo
Messages already sent stay sent. If a sequence had more than one person in flight, everything still scheduled for that job stops once a real reply lands. You decide what happens next. The system does not keep running on the old plan.
The goal is not a perfect reader. It is a system that fails toward quiet.