Most out-of-office messages fail the same way: they tell the sender you're away without telling them what to do next. A great OOO isn't just a notice - it's a decision tree that runs on your behalf while you're gone.

Here's how to write one that actually works: the structure, the tone variants, the internal-vs-external distinction, and the most common mistakes to avoid.

The anatomy of an effective out-of-office message

Every good OOO message answers four questions, in order:

Am I available? No. Say so directly. Avoid "limited access to email" when you mean "I will not see this until I'm back."
Until when? Give the exact return date, not a vague range. "Back on 14 July" is more useful than "back in a couple of weeks."
What happens to this email? Will you read it on return? Will it be archived? Should the sender resend?
Is there an urgent escalation path? Only include one if it's real. A fake urgent contact is worse than none.

Keep it short. Two sentences of context and one sentence of escalation beats four paragraphs of apology.

Standard OOO (professional)

Thank you for your email. I'm out of office from [START DATE] to [END DATE] and will reply when I return. For urgent matters, please contact [NAME] at [EMAIL].
[YOUR NAME]

Minimal / no-contact OOO

For roles where there genuinely is no one covering and no urgent path exists.

I'm away until [DATE] with no access to email. I'll reply to everything when I'm back - no action needed on your end.
[YOUR NAME]

Extended leave (three weeks or more)

Longer absences require explicit guidance on what happens to the email itself - otherwise senders don't know whether to wait or resend.

I'm on leave through [DATE] and won't be monitoring this inbox. Messages won't be read on my return - please resend anything time-sensitive after [DATE]. In the meantime, [NAME] at [EMAIL] can help with [AREA OF RESPONSIBILITY].
[YOUR NAME]

Parental leave

I'm on parental leave until [DATE] and won't be checking messages. For ongoing work, [NAME] at [EMAIL] is the right contact. For everything else, I'll be back on [DATE] and will respond to messages then.
[YOUR NAME]

Medical leave

Keeps the reason vague (as it should be) while still giving a clear path forward.

I'm currently on medical leave and not available by email. My colleague [NAME] ([EMAIL]) is handling my work during this time and can assist you.
[YOUR NAME]

Internal OOO (different from external)

Both Gmail (Workspace) and Outlook let you write separate messages for people inside and outside your organisation. You should use this feature. Internal colleagues usually need more operational detail - where to find files, who has the access, which Slack channel to use. External contacts need less.

Internal version:

I'm out until [DATE]. [NAME] is covering for me - they have access to [PROJECT FOLDER] and are up to speed on [CURRENT PRIORITIES]. For anything else, ping me on Slack when I'm back.

External version:

Thank you for your email. I'm out of office until [DATE]. For urgent questions, please contact [NAME] at [EMAIL].

How to set up the internal/external split

Gmail (Google Workspace)

Go to Settings → See all settings → General → Vacation responder. For Workspace accounts, you'll see a checkbox: "Only send a response to people in [your organisation]." This limits the OOO to internal senders. To send different messages to internal vs external contacts, you'll need to use a Filter + Canned Response (now called Templates) - create a filter matching senders outside your domain, apply the template as an auto-reply. It's more work to set up but gives you full control.

Outlook (Microsoft 365)

Outlook's automatic replies natively supports two separate messages: one for people inside your organisation, one for people outside. Go to File → Automatic Replies → then fill in both tabs. This is the cleanest implementation of the internal/external split and the main reason Outlook's OOO feature is more flexible than Gmail's for corporate use.

Tone variants

The templates above are written in a professional neutral voice. Depending on your context, you might want to adjust:

Context	Tone note	What to change
Startup or creative agency	Warmer, first-person	Replace "I am out of office" with "I'm away"; drop the formal opening
Legal or financial services	Precise, no contractions	Avoid contractions; name the return date explicitly
Sales or customer-facing	Reassuring	Name the colleague covering and confirm continuity of service
Personal email	Casual	Drop the "Thank you for your email" opener; write as you'd speak

Common mistakes

Vague dates

"Back soon" or "returning shortly" forces senders to guess. Always give a specific date. If the return date is uncertain, give a conservative estimate: "I expect to be back by [DATE] at the latest."

Fake urgent contacts

Listing a colleague as the urgent contact when they're not actually covering creates a problem for both of them. If there's no real escalation path, say so - it's more honest and the sender will respect it.

Oversharing

Saying you're at a conference in Barcelona or on a beach in Crete is unnecessary information for most senders. "I'm away" is enough. Location details are relevant only when senders need to know timezone shifts (e.g. "I'm at a conference in the US this week, so replies may be slow until Thursday European time").

No guidance on stale messages

For absences longer than a week, you need to tell senders what to do with the email they just sent. Will you read it on return? Should they resend? A message that arrives during a two-week vacation can easily get buried - being explicit about this is not pessimistic, it's useful.

When AI handling improves on static OOO messages

A static OOO message sends the same reply to everyone. That works for binary states - fully away vs. fully present. It starts to fail when the right response depends on who's asking and why. A customer asking about a billing dispute during your holiday needs a different message than a recruiter following up or a colleague checking the status of a shared doc.

An AI email assistant can read the incoming message, classify the intent, and select or draft the appropriate reply - so the billing dispute gets routed to finance, the recruiter gets a polite hold, and the colleague gets pointed to the shared folder. All without you configuring fifteen different Gmail filters. The catch is the usual one: you want the assistant to propose the reply and you to approve it, rather than sending automatically. That's the approval-first model and it's what Inboxer is built around.

For most people: start with one of the templates above, set it up in Gmail or Outlook, and revisit when you notice the one-size-fits-all reply causing more confusion than it solves.