Introduction
You send a cold email. Minutes later, an auto-reply lands: "I'm out of the office until July 14th." Most salespeople delete it and move on. That's a missed opportunity on both ends of the exchange.
This guide covers how to write an out of office message that sets the right expectations - and what your sales team should actually do when a prospect sends one back.
An out of office message is an automatic email reply that tells senders you are unavailable, states your return date, and directs urgent requests to an alternative contact. A strong OOO includes a specific return date, your monitoring status, and a named backup contact in under 60 words. For sales teams, an OOO reply from a prospect is a follow-up trigger - it tells you exactly when to re-engage.
What Makes a Good Out of Office Message?
A good out of office message answers three questions in under 60 words: Are you available? When will you be back? Who should I contact if this is urgent?
Vagueness is the most common mistake. "I'm currently unavailable" tells the sender nothing actionable. "I'm out of the office until Monday, July 14th" gives them a date to work with.
The four elements every OOO needs:
- Specific return date - "Next week" is useless. "July 14th" is actionable.
- Monitoring status - Are you checking email occasionally or fully offline?
- Urgent contact - Name and email of a colleague for time-sensitive matters.
- Brief context (optional) - "On annual leave" or "at a conference" sets tone without oversharing your itinerary.
According to a Litmus Email Analytics report (2023), auto-reply emails have an average open rate of 98% - making your OOO one of the highest-read emails you will ever send. Keep it sharp.
Out of Office Message Templates for Every Situation
Each template below is under 70 words. Copy, adapt, and use.
Standard OOO - Fully Away
Thank you for your email. I am out of the office from [start date] to [return date] and will not be monitoring email during this time.
For urgent matters, please contact [colleague name] at [colleague email].
I will respond to your message when I return on [return date].
OOO with Occasional Check-ins
Thank you for reaching out. I am away from the office until [return date] with limited email access.
I will do my best to respond to urgent messages, but please allow extra time for a full reply. For immediate assistance, contact [colleague name] at [colleague email].
Conference or Industry Event OOO
I am attending [event name] from [start date] to [return date] and have limited availability.
I will respond to all emails when I return on [return date]. For urgent matters, please reach [colleague name] at [colleague email].
Holiday or Company-Wide Closure OOO
Our office is closed for [holiday] from [start date] through [end date]. All team members will be back on [return date].
We will respond to your message as soon as we return.
Sales Rep OOO - With Lead Handoff
Thank you for your email. I am out of the office until [return date].
If you have an urgent question about [product or service], please contact [colleague name] at [colleague email] or visit [link]. I will follow up personally when I am back.
How to Set Up an Out of Office Reply in Outlook and Gmail
Setting up automatic replies takes under two minutes in both major email clients.
Microsoft Outlook (new version):
- Go to View then View Settings then Accounts then Automatic Replies
- Toggle Turn on automatic replies
- Set your date range and type your message
- Optionally configure a separate message for people outside your organization
Gmail:
- Open Settings (gear icon) then See all settings
- Scroll to Vacation responder and toggle it on
- Set your first and last day, then write your message
- Choose whether to send to everyone or only to people in your contacts
One underused feature in both clients: set a different OOO for internal vs. external senders. Your colleagues do not need your full professional auto-reply. Your clients and prospects do.
Why Do Cold Emailers Receive So Many OOO Replies - and What Should They Do?
If you run outbound sequences at any volume, OOO replies are a constant. According to HubSpot (2023), the average business professional receives 121 emails per day. During peak holiday periods, OOO auto-replies can account for 15 to 25 percent of all inbound replies on a given sending day.
Most cold email platforms treat OOO replies as noise - they get filtered out and the prospect quietly drops from the sequence. That is a pipeline leak.
What high-performing sales teams do with OOO replies:
- Extract the return date. If the reply says "back on July 14th," that is your follow-up trigger. Pause the sequence and schedule a personalized email for July 15th.
- Read the alternate contact. If the OOO mentions a colleague with decision-making authority, that is a warm path into the account.
- Do not resend the same message. When the prospect returns, they have hundreds of unread emails. Your re-engagement note should reference the timing: "I reached out while you were away - wanted to reconnect now that you're back."
According to Yesware (2023), personalized follow-up emails sent the day a prospect returns from vacation see 34% higher reply rates than generic sequence emails sent at random intervals.
How AI Tools Handle OOO Replies in Cold Email Sequences
Not all cold email automation platforms handle OOO replies the same way. The gap between basic detection and intelligent rescheduling is significant.
| Platform | OOO Detection | Auto-Pause Sequence | AI-Suggested Follow-up | Return Date Extraction |
|---|---|---|---|---|
| Outreach | Yes | Manual rule required | No | No |
| Salesloft | Yes | Manual rule required | No | No |
| Apollo.io | Basic | Yes | No | No |
| Instantly.ai | Basic | Yes | No | No |
| Klipy | Yes | Automatic | Yes | Yes |
Klipy's AI follow-up drafts automatically parse OOO reply content - including return dates - and surface a suggested follow-up task timed to land the day after the prospect is back. The unified inbox flags OOO replies separately from genuine responses, so your pipeline view stays clean and your reps focus only on real conversations.
Klipy's task suggestions converts each OOO into a scheduled touchpoint. The rep sees: "Sarah Chen returns July 14. Draft follow-up ready for review." No manual CRM entry. No dropped leads.
What to Include in Your OOO - and What to Leave Out
Not everything belongs in an auto-reply. Here is a quick reference before you hit save.
Include:
- Specific return date
- Whether you are monitoring email (yes, no, or limited)
- Alternate contact name and email for urgent matters
- A booking link if you want people to schedule time for when you are back
Leave out:
- Your exact location or travel itinerary - stating "I am in Paris until July 14th" tells anyone who emails you that your office is unattended
- Personal phone numbers unless absolutely necessary
- Promises you cannot keep, such as "I will respond within 24 hours" on a two-week trip
- Anything requiring the reader to take more than one action
For sales reps specifically, consider adding a meeting scheduler link so interested prospects can book time for your return date without waiting for a back-and-forth exchange.
Turning OOO Replies Into Pipeline With Klipy
At scale, the OOO problem is a volume problem. When you send 500 cold emails a week, manually tracking which prospects are away and when they return is a full-time job - one that usually does not get done.
Klipy's interaction capture logs every reply, including OOO auto-replies, against the contact record automatically. No manual CRM updates. When the prospect returns, Klipy's proactive sales CRM resurfaces them in your active pipeline with full context: what you sent, when you sent it, and what they replied.
For founders running their own outbound or SMB sales teams operating without a dedicated RevOps function, this kind of automated follow-through closes the gap between outreach volume and actual revenue without adding headcount.
If you are refining your cold outreach workflow, the free AI follow-up email generator can help you draft the re-engagement message for when your prospect gets back.
