How to Test a Website Chatbot Before It Goes Live
Create test conversations based on real enquiries and agree what a good answer or handover looks like. Include cases with a missing detail, an unsupported request and a visitor who asks for a person.
Cover predictable questions and boundary cases
Start with opening hours, service areas and how quotes work. Then try an ambiguous suburb name or ask for a guaranteed date. The chatbot should ask for clarification or explain how the date is confirmed.
Follow the enquiry beyond chat
Submit a labelled test, check which inbox or CRM record receives it and see whether the transcript and contact details are usable. Repeat on a phone and check the chat can be closed easily.
See the guide to deciding whether your website needs a chatbot to assess where chat would be useful. For more support, see Gecko Gully’s AI chatbot guides.
What you can do today
Ask the chatbot for a person and check what the receiving team can see.
Frequently asked questions
Should I test after an update?
Retest important answers and the handover when you change business information, instructions or integrations.
What answers should trigger a handover?
Send enquiries that need judgement or information the chatbot cannot verify to the appropriate contact route.
