Customer Service Reply Prompt for ChatGPT

Use this customer service reply prompt for ChatGPT when you need to answer a support message clearly without letting AI decide policy, expose customer details, or promise a fix you cannot give. The goal is to turn a messy support message into a clear reply that stays inside your real options and shows when a human should take over.

Best use cases

Replying to angry customers without sounding defensive.
Explaining refunds, delays, replacements, or missing information.
Classifying support tickets by request type, policy fit, urgency, and handoff need.
Making short support replies warmer and clearer.
Keeping simple requests from becoming long AI-sounding replies.
Turning a long complaint into the main issue and next step.
Checking whether your draft sounds robotic, cold, or like a generic template.

What to prepare

Before using ChatGPT, collect the customer's message, order or case status, support channel, ticket type, urgency, company policy, trusted FAQ or help-doc answer, and the action you can actually offer. Replace names, emails, phone numbers, addresses, order IDs, and account details with placeholders before pasting anything into an AI tool.

If the customer is quoting wrong AI information about your services, prices, hours, or policies, first audit the claim against your source-of-truth facts with the business information check, then write the support reply.

Copy this prompt

Write a customer service reply that is calm, useful, and policy-safe. Customer message: [paste message after removing names, emails, phone numbers, addresses, order IDs, and account details] Customer's exact question or request: [refund, replacement, delivery update, password help, cancellation, bug status, missing information, complaint, or "not clear"] Ticket type and urgency: [billing, shipping, account access, bug, how-to question, complaint, refund, cancellation, safety, legal, or unknown; low, normal, urgent, or unknown] Situation: [summarize order status, product, service, shipping, billing, bug, or delay] What we can offer: [refund, replacement, workaround, troubleshooting step, wait time, escalation, or "not sure yet"] Policy limits: [what we can and cannot promise] Trusted source: [FAQ, help-doc paragraph, order status, internal policy note, or "no trusted source yet"] Source conflicts or gaps: [old help article, unclear refund rule, missing order status, customer asks for a person, repeated failed bot answer, or "none known"] Customer emotion: [angry, confused, disappointed, worried, urgent, or unknown] Brand voice: [plain, warm, direct, formal, casual, etc.] Channel and expected length: [email, chat, help desk note, social DM, short answer, full reply, or "match the customer's length"] Tone: Calm, helpful, concise, and human. Answer the customer's exact request first, then explain only what is needed. Do not sound defensive or like a generic AI template. Rules: - Do not invent policy, timelines, refunds, discounts, legal claims, or technical facts. - Use only the trusted source and situation details I provided. - If key information is missing, ask for it instead of guessing. - If no trusted source supports the answer, say what must be checked or hand it to a person. - If the trusted source conflicts with the order status, customer history, or another policy note, do not write a final answer. Mark the conflict and prepare a handoff summary. - If the customer asks for a person, says the bot already failed, or the same answer has not solved the problem, stop trying to resolve it with another long AI reply. - If the case needs judgment, security review, legal review, medical advice, billing authority, account access, safety review, or a policy exception, mark it for human handoff. - If this is a routine FAQ answer, say why it is safe to answer from the trusted source. - Keep private details out of the reply. - Match the channel and keep simple requests short. - Give one clear next step. Return: 1. Safe to answer now: yes, no, or needs review 2. A one-sentence direct answer to the customer's exact request 3. A short reply under 120 words, only if it is safe to answer 4. A warmer version 5. A firmer version 6. Source used for the answer 7. Source conflict or missing fact to verify 8. Ticket classification: routine FAQ, policy-limited, sensitive, urgent, or needs investigation 9. Whether a human handoff is needed and why 10. If handoff is needed, a short handoff summary for the person taking over: customer issue, source checked, what was already offered, missing facts, conflict to resolve, and recommended next action 11. A one-sentence internal summary of the issue 12. Any sentence that could sound defensive, robotic, too long, or too vague

Test input

Customer message: I paid for express shipping and the order is still not here. This is ridiculous. I want my money back. Customer's exact question or request: refund request Ticket type and urgency: shipping/refund, urgent Situation: Order shipped late because of a warehouse delay. Tracking now shows delivery tomorrow. What we can offer: Refund express shipping fee, send tracking link, and escalate if it is not delivered tomorrow. Policy limits: We cannot refund the full order unless the package is lost or returned. Trusted source: Shipping policy says express shipping fees can be refunded when the carrier misses the promised window. Full order refunds require a lost package, return, or manager approval. Customer emotion: angry and urgent Brand voice: plain, warm, direct Channel and expected length: email, short answer

What good output should include

A short acknowledgment that repeats the customer's real issue in plain words.
A direct answer to the customer's question before any explanation.
Only the remedy, refund, timeline, or escalation path you can actually offer.
One next step the customer can understand immediately.
A clear note about what source the answer used, such as the FAQ, help doc, order status, or policy.
A clear warning when the source conflicts with another fact or does not support a final answer.
A ticket classification that separates routine questions from sensitive, urgent, or policy-limited cases.
A human handoff note when the issue is complex, sensitive, or outside the written policy.
A short internal handoff summary so the next person does not make the customer repeat the whole story.
No blame, no long excuse, no fake empathy, and no over-apology.
No private customer details copied back into the reply.

Use it as a reply checker

For angry customers, write a rough reply first, then ask ChatGPT to check tone before you send it. This is useful when you are frustrated, rushed, or trying to be firm about a refund policy.

Act as a customer reading this support reply. Customer's likely emotion: [angry, confused, disappointed, worried, urgent, or unknown] My draft reply: [paste draft] Check: 1. Does the reply answer the customer's exact question first? 2. Does the reply clearly acknowledge the customer's issue? 3. Does anything sound defensive, robotic, dismissive, too long, or like a template? 4. Does it promise anything not stated in the policy? 5. Is there one clear next step? 6. Does the reply ignore a source conflict, missing fact, or direct request for a person? 7. Should this stay with AI drafting, use a saved FAQ answer, or go to a person? 8. Rewrite only the parts that need fixing.

Repair prompt

The reply still sounds wrong. Rewrite it again with these rules: - Keep the same facts, policy limits, and next step. - Start with the direct answer, then acknowledge the customer's problem. - Remove corporate filler and over-apology. - Use shorter sentences. - If we cannot solve it yet, say what we will check next and when we will follow up. - Match the support channel and do not make a simple answer longer than needed. - Do not add any new promise, refund, discount, or timeline.

When to stop and escalate

Do not use a prompt as the final authority for legal threats, chargebacks, medical or safety issues, harassment, account security, or anything involving regulated personal data. Use ChatGPT to organize the facts, then send the case to the right person.

Use AI freely for repetitive questions when the answer is already in your FAQ, order status, or written policy. Keep a person in the loop when the customer is angry, the facts conflict, the answer affects money or access, the customer asks for a person, or the reply would require an exception.

Common mistake

Do not ask ChatGPT to decide the policy. Give it the policy, available options, missing facts, exact customer request, and channel, then ask it to write or check the message. A simple customer question should not become a long AI support script.

Specific customer service prompts

Find repeated ticket problems

If you have several similar tickets, use ChatGPT to find patterns before rewriting the same answer again. Remove private details first, then ask for common issue types, missing FAQ answers, and where a person should step in.

Analyze these support tickets for repeat problems. Do not write customer replies yet. Ticket samples: [paste 5 to 20 anonymized ticket summaries] Trusted sources: [FAQ links, help-doc excerpts, policy notes, or "not available"] Return: 1. Common ticket categories 2. Questions that can be answered from the trusted source 3. Questions that need a better FAQ or help-doc answer 4. Tickets that need human review and why 5. Missing facts agents should collect before replying 6. One short draft macro or saved reply for each safe routine category 7. Risks: privacy, refunds, account access, legal, safety, or policy exceptions Rules: - Do not invent answers for tickets that lack a trusted source. - Do not include private customer details in the macros. - Mark anything unclear as "needs review."