Customer Support Email Reply Generator

Write clear, empathetic support replies that follow a supplied company policy. This practical writing workflow asks for relevant evidence, spells out how to use it, and produces a reviewable output instead of generic suggestions or invented details.

GPT / Claude / Gemini6 variables
Prompt
You are a specialist assisting with customer support email reply generator. Produce a practical, evidence-led result from the inputs below.

CUSTOMER MESSAGE: {CUSTOMER_MESSAGE}
VERIFIED ORDER OR CASE FACTS: {VERIFIED_ORDER_OR_CASE_FACTS}
COMPANY POLICY: {COMPANY_POLICY}
AVAILABLE RESOLUTIONS: {AVAILABLE_RESOLUTIONS}
ESCALATION RULES: {ESCALATION_RULES}
BRAND TONE: {BRAND_TONE}

Task workflow:
1. Identify the exact customer request.
2. Acknowledge the issue without admitting unverified facts.
3. State feasible next steps and timeframes only when confirmed.
4. Distinguish eligible remedies from cases needing human review..

Accuracy and safety rules:
- Only use facts present in my inputs or explicitly identified as checked references; distinguish facts from assumptions.
- If a required item is missing, mark it unknown and explain the minimum verification needed. Do not fabricate examples as if they were real.
- Never invent refunds, delivery dates, account actions, policy exceptions, or case outcomes.
- Explain important tradeoffs and any limitation caused by my stated format, platform, or audience.
- Avoid padding, repetitive claims, fake metrics, and promises of guaranteed ranking, performance, admission, or success.
- Clearly label ready-to-use material versus suggestions that still need verification.

Deliverables:
1. A send-ready reply
2. A shorter variant
3. And internal case notes for follow-up.
5. Brief final checklist showing how I can verify the result against the provided inputs.

Before finalizing, check the work for contradictions, unsupported facts, and any missing edge cases. Prefer specific, useful instructions over generic advice.
Quick brief
Purpose

Write clear, empathetic support replies that follow a supplied company policy.

Expected output

The response should contain a send-ready reply, a shorter variant, and internal case notes for follow-up. The output should be formatted so it can be copied, checked, and used without guessing what was assumed.

Customize before copying

Replace these placeholders with your own context before you run the prompt.

{CUSTOMER_MESSAGE}{VERIFIED_ORDER_OR_CASE_FACTS}{COMPANY_POLICY}{AVAILABLE_RESOLUTIONS}{ESCALATION_RULES}{BRAND_TONE}
Works well with
GPT
Claude
Gemini
Variations
Make the response shorter while keeping all required evidence and verification steps for Customer Support Email Reply.
Produce a beginner-friendly version that defines specialized terms and includes a concrete example for Customer Support Email Reply.
Use a professional, implementation-ready format with explicit edge cases, constraints, and acceptance criteria for Customer Support Email Reply.
What this prompt helps you do
Write clear, empathetic support replies that follow a supplied company policy. This practical writing workflow asks for relevant evidence, spells out how to use it, and produces a reviewable output instead of generic suggestions or invented details.
When to use it
Use this template when your immediate task is write clear, empathetic support replies that follow a supplied company policy. It is most useful when you can provide the requested input fields and review the result against real examples.
How it works
The workflow anchors its reasoning in the supplied material, organizes the user's goal, and executes this task-specific process: Identify the exact customer request; acknowledge the issue without admitting unverified facts; state feasible next steps and timeframes only when confirmed; distinguish eligible remedies from cases needing human review.
Best practices
Provide the actual policy and permitted remedies; redact sensitive customer information. Replace every input placeholder with genuine context, including examples of the expected result. Review the first draft against your own constraints before reusing it.
Common mistakes
Skipping key inputs, accepting unsupported claims, and publishing or executing generated output without review are frequent failure modes. In this task especially: Never invent refunds, delivery dates, account actions, policy exceptions, or case outcomes.
What you should expect back
The response should contain a send-ready reply, a shorter variant, and internal case notes for follow-up. The output should be formatted so it can be copied, checked, and used without guessing what was assumed.
Limitations
Never invent refunds, delivery dates, account actions, policy exceptions, or case outcomes. This is an assisted drafting and analysis template: it cannot independently validate inaccessible files, live platform data, or unprovided sources.
Model notes
Works with GPT, Claude, and Gemini. Provide the stated inputs as text, with redacted private information where appropriate.
Real-world applications
Suitable for people using AI to write clear, empathetic support replies that follow a supplied company policy in routine copywriting workflows, with manual verification before reuse.
How to tell if it worked
The reply is respectful, accurate, and leaves the customer with a clear next step. A second reviewer should be able to trace assertions to supplied inputs, and the final artifact should pass the verification checklist.
Where to go next
Explore related prompts in the copywriting category when you need adjacent tasks, reviews, or follow-up work.