← Back to Blog
EmailMay 10, 2026·7 min read

Out-of-Office Message Examples (2026): 9 Templates That Don't Read Like Spam

Most out-of-office auto-replies sound like they were written by a corporate communications committee in 2014. Below are 9 real templates by scenario that read like they came from an actual person, plus the 5 phrases that immediately signal “copy-pasted from a HR portal”.

Skip the writing entirely with our free OOO message generator, or read on for the templates.

The 5-line structure that works

Every good OOO follows this skeleton:

  1. Greeting (1 line): friendly but appropriate to the scenario.
  2. Status (1-2 sentences): what's happening, when you're back.
  3. Email handling expectations (1 sentence): “I'll respond when I return” vs. “I'll reply on a 1-week delay”.
  4. Alternative contact (only if relevant): what to do for urgent matters.
  5. Closing (1 line): warm sign-off.

1. Standard 1-week vacation

Use when: Standard short vacation

Hi,

I'm out of the office until October 17 and away from email.

I'll work through my inbox in order when I'm back. If something is genuinely time-sensitive, please reply with 'URGENT' in the subject so I can prioritise it on my first day back.

Thanks for your patience,
Alex

2. Long vacation (3+ weeks)

Use when: Extended absence

Hello,

I'm on extended leave through November 15. I'll be checking email about once a week to handle anything truly urgent, but most messages will sit until I'm back.

For anything client-related, please reach out to Sarah Chen (sarah@company.com) — she has full context on active accounts and can decide what needs to wait for me vs. what needs to be handled now.

For everything else, I'll respond when I return.

Thanks for your patience,
Alex

3. Parental leave

Use when: Parental leave

Hi,

I'm on parental leave until February 2027 to spend time with our new arrival.

I won't be checking email at all during this time. For client-facing matters, please reach Marcus Reyes (marcus@company.com), who's handling my accounts. For internal matters, my team lead Priya Patel (priya@company.com) is the right contact.

Looking forward to catching up when I'm back,
Alex

4. Conference / off-site

Use when: Conference attendance

Hi,

I'm at the Marketing Operations Summit in Austin through Friday. Email response will be slower than usual — I'll batch replies once or twice a day.

If it's something I'd want to know about now (a big client issue or a press inquiry), please text me at +1 555-XXX-XXXX. Otherwise, I'll get to your message in the order I see it.

Thanks,
Alex

5. Sick leave

Use when: Sick leave

Hi,

I'm out for a personal health matter and will be back on Monday, October 21. I won't be checking email until I'm back.

For anything urgent on the [Project X] launch, please reach Daniel Lopez (daniel@company.com) — he's covering my work this week.

Thanks for your understanding,
Alex

6. Sabbatical

Use when: Sabbatical

Hi,

I'm on a 3-month sabbatical and will return January 5, 2027. I'll be entirely off email during this time and won't see your message until I'm back.

For anything that genuinely can't wait until January, please contact our CEO, Sarah Chen (sarah@company.com), who can route to the right person.

Looking forward to reconnecting in the new year,
Alex

7. Holiday closure (whole company)

Use when: Holiday closure

Hi,

[Company Name] is closed from December 24 through January 2. Our team will return to email on January 3 and respond in the order messages were received.

For account emergencies, please email support@company.com — that inbox is monitored by an on-call team member during the closure.

Wishing you a restful end of year,
[Company Name] Team

8. Limited connectivity / remote area

Use when: Limited connectivity

Hi,

I'm travelling through October 28 and will have intermittent internet access. I'll be batching email replies whenever I get a stable connection — expect responses within 24-48 hours rather than the usual same-day.

For anything time-sensitive on [Project Y], please reach Sarah Chen (sarah@company.com) for faster turnaround.

Thanks for the patience,
Alex

9. Brief / minimal (internal only)

Use when: Internal-only short OOO

Out until Monday. Catch up with you then.

— Alex

5 phrases to delete from every OOO

  1. “Sorry for the inconvenience.” You're taking a vacation — that's not an inconvenience, that's a normal part of working. Apologising for it teaches senders you owe them something for being away.
  2. “I'll get to your email as soon as humanly possible.” Manipulative urgency. Just say when you'll respond.
  3. “Your message is important to me.” If it actually were, you'd be reading it. Skip the corporate placation.
  4. “During my absence, please direct your inquiry to...” Robotic. “If it's urgent, reach Sarah at...” works the same with half the words and twice the warmth.
  5. “Thank you for your understanding.” Recipients haven't agreed to understand anything yet. The phrase pre-empts a complaint that probably wasn't coming.

Frequently asked questions

Should I include the exact return date in my OOO?

Yes if you can commit to it. Vague language like 'I'll be back soon' frustrates senders and damages trust. A specific return date with 'I'll respond starting [date]' sets clear expectations and reduces follow-up emails. If you're unsure of the exact date, give a range: 'returning in mid-October' is better than 'returning soon'.

Should my OOO say where I'm going?

No, especially for vacations. Naming a destination is a security signal that you're physically away from home. Keep it generic: 'on vacation', 'travelling', 'away from the office'. The exception is conferences and work-related travel, where naming the event adds professional context.

How long should an out-of-office message be?

25-80 words is the sweet spot. Brief enough to read in 5 seconds (most senders just want the basic info), detailed enough to set proper expectations. The 5-line structure: greeting, your status, expected return, what to do for urgent matters, sign-off.

Skip the writing

Free OOO Message Generator

3 versions per scenario (long, standard, brief). 8 scenarios covered. No sign-up.

Generate OOO message →

More from SwiftCopy

Keep exploring this topic

Keep the session moving with one related guide, one practical tool, and the broader library of workflows built around the same writing jobs.