Downtime Notifications
Planned maintenance, outage alerts, and resolution updates.
Revised Format
Hi {{cursor}},
Thank you for reaching out regarding revised format.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
If you need any clarification, I am available to chat anytime this week.
Best regardsInitial Notice
Initial Notice
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of initial notice]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Follow-Up Message
Hi {{cursor}},
Quick update on follow-up message:
[Key information]
Let me know if you have any questions.
BestStandard Communication
Standard Communication
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of standard communication]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Formal Reminder
Hi {{cursor}},
I wanted to follow up with you about formal reminder.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
If you need any clarification, I am available to chat anytime this week.
Best regardsFriendly Confirmation
Friendly Confirmation
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of friendly confirmation]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Brief Report
Hi {{cursor}},
Quick update on brief report:
[Key information]
Let me know if you have any questions.
BestDetailed Guide
Detailed Guide
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of detailed guide]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Professional Brief
Hi {{cursor}},
Thank you for reaching out regarding professional brief.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
I look forward to hearing from you. Feel free to reply to this message or schedule a call.
Best regardsQuick Draft
Quick Draft
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of quick draft]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]When to use this template
- Planned maintenance window scheduled. Notice 48-72 hours in advance with affected services and the maintenance window in user-friendly time.
- Active outage notice within minutes of detection. Even a 'we're investigating' note is better than silence.
- Resolution email when the issue is fixed with a one-paragraph plain-English summary of what happened.
Customize for your workflow
- Have a status page URL that auto-updates. Email is too slow for active incidents; the status page is where users go.
- For multi-region products, specify which regions are affected. 'EU users may see slowness; US is unaffected' is more useful than blanket alerts.
Common questions
How often should I update during an active incident?
Every 30 minutes minimum, even if the update is 'still investigating'. Silence past an hour signals you don't know what's happening.
Do I need a separate post-mortem?
Yes — for engineering and stakeholders, not the users themselves. Customer-facing post-incident notes should be one paragraph; the full post-mortem is internal.
Related reading
More SaaS & Product Templates
Release Notes Templates
Changelog and version update announcement formats.
10 snippetsUser Onboarding Emails
SaaS product onboarding sequences and activation emails.
9 snippetsFeature Announcement
New feature launch messages and product update notifications.
8 snippetsBeta Program Templates
Beta invite, feedback collection, and early access communications.
9 snippetsChurn Prevention Messages
At-risk user re-engagement and cancellation prevention templates.
11 snippetsProduct Feedback Requests
NPS surveys, feature requests, and user research recruitment.
8 snippetsUse these snippets in TypeFire
Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.