Find out where my customer service chatbot fails and fix it
An analysis of your chatbot's conversations and metrics, with the gaps, root causes, and prioritized fixes to resolve more questions.
The prompt
Analyze my customer service chatbot's performance and tell me how to improve it.
What the bot handles: [products/services, industry, channels]
Metrics I have: [e.g. containment rate, handoff rate, CSAT, conversion, fallback/"didn't understand" rate, drop-off points]
Conversation samples: [paste 20-50 transcripts, ideally including failures and handoffs]
User groups: [e.g. new vs. returning customers, mobile vs. desktop, regions]
What the bot can access: [FAQ, help center, order system, account data, none]
Goal: [e.g. resolve more without a human, increase sales, cut wrong answers]
Analyze:
1. Failure patterns: group failed conversations by cause: missing knowledge, misunderstood intent, no access to needed data, policy limits, bad flow design, or wrong answer. Count each and quote one example.
2. Accuracy risk: answers that were wrong, outdated, or made up, and where they came from.
3. User groups: how different groups use the bot and where each struggles.
4. Handoffs: whether people reach a human at the right moment, with context passed along.
5. Metrics: what the numbers suggest, and which metric I'm missing.
Return:
- A table of issues: issue, frequency, impact, fix (content, flow, data integration, or handoff rule), effort (low/med/high).
- The top 5 fixes in priority order.
- Rewritten responses for the 3 worst examples.
- A test set of 10 questions to rerun after the changes.
Only use numbers from my data; label anything estimated.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- products/services, industry, channels
- e.g. new vs. returning customers, mobile vs. desktop, regions
- FAQ, help center, order system, account data, none
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Handle a warranty callback and decide what is coveredA fair way to assess a customer's warranty claim, decide responsibility, and reply clearly, whether the fix is covered or not.
- Explain a financial aid offer to a student and familyBreaks down a college aid offer into net cost, grants vs. loans, and next steps, with a clear reply to the family.
- Respond to a negative online review without breaching client confidentialityA short public reply to a bad Google or Avvo review that protects client confidences, plus guidance on whether to reply at all.
- Set up a simple log to track customer feedback and bug reportsA ready-to-use spreadsheet structure, tagging scheme, and weekly review routine for teams without a ticketing system.