Out-of-office season: reroute, do not retreat

Starting about now and running through August, a growing share of your outreach will come back with an auto-reply. Most sellers process an out-of-office the same way: small sigh, mark the account dormant, move on. Which is a strange reaction, considering what the message actually contains. A typical OOO hands you a return date, the name and address of the person covering, and sometimes a phone number that was never public. It is the only message in outbound that answers questions you did not ask. Treating it as a stop sign wastes the most informative reply your sequence will get all summer.

Read it as a routing instruction

The named backup is a warm door. "For urgent matters, contact Dana" is an introduction, made in writing, by the person you were trying to reach. A short, honest note to Dana that references the coverage line and asks one light question is not an intrusion, it is using the door as built. Sometimes Dana is junior and simply tells you how things really work over there, which is worth more than the original thread. Sometimes Dana turns out to be the person who actually owns the problem. Either way you now know two names at the account instead of one, and multi-threading an account before you need it is the whole lesson of champion tracking run in reverse: relationships with people, plural, survive whatever one calendar does.

The return date is a scheduling gift. Log it. A touch that lands the second or third day after someone returns, when they are triaging a swollen inbox and deleting greedily, works better than one that lands the first morning back. Reference the gap plainly: no guilt, one sentence of context, one small ask. Most of your competitors sent their note into the vacation void, got the auto-reply, and never followed up at all. Their message is item two hundred in the return-day purge. Yours arrives alone, two days later, from someone who visibly paid attention. The reply data has always favored this kind of persistence anyway, the pattern from most replies come from follow-ups, and OOO season sharpens it.

The account stays warm in the meantime. Two or three weeks of absence does not cool a real account, but a seller who vanishes for the same two or three weeks does. Keep the low-ask touches running: the useful article, the relevant note, the call to the backup. Nothing that demands a decision from a person on a beach. Presence without pressure is the summer register.

The season is a sorting advantage

Here is the compounding part. Because most outbound teams retreat in the face of auto-replies, and some retreat from summer entirely, a team that reroutes instead spends July building second contacts and perfectly timed return-week touches while the field empties around it. We argued in the summer slowdown is a choice that summer punishes only the teams that accept it. OOO routing is what the non-accepting version looks like in practice: same list, same effort, redirected instead of paused.

Our reps run a standing summer discipline for this: every OOO gets its return date logged and its backup called within two days, and the follow-up fires on the schedule the auto-reply itself provided. It is unglamorous, it is nearly free, and every September it produces meetings that look like luck from the outside. If your team's pipeline goes quiet every summer and wakes up apologizing in the fall, book a strategy call. We will show you what rerouting a summer looks like on a real account list.