Brand
Wispr Flow
Subject line
Brief disruption earlier today
Use case
Transactional EmailsAbout this email
This incident apology notifies users about a temporary backend outage that affected authentication, confirms the issue is resolved, and points readers to the support page for updates. The tone is plain, humble, and direct — no marketing flourishes, just a short status update signed by 'The team at Wispr Flow.'
Wispr Flow journey
Why this works
**Why this works.** The subject line names the problem (disruption) and timing (earlier today) instead of burying it behind a vague "service update" label, so users instantly know whether the email affects them and can decide whether to read further. The pattern here is "name the problem, not the solution"; you can lift it for any incident or apology email where clarity about what broke matters more than reassurance about what you fixed.