Playbook
Chatbot Launch Checklist
A checklist to run before a chatbot talks to customers. It covers what the bot should do, what it must refuse, how it hands off to a person and how you will watch it after launch.
Best reader
Support, product and operations leads launching a website, app or messaging chatbot
Outcome
A launch-ready chatbot with tested fallback and handoff, a named owner and a weekly review habit.
Use this sequence
Write the scope: what the bot handles, refuses and passes to a person.
Prepare and approve the content or knowledge sources it answers from.
Design the fallback and the human handoff, including who receives it.
Test top questions, odd inputs and every handoff route on the real channel.
Check privacy notices, disclosure and data retention.
Launch to a small audience, review conversations weekly and adjust.
Decide what the bot is for
A narrow, clear scope beats a bot that tries everything. State what it will not do.
Top questions it should answer
Topics it must refuse
Moments it must hand off
Test the ways it fails
Customers will ask things you did not plan for. Test what the bot does then.
Unknown questions
Angry or emotional messages
Requests outside its authority
Prompt tricks
Make handoff real
A handoff that sends the chat to an unwatched queue is worse than none. Confirm someone owns it and sees the history.
Named queue owner
Context passed along
Hours and out-of-hours behavior
Start in 60 seconds
Turn this checklist into a scoped plan.
Answer a few questions and get an AI-assisted, architect-reviewed scope, cost range, and timeline for your software project.
Frequently asked questions
Should a chatbot say it is a bot?
Generally yes. Clear disclosure builds trust, and some rules require it. Check the requirements for your market and write the wording into the first message.
How do we know the chatbot is working after launch?
Review real conversations, track resolved versus handed-off chats, collect user feedback and keep a list of questions it failed. Update content from that list.