At the start of customer communication
How to write an initial incident acknowledgment
Write the first customer-facing incident message from verified impact, scope, times, explicit unknowns, current investigation state, and a specific next-update commitment.
Confirm the communication trigger and audience
Use your team’s incident and notification process to confirm that customer communication should begin, who the affected audience is, and which channels to use. This guide starts after that decision; it does not set a universal trigger or audience.
Lead with the customer-visible impact
State the affected workflow and what customers may be unable to do or may experience. Use plain customer language and keep internal component names out unless they help explain a verified customer effect.
Bound the affected scope
Name the verified region, plan, workspace group, feature, or other affected subset. Mention an unaffected scope only when your team has verified it, and do not turn a partial observation into a percentage or customer count.
Anchor the message in time
Include when the customer-visible impact was first observed and the time of the current update, with timezones. Distinguish observed impact from when an internal alert fired or the team began investigating.
Keep unknowns explicit
If the cause, full scope, customer action, or restoration estimate is not confirmed, say so or omit the claim. Do not turn a hypothesis, elapsed time, or investigation path into a published fact.
Describe only verified response activity
State that the team is investigating or reviewing the verified issue only when that work is current. Do not imply that a fix, mitigation, recovery, or vendor response exists until the responsible team has confirmed it.
Set the next update commitment
Give one specific next-update time with a timezone that the communication owner can keep. Publish again at that time even if there is no material change, unless a verified material change requires an earlier update.
Align and review every channel
Check that the status page, customer email, in-app message, and support response selected by your team share the same impact, scope, times, unknowns, current state, and next-update commitment before publication.
Draft from verified facts.
The free acknowledgment and resolution composer runs entirely in your browser.
Open the composer →