All packs

Kit · 36 pages · 13 prompts + house style

Keep your support bot honest

Your bot is live and nobody checks what it tells customers. This is the weekly review that finds the wrong answers nobody complained about.

After using this: You'll have a weekly routine that catches the answers your bot got wrong quietly, the ones no dashboard flags because nobody complained.

Who this is for

You've ended up looking after a support bot and you're expected to make it good. Nobody has told you how to check whether it's working.

Not for you if

Your bot isn't live yet. Start with Get your support bot ready, which is about what to fix before you switch it on.

$149

One-time purchase · HTML and PDF

License

Instant delivery after payment.

Also in a bundleSave $138Launch a support bot

How it works

Each week, prompt 2 builds a sample of real conversations, including the ones that looked fine, and prompt 3 checks them against your docs. You sort each failure by cause, then decide whether it's a docs fix, a bot fix or a topic to take out of scope. A monthly test run and a one-page quality report show whether it's getting better.

What's inside

  1. 01What "working" actually means, and why deflection lies
  2. 02Which conversations to read each week
  3. 03How to check the answers that looked fine
  4. 04A weekly, monthly and quarterly routine
  5. 05Docs fix, bot fix, or take the topic out of scope
  6. 06Designing the handoff to a human
  7. 07What to do when it gets something badly wrong
  8. 08Reporting it upward
  9. 0913 prompts, from stripping customer details out of transcripts to making the case for more docs time
  10. 10Give your AI your house style
  11. 11The short version

See the pages

3 pages from the PDF you download, as they are. Select one for a closer look.

Preview a prompt from the pack

The full prompt, exactly as it appears in the pack. Nothing removed.

You are an experienced support operations lead. Help me decide what kind of fix this failure needs. The failure: [paste the conversation and what went wrong, customer details removed] What we have published on this topic: [paste, or say "nothing"] What I can change: [documentation / the bot's instructions / which topics it covers / all of these] How long a docs change takes to reach the bot: [e.g. straight away, hourly sync, daily sync, weekly, re-upload by hand] Recommend one primary action, and say why the others are wrong here: - Fix the documentation: which article, and what specifically. - Write new documentation: what's missing, and roughly how much. - Change the bot's instructions: what to change, and what it might break. Instructions are for how it answers, never the only home for a fact customers need. That goes in a public article. - Take this topic out of the bot's scope temporarily: for how long, what has to be true before it goes back, and the short article that tells customers how to reach a person meanwhile. - Escalate to product: because no documentation can fix it. Then give me the interim measure, if any, for the gap between now and the fix landing. Take the delay into account: if a docs change takes a week to reach the bot, say what protects customers in the meantime. Don't invent any fact I didn't give you. Where you'd need one, write [TODO: confirm]. At the end, list only the facts you needed and didn't have, not style choices, things to double-check, or anything I already gave you.

The thinking behind it

Want the thinking behind this kit? The course Keeping it true covers it in short parts, with an exercise in each.

Questions

Keep your support bot honest, $149

Instant delivery after payment.