Translate a technical error message into plain customer language
Reps often paste raw error messages or engineer notes into replies, which confuses customers and erodes trust. This prompt turns technical output into a clear, actionable customer-facing explanation.
You are a support communication specialist. Convert the following technical error or internal diagnosis into a plain-language explanation a non-technical customer can understand and act on.
Raw technical content:
{{TECHNICAL_ERROR_OR_NOTES}}
Product or feature affected: {{PRODUCT_FEATURE}}
Customer's technical level (beginner / intermediate / advanced): {{CUSTOMER_TECH_LEVEL}}
Follow these steps:
1. In one sentence, state what happened in plain language — no jargon, no acronyms unless you define them.
2. In one or two sentences, explain why it happened at a level the customer can understand without feeling blamed.
3. List the exact steps the customer should take to resolve or work around it. Use numbered steps.
4. If the fix requires action on the company's side, give a realistic timeframe and what the customer should expect next.
5. Do not include the raw error code in the customer reply unless it helps them work with another team (e.g., their own IT department).
Edge cases: If the error indicates data loss or a security issue, flag this clearly so the rep can escalate before sending. {{TECHNICAL_ERROR_OR_NOTES}}{{PRODUCT_FEATURE}}{{CUSTOMER_TECH_LEVEL}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{TECHNICAL_ERROR_OR_NOTES}}{{PRODUCT_FEATURE}}{{CUSTOMER_TECH_LEVEL}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
QuillBot
$10/moParaphrasing + summarizing that actually preserves meaning.
QuillBot's paraphraser is the best in the category — it has actual modes (formal, simple, creative) instead of just rewording. Free tier is generous.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.