Out-of-office message templates for customers, teammates and leave
Out-of-office message templates for customers, teammates, vacation, leave, and shared support inboxes, with timing, handoff, and privacy checks.
Is it right for you?
- Set the exact start and end time in the email system.
- Write separate internal and external replies when needed.
- Confirm the cover contact has context and authority.
- Remove private leave details and personal contact information.
- Test the reply from an external address before leaving.
Quick verdict
An out-of-office reply should tell the sender when they can expect a response and what route to use if they need help sooner. Keep the reason for the absence optional. A customer-facing reply must name a monitored alternative only when someone has agreed to cover the work.
What an out-of-office reply needs to do
A useful auto-reply has three pieces: availability, the expected response time, and an alternative route for time-sensitive work. It does not need a detailed explanation of where someone is or why they are away.
Microsoft's automatic-reply guidance allows a sender to set a time range and separate replies for people outside the organization. Use that separation when customers need a different support route from teammates [Microsoft Support, 2026].
Customer-facing templates
Short absence
Thanks for your message. I am away until [return date] and will reply when I return. For help with [specific topic], contact [monitored team email or phone].
Support coverage
We received your message. Our team is currently away and will respond by [date and time]. For an urgent issue that meets [defined condition], contact [monitored route].
Appointment or service business
Thank you for contacting [Business]. We are away until [return date]. To request or change an appointment, use [booking link or monitored phone number].
Longer leave
Thank you for your message. I am away from work until [return date] and will not be monitoring email. For [work area], please contact [team or named cover contact].
No cover contact
Thanks for your email. I am away until [return date] and will respond after I return. I do not have email coverage during this period.
Internal templates
Teammate coverage
I am away from [start date] through [end date]. [Name] is covering [specific queue, customer group, or task]. Please add urgent items to [shared channel or list].
Project handoff
I am unavailable until [return date]. The current status of [project] is [one sentence]. The next decision is [action] by [date]. [Name] owns questions while I am away.
Limited access
I have limited email access until [return date]. I will review messages intermittently, but please use [team route] for anything that needs a response before then.
Use a truthful handoff
Do not put a colleague's name into an auto-reply unless that person knows they are covering the work and can access the needed systems. A customer who writes to an unprepared cover contact has simply been moved to another delay.
For a shared support inbox, the reply should name a response window the team can meet. If the whole team is unavailable, say so and provide a date and time. Do not promise an urgent response because it sounds reassuring.
Microsoft's setup instructions also note that external replies are a separate setting. Send a test email from outside the organization to confirm the correct message and time range are active [Microsoft Support, 2026].
Privacy and security checks
Avoid medical, family, travel, or location details. The sender needs availability information, not a personal explanation. "I am away until June 12" is normally sufficient.
Avoid listing a personal mobile number unless it is the established customer-support route and the owner has agreed to use it. Keep time-sensitive business messages in systems where the team can see the history.
Do not include account information, order details, or confidential project status in an auto-reply. Auto-replies may reach people outside the organization.
Set the message before the absence starts
Microsoft recommends setting a defined automatic-reply time range rather than relying on memory to turn the message off. Set the end time before leaving, then calendar a brief review on the return day [Microsoft Support, 2026].
For a one-person business, a simple response-time message often works better than an elaborate template. State the return date, point customers to the best active route, and remove the reply when the business is available again.
Frequently asked questions
Q: Should I say why I am away?
A: Usually no. State the timing and the next contact route. Add a reason only when it helps the sender understand a business process.
Q: What should a customer-facing message include?
A: Include the response date or window and a monitored alternative contact route when one exists.
Q: Can I promise an urgent response?
A: Only if a named person or team is actually responsible for responding and has the authority to help.
Q: Should internal and external auto-replies be different?
A: Often yes. Teammates may need project handoff details, while external senders need a concise response expectation and support route.
Q: What should I write for parental or medical leave?
A: Keep it private. State that you are away until a return date and identify the work contact route if applicable.
Q: How do I avoid stale auto-replies?
A: Set a start and end time, test it from an external address, and review the message on the return day.