5 Questions Your Website Chatbot Should Answer From Day One
A new chatbot does not need to know everything. It needs to answer the handful of questions visitors ask every week, correctly, and know when to hand over. Here are five to cover before launch, and where each answer comes from in HolderChat.
One rule first: a chatbot can only answer what is written down somewhere it can read. If an answer exists only in someone’s head, write it on a page or in a document before you expect the bot to know it.
1. “How can I reach you, and when are you available?”
This is the simplest question and the most embarrassing one to get wrong. Put your company name, email, phone, and address in the Company Information tab; the bot can use these details in answers and handoffs, and updates apply without a rebuild. If you are not reachable around the clock, set the optional Working Hours / Timezone in Bot Behavior & Messages.
Check that older contact details are not still sitting in a knowledge source. The documentation lists outdated company fields or conflicting knowledge as the cause of a wrong contact email in answers. See Company Information.
2. “What are your delivery, return, or cancellation terms?”
Policy questions need exact answers, not a friendly guess. Add the page that contains your terms as a website source, or upload the policy as a file (PDF, DOCX, TXT, MD, XLSX, and PPTX are supported), then click Rebuild Bot. In your Bot Instructions, tell the bot to answer only from the provided knowledge and to say so when something is not covered.
When you test, ask the question in two or three different ways and compare the answers with the published text. The testing checklist in the documentation explicitly includes “no hallucinated pricing or policies”. See Testing Your Chatbot.
3. “How do I … with your product?”
How-to questions are where a chatbot saves the most back-and-forth, because the answers usually already exist in manuals, help articles, or FAQ pages. Add them under Knowledge Sources. On WordPress, the HolderChat Connector syncs the pages and posts you select, so updated help articles reach the bot after the sync and rebuild.
Keep each help page about one topic. That makes it easier for you to check an answer against its source when you test.
4. “Where can I find …?”
Many visitors simply cannot find a page: the price list, the download, the booking form. When you add your website as a source, HolderChat shows a menu preview of the pages it discovered before parsing, which is a good moment to check that the important pages are included. After parsing, the Website Info view shows how many pages were parsed and any crawl errors.
If a page is missing from the preview, it is often missing from your navigation too, which is worth fixing for human visitors as well.
5. “Can I talk to a person?”
Every support chatbot gets this question, and the answer should never be a dead end. In the Support tab you can add a Telegram group or a Microsoft Teams channel as second-line support. When the bot cannot answer from its knowledge base, it can route the request there. With Telegram, your team replies in the group and the answer appears in the visitor’s chat in real time.
Two things make this work: a valid channel setup on your side (for Telegram, the bot must be an admin in the group), and Bot Instructions that tell the bot to offer the handoff. Test it once from Test Chatbot before launch. See Support Channels.
After launch: let real questions guide you
The five questions above are a starting point. Your visitors will show you the rest. Open the Conversation History tab once a week, look through recent chats (you can search by date or message text) for questions the bot could not answer, and add the missing page or document. Then rebuild and ask the same question again in Test Chatbot. See Conversation History.
- Contact details and working hours are set.
- Policies come from the published text, not from the prompt.
- Help content is added as knowledge sources.
- Important pages appear in the website preview.
- A human handoff is connected and tested.
Build your chatbot
Create a bot from your website or documents, then embed it with one script tag or the WordPress plugin. The setup for support use is described step by step in Customer Support Chatbot for Your Website. The broader setup is in AI Chatbot for Your Website, and other walkthroughs are listed in HolderChat Guides. This article is part of the HolderChat blog.