🎧Customer Support

Service Outage

Communication templates for planned maintenance, unexpected outages, and incident resolution.

9 snippets included|Free to download|Works with TypeFire for macOS
Download TypeFire for macOS
zoutage

Outage Acknowledgment

Hi there,

We are aware of an issue affecting [service/feature] and our team is actively working on it.

What we know:
- Issue started: {{date}} at approximately [time]
- Affected: [Description of what is impacted]
- Status: Under investigation

We will provide updates every [30 minutes / 1 hour] until the issue is resolved. You can also check our status page for real-time updates: [Status page URL]

We apologize for the disruption and appreciate your patience.

Best,
{{cursor}}
zoutageupdate

Outage Update

Hi there,

Here is an update on the ongoing issue with [service/feature]:

Current status: [Identified / Monitoring / Implementing fix]
Update time: {{date}}

What has changed:
- [Progress update 1]
- [Progress update 2]

Expected resolution: [ETA if known, or "We are still investigating"]

We understand this is causing disruption and we are treating this with the highest priority. Next update in [X minutes/hours].

Best,
{{cursor}}
zoutageok

Outage Resolved

Hi there,

The issue affecting [service/feature] has been resolved as of {{date}}.

Incident summary:
- Duration: [Start time] to [End time]
- Root cause: [Brief explanation]
- Resolution: [What was done to fix it]

All systems are now operating normally. If you are still experiencing issues, please try [clearing your cache / refreshing / logging out and back in].

We sincerely apologize for the inconvenience. We are taking steps to prevent similar issues in the future, including [preventive measure].

Best,
{{cursor}}
zmaint

Planned Maintenance Notice

Hi there,

We will be performing scheduled maintenance on [date] from [start time] to [end time] ([timezone]).

What to expect:
- [Service/feature] will be temporarily unavailable
- The maintenance window is approximately [X hours]
- No action is required on your end

What will be improved:
- [Improvement 1]
- [Improvement 2]

We have scheduled this during low-traffic hours to minimize the impact. If you have any concerns, please reach out.

Best,
{{cursor}}
zdegrade

Degraded Performance Notice

Hi there,

You may be experiencing slower than normal performance with [service/feature]. We have identified the issue and our team is working on it.

Current impact:
- [What is slower or affected]
- [What is still working normally]

The service is still functional, but you may notice [specific symptoms]. We expect to have this fully resolved by [ETA].

We appreciate your patience while we work to restore full performance.

Best,
{{cursor}}
zpostincident

Post-Incident Report

Hi there,

Following the service disruption on [date], we wanted to share a detailed account of what happened and what we are doing to prevent it from happening again.

Timeline:
- [Time]: Issue first detected
- [Time]: Team engaged and investigation started
- [Time]: Root cause identified
- [Time]: Fix implemented
- [Time]: Service fully restored

Root cause:
[Detailed explanation]

Impact:
- Duration: [Total downtime]
- Affected customers: [Number or percentage]
- Data impact: [None / Description]

Preventive measures:
1. [Measure 1]
2. [Measure 2]
3. [Measure 3]

We take reliability seriously and we are committed to earning your trust. Thank you for your patience during this incident.

Best,
{{cursor}}
z3rdparty

Third-Party Outage Notice

Hi there,

We are currently experiencing issues with [feature/service] due to a problem with one of our third-party providers ([Provider Name]).

This is affecting:
- [What is impacted]

This is NOT affected:
- [What still works normally]

We are in contact with [Provider Name] and monitoring the situation closely. We will update you as soon as we have more information from their team.

For real-time updates, please check: [Status page URL]

We apologize for the inconvenience.

Best,
{{cursor}}
zemergmaint

Emergency Maintenance

URGENT: Emergency Maintenance Required

Hi there,

We need to perform emergency maintenance on [service/feature] starting at [time] today. This is necessary to [reason - e.g., address a security vulnerability / resolve a critical database issue].

Expected impact:
- [Service] will be unavailable for approximately [duration]
- Your data is safe and will not be affected

We understand this is short notice and apologize for the inconvenience. This maintenance is critical to ensure the continued security and reliability of the platform.

We will send an update once maintenance is complete.

Best,
{{cursor}}
zrestored

Service Restored - Thank You

Hi there,

All systems are back to normal. Thank you for your patience during the disruption.

If you saved any work locally during the outage, now is a good time to sync it. Everything should be working as expected.

If you encounter any lingering issues, please let us know immediately and we will prioritize your case.

We appreciate your understanding and we are sorry for any inconvenience this caused.

Best,
{{cursor}}

When to use this template

Customize for your workflow

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 reads as 'they don't know what they're doing'.

Do I need a separate post-mortem template?

Yes — but for engineering and stakeholders, not customers. Customer-facing post-incident notes should be one paragraph. The 10-page post-mortem is internal.

Related reading

More Customer Support Templates

Use these snippets in TypeFire

Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.

Get TypeFire Free