The number that started it
We pulled every inbound reply across our outbound program and classified it. The breakdown was not what we expected:
- 44% were out-of-office auto-replies. Not "no." Not "not interested." Just "I'm away until the 23rd."
Out-of-office isn't rejection. It's a timing accident. The person never saw the message — a mail server answered for them. And yet, in most outbound setups, that auto-reply does something quietly destructive.
The leak
Every major sending platform stops a contact's sequence the moment any reply lands. That rule exists for a good reason: if someone answers, you don't want a robot to keep emailing them. But the rule can't tell the difference between a human typing "not interested" and a vacation responder firing automatically.
So here's what happened to a prospect who was simply on holiday:
- Our sequence sends email one.
- Their auto-responder fires: "Out of office until Monday."
- The platform marks them as replied and stops the sequence.
- Nobody ever follows up.
The lead — already researched, enriched, and a genuine fit — was dropped on the floor because of a calendar. Across our data, that was a meaningful share of every list we touched. We had paid to find every one of them.
The fix: snooze, don't stop
The instinct is to try to avoid out-of-office replies. You can't — people control their own auto-responders, and a chunk of any list will be away on any given week (summer and late December especially). Chasing a zero is the wrong goal.
The right goal is to make an out-of-office reply harmless. So we built a snooze.
When an auto-reply is recognized as out-of-office, our agents now:
- Read the return date. "Back on June 23," "returning Monday," "away until 6/23" — the message usually tells you exactly when to come back. When it doesn't, we default to a one-week snooze.
- Pause the lead until then instead of dropping them, holding their place in the sequence.
- Resume automatically when the date arrives — re-entering the exact campaign they were in.
A scanner runs every hour, wakes up the leads whose snooze has elapsed, and puts them back in motion. No human has to remember anyone.
The guardrails that make it safe
"Resume the sequence later" is easy to get dangerously wrong. A snooze that re-emails the wrong person damages your sender reputation and your brand. So the resume is wrapped in hard guards. A snoozed lead is not resumed if, in the meantime, they:
- replied positively or booked a meeting,
- said "not interested," "wrong person," or anything negative,
- landed on a suppression or do-not-contact list.
Suppression and consent checks are never skipped — only the ordinary timing throttle is lifted, because a returning lead was already approved when they first entered the sequence. And the snooze clears exactly once on a real resume, so nobody gets the same touch twice through this path.
Why this is the Synter way
This is what "you direct, the agents execute" looks like in practice. You don't want to babysit a spreadsheet of who's on vacation and when they're back. You set the intent — follow up with the right people at the right time — and the agents handle the bookkeeping, including the unglamorous part where someone's auto-responder fires at 2 a.m. on a Saturday.
Out-of-office used to be where leads went to die quietly. Now it's just a later send date.