A supplier has acknowledged an outage and your internal response needs a stable reference and verified update route.
The useful bits
- Affected service and period
- Supplier’s official incident channel
- The reply should establish a stable reference and a trustworthy route for changing status information.
Before you write
Use this example when a supplier has acknowledged an outage and your internal response needs a stable reference and verified update route. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Affected service and period
- Supplier’s official incident channel
- Internal incident owner
An email you can adapt
The subject “Incident reference for [service issue]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Incident reference for [service issue] Hi [name], We are tracking the effect of [issue] on [workflow]. Please provide the official supplier incident reference and the approved source for status updates. We need confirmed impact, known limitations and the next update checkpoint rather than an unsupported recovery promise. [Internal owner] will coordinate our response and avoid sending duplicate requests. Please identify any customer action that is actually required, with the relevant official guidance. Best, [sender]
Check the boundary
Separate the supplier’s verified incident information from speculation about cause or recovery time.
What a useful reply should settle
The reply should establish a stable reference and a trustworthy route for changing status information.
Use that route for subsequent updates and record what was known at each internal decision point.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction
