unavailability_notice_email
Draft a heads-up email to clients about your upcoming absence — vacation, conference, or personal — with exact dates and pre-departure deliverables, so clients aren't surprised when you go offline.
Instructions
Write a proactive heads-up email to an active client before you go away — annual leave, a personal absence, or a conference/training. Sends this BEFORE you leave so the client isn't surprised when you go quiet. Three routes: vacation (default — fully offline; states the exact dates, what you'll complete before you go, and when you'll respond on return; gives the client confidence that active work is handled), conference_or_training (professional development; acknowledges you may check email intermittently; warmer tone since you're still reachable in genuine emergencies), personal (minimal detail — just the dates and return; no explanation required). Distinct from project_pause_email (formal indefinite pause, often for non-payment), availability_announcement_email (announcing new slots for future work), and project_delay_notification_email (your own delay mid-project). Does not count against your monthly draft limit. Required: client_name, return_date (when you'll be back — e.g. 'Monday 7 July', 'next Thursday'). Optional: project_name, from_date (first day away — e.g. 'Friday', '27 June'; omit if sending on the day of departure), pre_absence_deliverable (what you'll complete before you leave — e.g. 'the first-draft wireframes', 'the revised copy'), cover_contact (name + email of someone handling genuine emergencies — omit if you have no cover), route ('vacation' | 'conference_or_training' | 'personal' — default vacation), your_name.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| client_name | Yes | Client first name | |
| return_date | Yes | When you'll be back and responding to emails — e.g. 'Monday 7 July', 'next Thursday', '14 July'. Give a specific date so the client has a concrete expectation. | |
| project_name | No | Optional: project name — e.g. 'the Hartley website', 'your brand refresh'. Makes the email specific rather than generic. | |
| from_date | No | Optional: first day away — e.g. 'Friday', '27 June', 'tomorrow'. Omit if sending on the day of departure. | |
| pre_absence_deliverable | No | Optional: what you'll complete and send before you leave — e.g. 'the first-draft wireframes', 'the revised copy deck', 'the updated timeline'. Reassures the client that active work is handled. | |
| cover_contact | No | Optional: name and contact for genuine emergencies — e.g. 'Sarah (sarah@agency.com)'. Omit if you have no cover. Do not list a cover contact unless you have one — a named contact who doesn't respond is worse than no contact. | |
| route | No | vacation (default) — annual leave, fully offline; conference_or_training — professional development, may check email intermittently; personal — minimal detail, just the dates. | |
| your_name | No | Optional: your name for the sign-off |