ChatGPT for customer service: what to hand over, prompts and guardrails

ChatGPT for customer service: what to hand over, prompts and guardrails

ChatGPT for customer service works best on the jobs that happen before a reply goes out: drafting answers from your policy, summarizing long tickets, rewriting a tense message in a calmer tone and turning solved tickets into help articles. It should not send replies on its own or decide refunds and exceptions. Use it as a drafting tool for your agents, on a plan that keeps customer data out of model training, and have a person read every reply before it sends.

This guide covers what to hand over, which plan to use, a five-step setup, prompts you can copy, the rules on answering customers directly, and how to tell if it is working.

On this page

What ChatGPT can and can't do in customer service

The split is simple. ChatGPT handles language: reading, summarizing, drafting, translating and changing tone. People decide on money, exceptions, anything legal and anything where being wrong is expensive. The table shows where most support tasks land.

Task Give it to ChatGPT? Who signs off
Draft a reply from your policy text Yes Agent reads and edits before sending
Summarize a long ticket thread for a handover Yes Next agent checks it against the thread
Rewrite a blunt reply in a calmer tone Yes Agent
Translate a reply into the customer's language Yes, for common languages A fluent speaker for anything contractual
Turn solved tickets into a help article Yes Knowledge base owner
Tag tickets by topic and urgency Yes, in batches Team lead spot-checks a sample
Approve a refund, credit or policy exception No Agent or manager, under your rules
Reply to legal threats, safety issues or chargebacks No Named escalation owner
Quote an order status or delivery date Only from data you paste in Agent checks the order system

The last row matters most. ChatGPT cannot see your order system unless you connect it, so if you ask "where is order 4471?" it will either say it doesn't know or, worse, write something plausible. Paste the facts in and ask it to use only those.

Is it safe to paste customer data into ChatGPT?

It depends on the plan, and on what you paste. Pick the plan first, then strip the ticket.

OpenAI says it does not use business data from ChatGPT Business, ChatGPT Enterprise, ChatGPT Edu or the API to train its models by default, and that Business and Enterprise admins control how long conversations are kept (OpenAI enterprise privacy). On a personal Free, Plus or Pro account, the training setting sits under Settings, then Data controls, as "Improve the model for everyone". OpenAI's Data Controls FAQ says new conversations won't be used for training once it is off, and that Temporary Chats may be kept for up to 30 days for safety purposes.

Plan Used for training by default? Fit for a support team
Free, Plus, Pro (personal) Controlled by "Improve the model for everyone" Testing only, with the setting off and no customer details
ChatGPT Business No Yes, for most small and mid-size teams
ChatGPT Enterprise No Yes, with admin retention controls and audit logs
API (inside your help desk) No Yes, when a developer builds it into your tools

A business plan solves the training question. It does not make it fine to paste everything. Card numbers, passwords and ID numbers never need to be in a drafting chat, so take them out every time. The checklist below is the routine we suggest for every ticket.

Checklist: seven steps before pasting a support ticket into ChatGPT, from choosing a Business plan to escalating legal threats to a person

If your company doesn't have written rules for this yet, start with our free AI policy template and add a support section. The sample ChatGPT policy for employees has wording you can adapt.

How to use ChatGPT for customer service in five steps

Most teams start by pasting tickets into a blank chat and asking for a reply. The drafts come back generic, so people give up. The fix is to give ChatGPT the same briefing a new hire gets, once, and reuse it.

1. Make a Project for support

Create a ChatGPT Project called Support replies. Upload your refund policy, shipping policy, warranty terms, SLA and your ten most common macros. Every chat inside the Project can use them. Our guide to ChatGPT Projects, custom instructions and files walks through the settings.

2. Write the instructions once

In the Project instructions, say who it is writing for, the tone, the reply length and the hard rules. Copy this and change the brackets:

You draft customer support replies for [COMPANY], which sells [PRODUCT] to [CUSTOMERS].
Tone: warm, plain, no jargon. Reply length: under 120 words unless the customer asked several questions.
Use only the policies in this Project and the facts in the ticket. If something is missing, write [CHECK: what is missing] instead of guessing.
Never promise a refund, credit, delivery date or exception. Write [AGENT DECIDES] where one is needed.
Sign off as [AGENT]. Use US spelling.

If you want a fill-in version for personal accounts, the ChatGPT custom instructions template uses the same six blanks.

3. Give it your voice

Paste five replies your best agent wrote and ask ChatGPT to describe the tone in ten rules. Edit the rules, then add them to the instructions. This works better than adjectives like "friendly but professional", which every model reads the same way.

4. Set the escalation rules

List the cases that go to a person with no draft at all: legal threats, safety or injury, data deletion requests, chargebacks, press, and any customer on their third contact about the same issue. Tell ChatGPT to reply only "ESCALATE: [reason]" for these.

5. Review, then send

Every draft gets read by the agent who sends it. Check names, amounts, dates and anything that sounds like a promise. The placeholders from step 2 make the gaps easy to spot.

ChatGPT prompts for customer service

These work inside the Project from step 1. Paste the ticket after each one, with personal details replaced by placeholders.

Draft a reply

Draft a reply to this ticket. Answer every question the customer asked, in the order asked. Quote the policy line you relied on at the end, in brackets, so I can check it. Ticket:

Summarize a thread for a handover

Summarize this thread in five lines: what the customer wants, what we have already tried, what we promised and when, the customer's mood, and the next action. Thread:

Calm a tense reply

Rewrite my reply so it is calmer and shorter. Keep every fact and every commitment exactly as written. Acknowledge the problem once, then give the next step. My reply:

Say no without losing the customer

The customer asked for [REQUEST]. Our answer is no, because [REASON FROM POLICY]. Draft a reply that says no in the first two sentences, explains why in one, and offers [ALTERNATIVE] if it applies. Ticket:

Turn solved tickets into a help article

Here are [N] solved tickets on the same issue. Write a help article: a title phrased as the customer's question, the answer in the first two sentences, then numbered steps. Flag any step where the tickets disagree.

Tag a batch of tickets

Tag each ticket below with one topic from this list: [TOPICS]. Add urgency: high if the customer mentions a deadline, money taken twice, a safety issue or cancelling. Return a table: ticket ID, topic, urgency, one-line reason.

For more, our 100 customer support prompts cover triage, macros and de-escalation by ticket type.

Should ChatGPT answer customers directly?

Not without a review step, and not without telling people. Two reasons.

First, you own what your bot says. In Moffatt v. Air Canada, 2024 BCCRT 149, an airline's website chatbot told a customer he could apply for a bereavement fare within 90 days of buying his ticket. The airline's policy didn't allow that. Air Canada argued the chatbot was responsible for its own actions. The British Columbia Civil Resolution Tribunal called that "a remarkable submission", held the airline responsible for everything on its website, and ordered it to pay C$812.02 in damages, interest and fees.

Second, disclosure rules are arriving. Article 50 of the EU AI Act (Regulation (EU) 2024/1689) requires AI systems that talk directly with people to be designed so those people are informed they are dealing with an AI, unless that is obvious from the context. It applies from August 2, 2026. If you serve customers in the EU, check with your legal team how this applies to your chat widget. This is a summary of the rule, not legal advice.

The practical answer for most teams: let AI draft, let people send. If you do put a bot in front of customers, label it, limit it to questions your help center already answers, and give customers a one-click way to reach a person.

How to tell if ChatGPT for customer support is working

Track four numbers for a month before you start and a month after. Use your help desk reports, not gut feel.

  • Handle time per ticket. Should drop on routine tickets.
  • Edit rate. The share of drafts sent with light or no edits. Below half means your instructions or policies in the Project need work.
  • Reopen rate. If it rises, drafts are missing part of the question.
  • CSAT on AI-drafted replies vs the rest. Tag tickets where a draft was used so you can compare.

Worked example (illustrative numbers, not a benchmark). A team handles 1,200 tickets a month. Writing a reply from scratch takes 6 minutes. Editing a good ChatGPT draft takes 3. If every draft were usable, that saves 3 minutes × 1,200 = 3,600 minutes, or 60 hours a month. Say 15% of drafts are thrown away and rewritten. Those 180 tickets save nothing, so the real saving is 3 minutes × 1,020 = 3,060 minutes, or 51 hours. Run the same sum with your own handle times before you decide which plan to pay for.

If you'd rather not build the setup yourself, Custom AI for Your Job sets up an assistant around your support role, with your policies, tone and escalation rules already in place.

Questions about ChatGPT for customer service

Can ChatGPT replace customer service agents?

No. ChatGPT can draft replies, summarize tickets and translate, which cuts the time agents spend writing. It cannot check your order system unless connected, approve refunds or decide when a customer needs an exception. A tribunal held Air Canada liable for wrong advice its chatbot gave, so a person should still review what goes out.

Is it safe to put customer data into ChatGPT?

Use ChatGPT Business, Enterprise or the API, which OpenAI says are not used to train its models by default. On a personal account, switch off "Improve the model for everyone" in Data controls. Either way, remove card numbers, passwords, ID numbers and health details, and replace names and order numbers with placeholders before pasting.

Which ChatGPT plan should a support team use?

ChatGPT Business suits most small and mid-size teams: business data is not used for training by default and admins control retention. Enterprise adds audit logs and wider admin controls. If you want AI inside your help desk rather than in a separate chat, a developer can build it on the API.

Do I have to tell customers a reply was written with AI?

For a draft an agent reviews and sends, that is your call and your policy's. For a chatbot that talks to customers directly, Article 50 of the EU AI Act requires people to be informed they are dealing with an AI unless it is obvious. It applies from August 2, 2026. Check with your legal team for your markets.

How do I stop ChatGPT making up policies?

Upload the real policy documents to a Project, tell it to use only those and the ticket, and ask it to quote the policy line it relied on at the end of each draft. Tell it to write a placeholder such as [CHECK] when information is missing instead of guessing. Then have the agent check the quoted line before sending.

Laisser un commentaire :