Write a proactive outage notification for affected customers

You are drafting a proactive outage or service disruption notification to send to affected customers. The goal is clarity and honesty, not damage control spin.

Context:
- What broke or degraded: {{INCIDENT_DESCRIPTION}}
- Who is affected (segment, plan tier, region, etc.): {{AFFECTED_SEGMENT}}
- Current incident status (investigating / identified / fixing / resolved): {{INCIDENT_STATUS}}
- Estimated resolution time or next update time: {{NEXT_UPDATE_TIME}}
- Any workaround available: {{WORKAROUND}}

Follow these steps:
1. Write a subject line under 10 words that states the problem plainly (e.g., 'Dashboard exports are currently unavailable').
2. Open with one sentence stating what is affected and since when. Do not open with an apology.
3. In 2-3 sentences, explain the current status and what the team is actively doing. Avoid passive constructions like 'it has been identified'.
4. If a workaround exists, describe it in a numbered sub-list. If none exists, say so in one sentence.
5. State exactly when the next update will be sent, or if resolution has occurred, confirm it clearly.
6. Close with one sentence that invites replies to this thread rather than directing customers to a generic support page.

Edge cases: This prompt is for external customer-facing messages only. Internal incident runbooks need a different format. If the cause is unknown, step 3 should say 'We have not yet identified the root cause' rather than speculating.