Reply based branching starts when a contact changes the conversation's state. Pause the automated path, read the reply, and choose the next action from it. A reply can open a human conversation, ask for clarification, raise an objection, delay a decision, or close the door. Silence leaves the state unknown. Follow-ups work because timing changes context, and the same person can reply later with the same budget and need.1 Attention can account for the difference between silence and response while fit stays the same.2 Keep unanswered contacts in a reasoned follow-up path and answered contacts in a deliberate branch.
Set the router
Use the reply as a control signal. Read it before deciding whether the contact stays in an outreach path.
A reply should stop the sequence and move the sender to a human conversation.3 With Auto remove on reply set to Yes, any reply stops the user from continuing to send emails or create related tasks for the Contact.4 Some sequence systems suppress all later stages after a recipient replies.5
| Reply type | What to learn | Action | Move on when |
|---|---|---|---|
| Interest | what prompted the reply and what they want next | write back yourself and ask what prompted the reply | they state a concrete next request |
| Objection | what concern needs handling and whether a later revisit makes sense | answer the objection and record the condition for a later touch | the revisit condition is written down |
| Question | what answer they need before they can continue | answer the question and ask what decision it supports | their response gives a clear route |
| Rejection | whether they want outreach closed or have named a condition for return | close the active path and record the stated reason | they explicitly give a reason to return |
| Unclear intent | what the reply means and which branch it belongs to | ask a clarifying question and keep the scheduled path paused | the meaning and next action are clear |
Interest replies
Write back yourself to advance an interested reply. The branch ends when you know why the contact answered and what they want next, with an explicit next request.
Ask what prompted the response, which part they want to discuss, or what they need before deciding. Choose a different automation behavior when a reply does not mean the sequence should end completely.6 If they request detail, send what they asked for and wait for their reaction. If they ask to reconnect later, write down the return condition before ending the exchange.
A positive tone alone leaves the route undefined.
Objections and questions
An objection gives you a problem to handle. A question gives you a gap to close, so keep both branches narrow and easy to answer.
Sell one thing at a time. Selling everything in one email leads to long emails that get deleted.7 Start with the biggest problem, move to the next problem if needed, and ask for a response if neither works.8
Answer the question that arrived before adding context. Then ask what decision the answer supports. If it exposes a separate concern, route the conversation to that concern and keep the original request visible. After handling an objection that deserves a later follow-up, record it as a sequence or task.9
Rejections and unclear replies
A rejection closes the active path. Unclear intent needs interpretation before outreach continues.
Use the person's own words to choose between closing and clarifying. For a clear rejection, close the active outreach path and record the reason. When the meaning is unclear, ask for the missing meaning and leave scheduled outreach paused. Resume only after the reply supplies a condition that justifies another touch.
Treat politeness as neither interest nor permission for another automated message. The reply determines the branch.
Keep silence moving
Silence has its own branch, and it ends when the contact replies.
Follow-ups generate 50 to 100 percent more total replies than the first email alone because each follow-up reaches the prospect in a different inbox state with a fresh reason to respond.10 Timing changes context, so give each silent touch a fresh reason to respond.11 Repeating the same ask keeps the contact in the same branch and gives them little to react to.
Keep a bubble up email as a reply to the previous email in the thread.12 Space early touches at least three days apart and later touches seven to fourteen days apart to reduce spam reports.13 When a reply arrives on this path, stop the silent branch and use the reply table.
Return after a reply
Resume outreach only from a recorded condition. Write down what must happen before it starts again, and do not use the next unused step in the old sequence.
A reply can lead to a later sequence when the conversation needs more time or a specific follow-up. Choose that behavior deliberately, attach it to the stated condition, and keep the live conversation outside the old cadence. If no condition exists, close the branch.
Keep the later message connected to the conversation that created it. Otherwise, the contact has to interpret the outreach from the beginning.
What not to do
These mistakes blur the reply state and let the old cadence take control again.
- Do not let a scheduled follow-up continue after a response. A prospect may receive a follow-up even after responding.14
- Do not send fourteen emails on one channel. That pattern is described as obnoxious.15
- Do not keep adding touches without spacing. More follow-ups can bring more replies and more spam risk.16