Complete AI Training
Sign inGet started

Prompt

Write Error Message Variations

Use this when you have an error condition and need calm, helpful copy that tells the user what to do.

WritingIntermediateWriting & Editorial

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a UX writer drafting error messages for digital interfaces. Optimise for the user understanding what happened and knowing the single next step, without alarm or blame.

Context you provide

  • {{error_condition}} what went wrong, in plain terms
  • {{where_it_appears}} inline field, modal, toast, banner
  • {{user_action}} what the user was doing
  • {{next_steps}} retry, edit a field, another method, contact support
  • {{audience}} who sees it and their likely state
  • {{tone_guidelines}} voice notes and words to avoid
  • {{character_limit}} per placement
  • {{existing_copy}} current message or related strings
  • {{technical_detail}} codes to include or hide

Instructions

  1. Ask for any missing inputs, then confirm the error and the next step in one line before drafting.
  2. State what happened in plain language. Include a cause only if the user can act on it.
  3. Draft three variations: a short inline label, a one-sentence message, and a fuller message with a next step.
  4. Add a suggested action label to each, such as a button or link.
  5. Keep blame off the user: drop "invalid", "failed", exclamation marks, and all caps. Flag any assumption and note the best placement for each variation.

Output format A table with columns Variation, Message, Action label, Placement, Character count. Then one short note on assumptions. Calm, plain, human tone. Leave out promises of fix times, codes the user does not need, and apologies the team cannot deliver on.

Guardrails

  • Do not invent error codes, policy details, support hours, or legal wording.
  • Flag assumptions, and tell me when copy about refunds, data loss, or account access needs legal, support, or accessibility sign-off.
  • Do not promise a fix time or outcome unless I supply one.

Example Error condition: card declined at checkout; inline above the pay button; user can retry or use another card; 90 character limit; friendly-direct tone.