All packs

Kit · 45 pages · 14 prompts + house style

Get your support bot ready

Find what your bot will get wrong before you switch it on. Audit, fix, set the tool on purpose, then prove it.

After using this: You'll know what your bot would have gotten wrong, you'll have fixed it, you'll have set the tool on purpose, and you'll have a set of test questions you can rerun any time to prove it.

Who this is for

You're about to switch on your support bot (the AI assistant on your own site), or you already did and it isn't going well. You want to know what it'll get wrong before your customers find out.

Not for you if

Your bot is live and behaving, and what you really need is a routine for checking it every week. That's Keep your support bot honest.

$149

One-time purchase · HTML and PDF

License

Instant delivery after payment.

Also in a bundleSave $138Launch a support bot

How it works

Start with the readiness audit on the questions customers actually ask. Fix what it finds in the right order, write down what your bot must never answer, and set the tool on purpose. Then build 30 to 50 test questions with known answers, score the bot against them, and check the 10-point launch gate before you switch it on.

What's inside

  1. 01How your support bot actually works
  2. 02The 7 ways it goes wrong, and the fix for each
  3. 03The readiness audit
  4. 04Fixing things in the right order
  5. 05What your bot must never answer
  6. 06Testing it before you trust it
  7. 07What should you set in the tool itself?
  8. 08Are you ready to switch it on? The 10-point launch gate
  9. 09What happens after launch day?
  10. 1014 prompts, from ranking your top questions to deciding what it answers on day one
  11. 11Give your AI your house style
  12. 12The 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 expert help-center writer. This article explains what customers can do. I need it to also mark the edges, because an AI answering from it will otherwise invent capabilities we do not have. Article: [paste the article] What this feature cannot do: [paste everything you know: unsupported cases, limits, things people ask for that do not exist, known gaps] Questions customers ask that we cannot say yes to: [paste any you know] Do this: 1. Write a short, plain "what this doesn't do" section, as a list. State each limit as a fact, without apology and without hinting it might change. 2. Add any hard numbers, quotas or time limits, exactly as I gave them. 3. Where a customer commonly wants something we don't support, say so plainly, and give the nearest thing that does work if there is one. 4. Show me where in the article each piece should go. Rules: use only the limits I gave you. Do not invent a limit, a number, or a workaround. Don't invent any fact I didn't give you. Where you'd need one, including a limit you think probably exists, 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 How a help center actually works covers it in short parts, with an exercise in each.

Questions

Get your support bot ready, $149

Instant delivery after payment.