Out-of-Office Message: Six Examples With a Reliable Handoff
Choose from six complete out-of-office messages, set realistic response expectations, and check Gmail or Outlook dates, audience, and coverage before leaving.
A good out-of-office message says when you will return, whether you will read email, and how genuinely urgent work should be handled. Keep the promise realistic and the personal detail minimal. Before switching it on, confirm that any named backup has agreed to cover and that the automatic reply ends when you intend.
An automatic reply is a signpost. It cannot approve a request, transfer responsibility, or make an unavailable colleague available. The useful work is making the signpost match the actual arrangement.
Table of contents
- What should your out-of-office message say?
- Which of these six messages fits your absence?
- How do you set the dates and audience correctly?
- What should you check before leaving?
- How do you return without promising too much?
- Frequently asked questions
What should your out-of-office message say?
Include your availability, return date, response expectation, and a valid route for time-sensitive work. Omit any field that would force you to invent coverage or make a promise you cannot keep.
Use four checks before drafting:
- Date: Is this the first day back, or the last day away?
- Availability: Will you actually check email?
- Response: Can the message wait, and what should the sender expect?
- Coverage: Who can help, with which requests, and through what channel?
Write “I return on October 19” instead of “I am away until October 19” if the latter could be misunderstood. Use the month name when readers may follow different numeric date conventions.
Microsoft supports different reply audiences for relevant work or school accounts. Take advantage of that distinction: colleagues may need a project contact, while external senders may only need an approved support route.
Avoid listing travel locations, medical details, or a colleague's private phone number. The reader needs a way to handle the work, not a detailed account of your absence.

Which of these six messages fits your absence?
Choose the message that matches your real availability and coverage. These six original examples use fictional arrangements; replace the circumstances with facts and approved contact details before using one.
1. Short absence, no immediate coverage needed
Thank you for your message. I am away from email today and return on October 19. I will review messages after I return. If your request has a deadline, please include it clearly in your email.
2. Vacation with an established support route
Thank you for your email. I am on leave and will return on October 26. I will not be checking this inbox while away. For urgent product-support requests, please use the support form on our website so the on-duty team can help. Other messages will be reviewed after I return.
3. Conference with limited availability
Thank you for getting in touch. I am attending a conference through October 22 and may be slower to respond. I return to my usual schedule on October 23. For an urgent issue on an existing project, please contact your usual project-support contact rather than waiting for this inbox.
4. A day of focused work
Thank you for your message. I am away from email for focused project work today and will review messages tomorrow, October 20. For a time-critical issue, please use our agreed escalation channel. This reply does not confirm that I have reviewed your request.
5. Leave with no individual backup
Thank you for your email. I am unavailable until I return on November 2 and cannot respond during that time. There is no alternate contact for my individual work. If your request cannot wait, please make another arrangement rather than relying on a reply before that date.
6. Internal team handoff
I am away through October 16 and return on October 19. Jordan is covering approvals for the onboarding pilot; please contact Jordan through the team directory. The current project status and handoff notes are in the shared project folder. Other requests can remain in this inbox for my return.
Use the last version only after the named colleague agrees. Do not paste the example as though those arrangements already exist. Similarly, use a support form or escalation channel only when it is real and appropriate for the sender.
For Gmail, remember that a responder is not a receipt for every message: Google says replies usually go out on the sender's first message, with possible repeat replies after four days or after you edit the response.
How do you set the dates and audience correctly?
Use your provider's official instructions and check the account type. A familiar-looking mail application does not guarantee that every connected account supports the same automatic-reply feature.
In desktop Gmail, go to Settings, then See all settings, then the General tab's Vacation responder section. Enter the dates, subject, and message, choose the audience option if needed, and save. Google's guide says the responder starts at 12:00 AM on the start date and ends at 11:59 PM on the end date unless ended earlier.
For new Outlook, Microsoft's instructions direct you to settings, then Accounts and Automatic Replies. Set a time period and review the external audience. Classic Outlook uses File and Automatic Replies for supported accounts. Follow the appropriate version tab if your screen differs.
Do not assume Outlook's built-in feature covers a Gmail, Yahoo, or other POP/IMAP account. Microsoft documents account limitations and an alternative rules approach. For those accounts, check the provider's own vacation-response feature first.
These links and instructions were checked on October 10, 2026. Menus can change; the official account-specific guide should resolve differences.

What should you check before leaving?
Verify the response, coverage, and unfinished commitments as one small handoff. A polished message cannot compensate for a deadline that nobody knows they now own.
Use this five-point check:
- Read the return date aloud and compare it with your calendar.
- Confirm the backup person's agreement and scope of responsibility.
- Verify any support link or contact route from the recipient's perspective.
- Check which internal and external senders will receive the response.
- Confirm the scheduled end and test delivery when appropriate.
Be careful with external replies. Microsoft warns that broad external responses can also reach newsletters, advertisements, and junk senders; it recommends the contacts-only option when appropriate.
Resolve outstanding promises before archiving anything. Our inbox-zero guide focuses on decisions and commitments, which is useful here: identify what can wait, what needs an answer, and what another person has actually accepted.
For a deadline you cannot cover, send a direct message before leaving. An automatic reply discovered afterward is a poor substitute for setting a clear work boundary while the other person can still adjust.
How do you return without promising too much?
Turn off the reply if necessary, check coverage handoffs, and review time-sensitive commitments before trying to clear every message. Your first day back needs priorities, not a race against an arbitrary inbox count.
Start with work whose consequences changed while you were away. Ask the covering colleague what was resolved and what still needs you. Then choose a small set of meaningful outcomes using a daily planning template.
Do not promise every sender a response on your first morning unless that is realistic. “I will review messages after I return” leaves room for triage without pretending that every request has the same urgency.
Do Only 3 Things a Day provides the daily card, review loop, and seven-day start for that return. The aim is to resume useful work without immediately recreating the overload you stepped away from.
Frequently asked questions
Do I need to say why I am away?
Usually the availability and return date are enough. Include a reason only when it helps the reader and you are comfortable sharing it. Follow your organization's communication requirements where they apply.
Should I promise an immediate response?
Only if you can deliver it. Otherwise describe when you will review messages and provide an appropriate urgent route. A reassuring promise becomes unhelpful when the sender relies on it and nothing happens.
Why did someone not get my reply?
Check the audience settings and provider rules. Google says spam and mailing-list messages do not receive its vacation reply. Repeat senders may also not receive a new response each time. Consult the official guide before assuming setup failed.
What if there is nobody to cover?
Say so clearly and avoid inventing an urgent contact. Notify people with active deadlines before you leave, agree what can wait, and direct senders to another arrangement when your absence makes their deadline impossible.