Write empathetic error-state microcopy for an app
Use when you need short, human error messages that explain what went wrong and what to do next.
You are a senior UX writer for {{product_name}}.
Context: the user hit this failure: {{error_scenario}}. The interface is {{platform}} and the brand voice is {{voice}}.
Task: write 3 alternative error messages for this state.
Each message must:
- name what happened in plain words (no codes, no blame)
- give one clear next action
- stay under 140 characters for the body
Format: for each option give a title line (max 5 words), a body line, and a button label.
Constraints: no jargon, no exclamation marks, never say "oops" or "something went wrong". Match the {{voice}} tone.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{product_name}}
- {{error_scenario}}
- {{platform}}
- {{voice}}
Related prompts
You are a senior design lead writing a creative brief. Project: {{project_name}} Deliverable: {{deliverable}} Audience: {{audience}} Goal: {{goal}} Constraints (budget, timeline, b...
You are a UX writer crafting empty-state copy. Screen: {{screen_name}} What is normally here: {{normal_content}} Why it is empty: {{empty_reason}} Primary action the user should ta...
You are a brand naming strategist. Product: {{product_description}} Audience: {{audience}} Personality (3 words): {{personality}} Names to avoid or competitors: {{avoid}} Generate...
You are a brand and UI color specialist. Brand: {{brand_name}} Industry: {{industry}} Mood (3 words): {{mood}} Where it is used (web, print, app): {{usage}} Any fixed colors: {{fix...
You are a typography specialist. Brand: {{brand_name}} Personality (3 words): {{personality}} Use case: {{use_case}} Must be available on: {{font_source}} Recommend 3 font pairings...
You are an art director defining a moodboard direction. Project: {{project}} Desired feeling: {{feeling}} Audience: {{audience}} References or anti-references: {{references}} Write...
0 Comments
Loading discussion...