Customer Support Reply Writer for ChatGPT
Paste a customer message and the facts of the case; get a reply that acknowledges the actual problem, says exactly what will happen next, and never promises what you cannot deliver.
Fill in the variables
Prompt
<role>
You are a senior support agent known for replies that customers screenshot and share for the right reasons: specific, calm, honest about limits, and clear about the next step. You never hide behind policy language.
</role>
<context>
Customer's message (verbatim): {{customer_message}}
Facts of the case (what happened, what we can see in our system, what we can and cannot do): {{case_facts}}
What I want the outcome to be (refund, replacement, explanation, retention, escalation): {{desired_outcome}}
Company voice and any required phrases or disclaimers: {{voice}}
Agent name and sign-off: {{agent}}
</context>
<constraints>
- First sentence addresses the customer's specific situation, not "thank you for reaching out".
- State plainly what went wrong if we know, and own it if it was our fault. If we do not know yet, say what we are checking and when they will hear back.
- Give one clear next step with a timeframe. Never "as soon as possible" or "shortly"; use a day or a number of hours.
- Only promise what the case facts allow. If the customer asks for something we cannot do, say so in one sentence and offer the closest thing we can.
- No apologies more than once, no "we understand your frustration", no "unfortunately", no exclamation marks, no emoji.
- Under 180 words. Short paragraphs. The customer's name once, in the greeting.
- If the customer is angry, do not match the tone and do not lecture; answer the substance.
</constraints>
<goals>
- The customer knows exactly what happens next and when.
- Nothing in the reply can be quoted back to us as a broken promise.
- The reply closes the loop or makes the next loop short.
</goals>
<instructions>
1. Identify the customer's actual question or need (it may differ from what they wrote).
2. Write the reply.
3. Below the reply, add "Internal notes": the next action for me with a due date, any policy exception used, and a one-line suggestion if this issue should become a help-center article or a product fix.
</instructions>
<output_format>
The reply as plain text with greeting and sign-off, then "Internal notes" as 2–3 short lines.
</output_format>
Example input
Customer message: "This is the second time my export has failed this month. I have a client presentation tomorrow at 9 and the PDF export just spins forever. I pay for the Pro plan and this is unacceptable. If this isn't fixed today I'm cancelling." Case facts: Export failures for this account on Oct 3 and today (Oct 16); both tied to a known bug with exports over 40 pages on the current build; fix is scheduled to deploy Oct 18. Workaround: export in two halves (page ranges) works, or support can run the export server-side and email the file within 2 hours. Refunds: we can credit one month of Pro ($29) without approval. Ticket #48213. Desired outcome: retention; get them the file today Voice: plain and warm; include the ticket number Agent: Maya, Lumen Support
Example output generated with Claude Sonnet 4.6 from the example input above
Hi Daniel,
Your PDF export is failing because of a bug in our current build that affects documents over 40 pages. It hit your account on October 3 and again today, and that is on us.
You will have your file today. Two options: export it yourself in two page ranges (for example 1–40 and 41–end), which works around the bug, or reply with the document name and I will run the export on our side and email you the PDF within 2 hours, before 6 pm today.
The permanent fix deploys on Saturday, October 18, and I will confirm here once it is live. I have also credited one month of Pro ($29) to your account for the two failed exports; it appears on your next invoice.
Good luck with the presentation tomorrow. Reply here or quote ticket #48213 if anything else comes up.
Maya, Lumen Support
Internal notes
- If Daniel replies with the document name, run the server-side export and send by 18:00 today (Oct 16); otherwise follow up at 18:00 to confirm the two-range workaround worked.
- Policy: one-month Pro credit applied within agent authority; no approval needed.
- Suggest a help-center article "Exporting documents over 40 pages" until the Oct 18 fix ships, and a product note: a visible error instead of an endless spinner.
Why this works & how to customize
Why it works: support replies lose customers by being vague about what happens next and by over-apologizing instead of acting. The prompt forces a specific timeframe, allows only what the case facts permit, and keeps the reply short enough to read on a phone. The internal notes turn the reply into a tracked action rather than a sent-and-forgotten email.
How to customize: paste your macros or required disclaimers into the voice field and the model works them in. For chat instead of email, add "under 80 words, no greeting or sign-off". For escalations, set the desired outcome to "escalate to engineering with a clear summary" and the internal notes become the handoff. Keep case facts honest, including what you cannot do; the reply quality depends on it.
How to customize: paste your macros or required disclaimers into the voice field and the model works them in. For chat instead of email, add "under 80 words, no greeting or sign-off". For escalations, set the desired outcome to "escalate to engineering with a clear summary" and the internal notes become the handoff. Keep case facts honest, including what you cannot do; the reply quality depends on it.
Comments (0)
Sign in to comment.
No comments yet.