An incident email can be accurate when drafted and misleading when sent. “We are investigating” may already be out of date; “resolved” may be stronger than the incident owner is willing to confirm. The last fact review matters as much as the first draft.
Use Migma to prepare a clear service notice from approved information, then have the incident and Loops owners review the current state and sending path. This guide is published by Migma. It offers original copy exercises and an editorial handoff, not a declaration that every service message is eligible for every recipient.
Start with the incident owner's statement
Ask for the affected service, confirmed customer impact, current state, observation time, next update plan, and public status destination. Keep unknown causes and unapproved recovery estimates out of the creative brief.
Loops' transactional best-practices resource discusses notices about current service conditions and the importance of clear time-sensitive information. Your operational owner still needs to classify the actual message and determine its appropriate audience and path. A service notice, a later retrospective, and a product announcement do different jobs.
Do not infer scope from a broad headline like “the platform is down.” If only one feature or region is confirmed affected, the email should preserve that limit. A shorter sentence is not better if it changes who appears to be impacted.
Keep three draft states distinct
Use a fictional reporting app with a delayed export feature. The examples below are invented writing exercises. Replace their facts only with details approved for the actual incident, and review the entire sentence after replacement.
Investigating
“Some report exports are taking longer than expected. Our team is investigating the delay. Your saved reports remain available. We will post the next update on the status page.”
Use this only if the impact, saved-report statement, and update process are verified. If data availability is unknown, remove that assurance. Do not add a recovery deadline because it makes the message feel more complete.
Monitoring
“A change has been applied to address delayed report exports. We are checking recovery and will update the status page as we confirm the results.”
This wording describes work under review. It should not be paired with a subject line saying “Everything is fixed.” Confirm what the change actually addressed and whether new and previously queued exports behave differently.
Resolved
“The report-export delay has been resolved. The status page explains the incident period and any remaining action for affected customers.”
Use this only after the incident owner approves the resolved state and the linked explanation exists. If some customers still need to retry or follow another action, make that step clear rather than implying there is nothing left to do.
Create the Migma design for quick reading
Give Migma the approved state statement, the reader's immediate question, and the single destination for current information. Ask for a restrained notice with readable text and clear hierarchy. Avoid celebratory artwork, promotional banners, and unrelated feature announcements that compete with the service information.
Migma's creation guide describes preparing email content for review. Inspect what it produces. A helpful rewrite can accidentally turn a limited impact statement into a universal claim or turn an estimate into a promise.
Keep important facts outside images. If a notice includes a timestamp, specify the relevant time context. Check the subject, preview text, headline, body, and button as one message: each should describe the same approved state.
Recheck the facts immediately before release
Name one person who can approve state wording and another who owns the final send. If one person holds both responsibilities, make both decisions explicit. The reviewer needs a current fact sheet, not only a screenshot of yesterday's draft.
If the state changes after approval, hold the pending message and review whether it is still useful. Do not silently patch just the first sentence while leaving the old subject or action behind. A queued investigating notice may need to be replaced by a different approved notice through the owner's controlled process.
Migma can provide reviewed HTML, while the Loops owner confirms the supported implementation and final variables. No native connection is assumed. Review the rendered destination message and verify the status link before the responsible owner releases it.
Test presentation without creating an incident send
Run Email Preflight and address relevant writing, link, layout, and inbox-preview findings. These checks do not verify incident truth or guarantee inbox placement. Use the sending team's established controlled test process, keeping real customer notifications separate from design review.
Inspect long service names, narrow screens, unavailable optional details, and the full status-page destination. A button should lead to information that supports the email's claim, not an unrelated homepage or an older incident.
Save the approved wording, observation time, reviewer, audience decision, and final message reference. When the incident closes, retain enough evidence to explain what customers were told at each stage. Prepare the creative in Migma, and let current operational facts determine the message that actually goes out.
Frequently Asked Questions
Is monitoring the same as resolved?
No. Monitoring describes checking recovery after an action. Use resolved wording only when the incident owner has approved that state and any remaining customer action is clear.
Should an incident email include a recovery estimate?
Include an estimate only when the responsible owner has approved it and the wording preserves its uncertainty. Do not invent a deadline to make a draft feel complete.
Can a preflight check confirm an outage is resolved?
No. Preflight helps review presentation, links, writing and related email risks. The incident owner must verify the operational facts and current state.
What if the incident changes after the email is approved?
Hold the pending message and review its subject, preview, body, action, audience and timing together. The owner should decide whether the notice remains useful or needs a different approved version.