3 blanks to fill
Empathetic Support Reply
Reply to a customer's issue with empathy, a clear answer and practical next steps, without promising anything beyond what your policy allows.
- customer-support
- service
- operations
For support agents, team leads and help-centre writers who want answers that are kind, accurate and within policy. Every prompt has blanks in capitals, like [CUSTOMER ISSUE] and [TICKETS], for the parts that change. Fill them in on the prompt's page and copy the result, or save the prompt to your Save My Prompts library and fill it in from the extension right inside ChatGPT, Claude or Gemini.
3 blanks to fill
Reply to a customer's issue with empathy, a clear answer and practical next steps, without promising anything beyond what your policy allows.
4 blanks to fill
Sort a batch of support tickets by issue, urgency, customer impact and the team that should take them, flagging missing data and safety cases.
3 blanks to fill
Turn approved product documentation into a step-by-step help centre article with prerequisites, the expected result and troubleshooting tips.
4 blanks to fill
Group de-identified support tickets into the questions customers ask again and again, and draft FAQ answers grounded in your approved docs.
5 blanks to fill
Summarise a support case for escalation: the timeline, customer impact, what's been tried, the evidence and the decision needed from the next team.
4 blanks to fill
Explain a refund decision to one customer in plain words, saying what they get or don't, why, what happens next, with a respectful close.
3 blanks to fill
Turn a customer's description of a problem into a bug report engineers can reproduce: environment, steps, the expected and the actual result.
3 blanks to fill
Draft a status update during an outage with confirmed facts, the current action, the impact on customers and when the next update will come.
3 blanks to fill
Get calm reply options for an upset customer's message that acknowledge what went wrong for them and set respectful boundaries where needed.
4 blanks to fill
Create reusable reply macros for your most common support issues, with fields to edit and a note on when each macro shouldn't be used.
3 blanks to fill
Analyse de-identified customer feedback for themes, how often each comes up, representative examples and the improvements worth making.
5 blanks to fill
Rewrite product instructions for a first-time user with numbered steps, what they should see after each one and how to recover from mistakes.
4 blanks to fill
Design a quality scorecard for one support channel that rates accuracy, resolution, empathy, clarity and policy, showing what each score looks like.
3 blanks to fill
Build a troubleshooting flow for a technical issue that starts with low-risk checks and says clearly when to stop and escalate to a specialist.
3 blanks to fill
Compare recent support tickets with your help articles to find unanswered questions, outdated steps and documentation that's missing entirely.
5 blanks to fill
Hand an open support case to the next shift or tier 2 with what's been tried, where it stands, the next step and how the customer is feeling.
3 blanks to fill
Group customer feature requests by the need behind them and their impact, without treating the number of requests as proof of priority.
4 blanks to fill
Explain your support response targets to one customer accurately, saying what applies to their plan, whether it was met and what happens next.
3 blanks to fill
Help a customer with an accessibility issue by asking only what you need to know and offering documented workarounds or a clear escalation.
3 blanks to fill
Review a support conversation for accuracy, tone, policy, privacy and missed follow-ups, and get coaching notes you can share with the agent.