Most out-of-office messages are too long. I have read roughly four thousand of them, almost all of them sent to me, and the ones I remember are the ones that explained too much. A good OOO reply is a small contract: it tells the sender what to expect, when, and who to talk to instead. Anything past that is a person on vacation narrating their vacation to a stranger who just wanted a status update.
The bar is low, which is the opportunity. A clear, short, slightly human message stands out precisely because most people phone in the auto-reply and move on. Harvard Business Review made this argument years ago: the OOO message deserves more thought than the generic “I’m out until [date]” people default to, and it’s still true. What follows is what I put in mine, and why.
What every out-of-office message actually needs
Three things, in this order:
- That you’re gone, and until when. A specific return date, not “next week.” Senders are usually skimming on a phone; give them the date they can circle.
- What happens to their message. Either you’ll respond when you’re back, or you won’t see it at all. Pick one and say it plainly. “I’ll reply when I return” and “I won’t be checking email” are both complete sentences.
- Who to contact if it can’t wait. A name, a role, and a way to reach them. Not a department inbox. Not “my team.” A person.
That’s the whole structure. Tone, length, and personality are adjustments on top of it, not separate categories. The University of North Carolina’s writing center makes a related point about email generally: the act of sending is instant, but the response isn’t, and most people only keep up with email during their working hours. Your OOO message is the one place you get to set that expectation out loud instead of leaving the sender to guess.
Five messages you can copy
These are deliberately different shapes. Use the one that matches your situation, not the one that sounds the most polished.
1. Standard business absence
This is the default and the one most people should reach for most of the time. It answers the three questions and stops. No apology for being away, no explanation of where you went, no “I’ll have limited access” (which is vague enough to mean almost anything). If you only ever send one kind of OOO message, send this one.
2. Short vacation / PTO
The difference from the standard version is mostly tone, and the word “patience” does real work here – it acknowledges the sender is waiting without apologizing for taking the time off. You earned the days. Don’t apologize for using them. The one thing I’d cut from most PTO messages I see is the line about “limited access.” Either you’re checking email or you aren’t. “Limited access” is a hedge that tells the sender nothing and quietly invites them to expect a reply you don’t intend to give.
3. Extended leave (parental, medical, sabbatical)
Extended leave is the one case where I think a longer message is justified, because the absence is long enough that “I’ll reply when I’m back” stops being a real promise. The sender needs a different path, so give them two: a named person for anything specific, and a team inbox for general questions. I keep this one deliberately non-specific about the reason. “Extended leave” covers parental, medical, sabbatical, and anything else, and you are not obligated to disclose which. If your company culture expects more detail, add it. But the default should be that the reason is yours.
One opinionated note: if you’re going to be gone more than two weeks, ask the person covering for you before you name them. Naming a colleague who never agreed is the single most common OOO mistake I see, and it’s rude in a way people rarely call out. A three-second message – “Mind if I list you as my backup while I’m out?” – is all it takes.
4. No email access / emergency contact only
This is the bluntest version, and it exists for a reason. Some roles genuinely can’t be reached – field work, travel without reliable connectivity, genuine disconnect on a real vacation. The key phrase is “will not be read.” That’s different from “I’ll reply when I’m back,” because it tells the sender their message may never be seen at all, so they’d better route it somewhere else now. Use this one sparingly. If you say you won’t be checking and then you check, you’ve trained people to ignore the next one.
5. A warmer, more personable variant
I use this one for client-facing work and small teams where the default corporate register would feel stiff. The shifts are small – “thanks for reaching out” instead of “thanks for your message,” “happy to help” instead of “please contact,” “catching up” instead of “responding.” None of it is unprofessional. It just sounds like a person wrote it. The risk is overdoing it; a little warmth goes a long way, and a joke about where you’re vacationing almost never lands the way you think it will. Keep the warmth in the verbs, not the asides.
Tone, by audience
Calibrate to who’s reading. An internal OOO to your team can be casual and short – they already know the context. A client-facing message should be warmer but still tight; the goal is to reassure, not to entertain. A message that might reach customers, vendors, or anyone outside your company should default to the standard version, because you can’t predict who’ll see it and the safest tone is the one that can’t be misread.
One thing I’d avoid across the board: the humorous OOO. I’ve tried it. The joke that’s funny to your team is confusing to a vendor you’ve never met, and the one that lands on Monday reads as smug by Thursday. If you want personality, put it in word choice, not in a bit.
The mistakes I see most often
- Naming a backup who never agreed. Always ask first. This is non-negotiable and it’s the one I see most.
- Forgetting the end date. “I’ll be out for the next few days” is useless to someone reading it on day four. Give a date.
- Leaving it on after you’re back. The auto-reply that’s still firing two weeks after you return is worse than no message at all. Turn it off the day you return, or set it to expire automatically.
- Apologizing for being away. “Sorry for the inconvenience” on a PTO message is a tell. You’re allowed to take time off.
- Over-sharing the reason. “I’m on a two-week honeymoon in Greece” is more than the sender needs. “I’ll be away until [date]” is enough.
- The vague “limited access” line. Pick a lane. You’re either checking or you’re not.
If you want a faster path to a message that’s already calibrated, WriteMail.ai can draft one from a couple of details – but the structure above is the part worth remembering. Get the three things right and the rest is style.
Set it before you need it
The last mistake is the one nobody lists: writing the message the morning you leave, in a rush, with one foot out the door. That’s when people over-share, forget the end date, and name a backup they haven’t asked. Write it the day before. Read it once. Then turn it on and stop thinking about it, because that’s the whole point of being out of the office.
