A launch checklist for your website chatbot

Most chatbot problems that customers notice could have been caught in an hour of checking before launch. Print this list, work through it with the person who knows your business best, and tick each line. It ends with a ten-question test script to run against your own assistant.

Knowledge and prices

• ☐ Every service you offer is listed, and nothing you have stopped offering.
• ☐ Each price is exact, a range with what it depends on, or "quote required".
• ☐ Services with variable prices say "do not estimate a price".
• ☐ Policies (cancellation, deposits, refunds) match what your staff really do.
• ☐ There is a "do not answer" list.
• ☐ Old promotions and expired offers are removed.

Hours, time zone and holidays

• ☐ The time zone in your settings is your business's, not your web developer's.
• ☐ Weekly opening hours are correct, including lunch breaks if you close.
• ☐ Upcoming holiday closures are in the knowledge.
• ☐ Someone is responsible for updating seasonal hours.

Languages tested

• ☐ Each configured language was tested by someone who speaks it.
• ☐ Prices, dates and times came out right in each language.
• ☐ Your team knows what to do with an inquiry written in a language they don't read.

Escalation and emergency messages

• ☐ The knowledge says when to offer a person or the inquiry form.
• ☐ Urgent situations have exact wording, such as "call 911" for emergencies.
• ☐ On Premium: live chat takeover is switched on, and team members know where waiting chats appear.

Notification e-mails received

• ☐ You submitted a test inquiry and the notification arrived at the right address.
• ☐ The visitor confirmation e-mail arrived too, and not in spam.
• ☐ The inquiry appears in the inbox and you can change its status.
• ☐ Someone is named to answer new inquiries, with a target response time.

Privacy text

• ☐ The greeting says it is an AI assistant.
• ☐ The knowledge tells it never to ask for card numbers, ID numbers, passwords or health details.
• ☐ Your privacy policy mentions the chat. See chatbot privacy basics.

Installation checked on every page template

• ☐ The chat appears on the homepage, a service page, a blog post and the contact page; sites often use different templates for each.
• ☐ It appears on a phone, and it doesn't cover your own buttons or cookie banner.
• ☐ The installation check in your cabinet finds the code on your site.
• ☐ If your site uses a consent manager or tag manager, the chat still loads.

Test script: 10 questions to ask your own assistant

Ask these on your live site from a phone, in a private browser window. Write down each answer and mark it right, wrong or incomplete.

1. What are your hours this Saturday?
2. How much does (your most popular service) cost?
3. How much does (a service you quote individually) cost? It should not invent a price.
4. Do you serve (a town just outside your area)?
5. Do you offer (something you don't do)? It should say no politely.
6. Can I cancel or reschedule, and is there a fee?
7. A question in each of your other configured languages.
8. A question that needs advice it must not give, such as a diagnosis or legal opinion.
9. "I'd like someone to call me." Check that it offers the inquiry form and asks for consent.
10. From a specific service page: "How much is this?" It should use the page you are on.

Fix the knowledge for every wrong or incomplete answer, then run the script again. When all ten are right, you are ready. After launch, keep the assistant healthy with the operating practices.

Frequently asked questions

Who should run the test script?

The person who knows your services and prices best, ideally with someone who speaks each configured language.

Should I test on the live site or in the wizard?

Both. The wizard's test chat is for early checks; the live site shows installation and page-aware answers.

What if an answer is wrong after launch?

Fix the knowledge, or request a correction from your cabinet. The Allinaa team reviews and applies it.