Help Center

Docs

Reply Handling

Decide what each reply category does to a lead's sequence: pause on out-of-office, flag the interested ones, and always stop for not-interested

Not every reply is the same

Give each reply category its own next move.

By default a cold sequence stops the moment a lead replies, which is the right call for most answers. But an automatic “out of office” reply is not a real answer, and an “I’m interested” reply deserves your attention, not silence. Reply handling lets you tell each sequence what to do per reply category, and Laureo applies it the instant the reply lands. It is an Ultra capability, built into the sequence builder.

Leaving it alone keeps today’s behavior
Reply handling is optional. A sequence you never configure behaves exactly as before: any reply stops the sequence. You only change what happens when you want to.

Out of office: wait, then continue

The headline capability.

When a lead is away, stopping the sequence loses them and sending the next step lands in an empty inbox. Instead, choose “Wait, then continue” for the out-of-office category and set how many days to wait. Laureo recognises an automatic away reply, pauses the sequence for that many days, and then continues where it left off. The reply is not counted as engagement, so nothing is marked as replied.

1

Open the sequence and find Reply handling

In the builder, scroll to the "Reply handling" section below Schedule & sending.
2

Set Out of office to "Wait, then continue"

Choose the wait option and enter the number of days (1 to 30). Seven days is a sensible default for a typical vacation responder.
3

Save

Your choice autosaves. From then on, an out-of-office auto-reply snoozes the lead for that many days instead of stopping the sequence.

Interested: flag for review

Stop the automation and raise it to a human.

A reply classified as interested or a booked meeting always stops the automation, and you take the conversation from there. Choose “Flag for review” to also get a notification so a hot reply is never buried, or choose to stop silently if you would rather catch it in your inbox yourself. The cold reply lands in your normal email inbox under the Cold filter either way.

Stop a whole company on one reply

One answer can pause everyone at that account.

Turn on “When someone replies, stop their whole company” and a single reply from anyone at a company halts this campaign for every other active lead at the same company email domain. It is off by default. Use it when you do not want a second person at the same account cold-emailed after a colleague has already engaged. Personal email domains, such as consumer mail providers, are never grouped this way, so a reply from a personal address only stops that one lead.

Not interested and unsubscribe always stop

Respect comes first.

  • Not interested stops the sequence. A lead who says no is removed from the sequence, and there is no option to keep emailing them.
  • An unsubscribe request always stops the sequence. What happens beyond that depends on the “When a reply asks to opt out” control in Delivery and compliance: Unsubscribe automatically suppresses the address right away (you can undo it from the suppression list), Ask me to confirm surfaces it for you to confirm before it is suppressed, and Do nothing leaves suppression to you. See Compliance.

Draft replies with AI

An interested reply can arrive with a draft already written.

With “Draft replies with AI” set to On, the moment an interested prospect replies, Laureo writes a draft reply into your inbox composer for you to review, edit, and send. It never sends on its own, the draft simply waits for you. This is an Ultra capability, on by default when your plan includes it; on other plans the control is shown but inactive. For the full behavior see AI Reply Drafting.

Reply handling never sends on its own
Reply handling changes whether a sequence stops, waits, flags, or drafts a reply for you. Even the AI draft only writes into your composer, it never sends. Nothing here contacts anyone new or overrides your suppression list or do-not-contact rules.