ChatGPT prompts for customer service replies you still send yourself
The best ChatGPT prompts for customer service give the assistant the customer's message and the facts you have, ask for a short draft in plain words, and set hard limits: use only what you pasted, never promise a fix, a date or a credit, and leave sending to a person. Below are six prompts for the replies support agents write most, plus a check to run before you hit send.
These work in ChatGPT, Claude, Gemini, Copilot or whatever assistant your company has approved. Swap the [brackets] for your own details and paste the email or ticket after the prompt.
What rules should go above every customer service prompt?
Paste these once at the top of the chat, or in your assistant's custom instructions if it has them. They do most of the work.
Rules for every reply you draft for me: - Write drafts only. I read, edit and send them myself. - Use only the facts in what I paste. If something isn't there, tag it [CONFIRM] instead of guessing. - Never promise a fix, a date or a credit, and don't say anything is fixed or solved unless I tell you it is. - Use the customer's own words about the problem. - Keep it short and in plain words. No sales language.
1. How do you reply when a customer asks for an update?
Draft a short update email from me to [customer name] about [ticket or problem]. Use only the facts below. Include: what we know, what we're doing now, and when they'll hear from us next ([next update time]). Acknowledge the impact in their words if their email has them. Don't share internal names or theories about the cause. Never promise a fix, a date or a credit. Under 150 words. Facts: [paste the ticket notes] Their email: [paste it]
The next update time is the part customers remember. Give one and keep it. There are ready-made versions in the ticket update email templates.
2. What do you send when you can't answer yet?
Write a two-sentence holding reply to this email. Say when I'll get back to them properly: [day and time]. Don't promise anything else. Email: [paste it]
A holding reply buys you time honestly. It only works if you then reply by the time you gave.
3. How do you start a reply to an upset customer?
Draft a reply to this customer. Thank them for telling us, acknowledge the problem in their own words, and offer one next step: a short call, one question, or passing their feedback to the team. Don't argue with their account of what happened. Don't promise a fix, a date or a credit, and don't say anything is solved. Under 120 words. Their email and the ticket: [paste both]
Many people write the first sentence themselves and let the assistant draft the rest. For a fuller walkthrough, see how to respond to an angry customer email.
4. How do you answer a low survey score?
This customer gave us [score] out of [scale] after ticket [ticket ID]. Their comment: [paste it exactly, or "no comment"]. Draft a short reply from [account owner] that thanks them, acknowledges the problem in their words and offers one next step. If there's no comment, ask one simple question about what went wrong and offer a short call. Mention the ticket by subject so it doesn't read like a form letter. Under 80 words. Never promise a fix, a date or a credit.
More on who should reply and when in following up on low NPS and CSAT scores.
5. How do you ask a customer for missing details?
From this ticket, list what we still need from the customer to move the case forward. Then draft one short email that asks for all of it at once, as a numbered list, with the exact question for each item. Explain in one line why we need it. Don't guess at the cause. Ticket: [paste it]
Asking once, with a numbered list, beats three emails over three days. More case prompts are in AI prompts for support case work.
6. How do you check a draft before you send it?
Run this on any draft above, in the same chat, before anything goes to a customer.
Check the reply you just wrote. List anything that: - promises a fix, a date or a credit, or says something is fixed - doesn't use the customer's own words about the problem - mentions a ticket or detail that isn't in what I pasted - opens or closes the same way as your other drafts today Don't rewrite it. Just list the problems, or say "No problems found".
Why do AI replies sound like a bot, and how do you fix it?
- Every reply opens the same way. Customers notice. Ask for three different openings and pick one.
- It doesn't sound like you. Write one apology in your own words and paste it in as the example.
- It answers a nearby question. Make it quote the customer's actual ask before it drafts.
- It's too long. Set a word limit in every prompt. Short replies get read.
Only use an assistant your company approves for customer data. If you aren't sure, take names and contact details out of what you paste.
Questions
Can ChatGPT answer customer emails for me?
It can write the first draft. A person should read every reply, check the facts and send it. Nothing in these prompts asks the assistant to send anything.
Is it safe to paste customer emails into ChatGPT?
Only if your company approves that tool for customer data. If it doesn't, or you aren't sure, take names, emails and account details out first and check what's left.
How do I stop AI replies sounding like a bot?
Paste one reply you wrote yourself as the example, ask for three different openings and pick one, and make sure the draft uses the customer's own words about the problem.
Why do the prompts ban promising a fix or a date?
Because a promise in writing is hard to take back. If engineering hasn't committed to a date, the reply shouldn't either. Say when the customer will hear from you next instead.
Want the full routine?
Three plays in The CS Agent Playbook cover this kind of reply drafting: the Escalation Brief (with a follow-up prompt for the customer update), Morning Inbox Triage (first drafts and holding replies, never sent for you) and Customer Survey Follow-up (a reply draft for every low score, with a QA check on tone and promises).
The whole playbook has 15 agent routines and 54 ready-to-paste prompts for support case work and customer success, each with guardrails, a sample result and a QA check. $39 for the 47-page PDF and a plain-text prompts file.
Get the playbook Try the free sample play
All sales are final, so try the free play first.