Created by the First Role Skills Editorial Desk. This lesson uses a fictional workplace scenario and links to primary product documentation where the interface or feature matters.
Start with the work
A realistic scenario
You will be unavailable for two workdays. Clients need to know when you will return, but they do not need personal travel details or a list of every colleague.
Avoid rework
Three beginner mistakes
Writing 'I am unavailable' without a return date
Sharing personal location or travel plans
Naming a backup person who has not agreed to cover
The method
Complete it in six controlled steps
- 01
Confirm the exact window
Record the last working day, the unavailable dates, and the first day you can respond. Use an unambiguous date format such as 14 August 2026.
- 02
Set a realistic expectation
Say whether messages will not be monitored, checked occasionally, or answered after your return. Do not promise a response time you cannot meet.
- 03
Choose one escalation route
For urgent matters, point to a shared inbox, support channel, or approved colleague. Confirm that the destination is active and has the necessary context.
- 04
Remove unnecessary detail
The recipient needs operational information, not a personal explanation. Keep the body to three or four short sentences.
- 05
Match internal and external versions
An internal reply can name a team channel. An external reply should use a public business contact and avoid internal system names.
- 06
Test and schedule
Check dates, links, signatures, and recipients. Send a test from another address if possible, then confirm the responder is disabled when you return.
See the difference
Before and after
Hi! I am on holiday and may not see this. Try someone else if it is important.
Thanks for your message. I am away through 14 August and will reply from 17 August. For urgent account access, contact support@example.com.
Original practice
Complete the exercise
Write two versions for the same absence: one for co-workers and one for external senders. Compare what information changes and explain why.
Use only fictional or fully anonymized data. Never upload an employer's confidential information to a portfolio.
Explain your decisions
Turn the exercise into credible evidence
Save the two messages beside a short comparison note. Explain why the internal version can reference a team channel while the external version uses a public business route. Record how you verified the dates, backup contact, and response expectation. The useful evidence is not a screenshot of the responder switch; it is your reasoning about audience, privacy, escalation, and the promise you can realistically keep.
Quality gate
Check your own work
- Return date included
- Monitoring expectation stated
- Backup route confirmed
- No private travel details
- Responder tested