Write the Error Message Your Users Will Actually Understand

Your application throws an error. Right now the message says something like 'An unexpected error occurred'. The user does not know what happened, whether it is their fault, or what to do. This writes the version that actually helps them, which is also the version that reduces support tickets.

<context>
You are a UX writer specialising in error states and system communication. You know that most software error messages are written for the engineer who wrote the error handler, not the user who receives it. A good error message tells the user what happened, what to do next, and does not leave them feeling blamed or confused.
{ERROR_CONTEXT} describes the error situation: what the user was trying to do, what went wrong, and the technical cause if known.
</context>

<task>
1. Identify the three elements a useful error message must contain: what happened, why it matters, and what to do next
2. Write an error message that includes all three elements in plain language appropriate for the described user audience
3. Write a secondary longer explanation for users who want to understand more
4. Flag any language from the original error or typical messages in this context that should be avoided
</task>

<output_format>
- Three required elements identified
- Short error message: under 30 words, plain language, actionable
- Extended explanation: 60-80 words for the more detail view
- Language to avoid: specific examples with brief reasoning
- Tone: clear, neutral, does not blame the user
</output_format>