To build a website chatbot from existing content, start with the questions your customers already ask, connect the pages that answer them, review the extracted knowledge, and test it before installing the chat widget. Your website gives you a starting point; the review determines whether it is ready to answer visitors.
This guide takes a small business through that process using RobiFox. You will finish with a source list, a practical test set, and a launch checklist. A chatbot that reads your website can explain your published policies. Reading those pages alone does not give it access to a customer’s order, payment, or account.
Make the owner decisions before you start
You can prepare the first version without a development project, but someone must own its content and limits. Decide whether its primary job is support, sales or documentation; RobiFox asks for that role when you create a project. Record the source owner, the person receiving questions that need human help and the visitor languages you can check.
Before launch, confirm that the chosen sources are current, someone has resolved conflicts, your test includes questions the assistant should decline, and the contact route works. These are business decisions rather than a promise that no-code setup makes answers automatically accurate.
1. Choose the questions your first version should answer
Pick a manageable group of recurring questions from your support inbox or sales conversations. For an online shop, a useful starting scope might be delivery regions, standard delivery estimates, product care, and the return process. For a service business, it might be service areas, what a package includes, and how to request a booking.
Write each question in the customer’s wording, then put the page containing the answer beside it. If you cannot find a current answer, mark it as a content gap. Do not expect the assistant to fill that gap from general knowledge.
- Suitable for website knowledge: “Do you deliver to Ireland?” when your current delivery page states the supported countries.
- Needs an additional system or a person: “Where is order 1234?” The delivery policy does not contain that customer’s tracking record.
- Needs a decision: “Can you make an exception for me?” A standard policy does not authorise a special arrangement.
Keep the first launch focused enough that someone on your team can check every important answer. You can expand coverage when the initial questions work reliably.
2. Prepare the pages and documents behind those answers
Use current product pages, help articles, pricing information, and approved policies. Check for expired offers, old PDFs, and copied FAQ sections that disagree with the main policy. Correct the source where possible, so both visitors and the assistant receive the same information.
RobiFox accepts a website address and supports PDF, Word, Excel, and plain text documents. Create your assistant, enter the website address, and follow the reading progress. You can add supported documents when an answer is not on the website. The RobiFox setup overview explains how the material becomes searchable knowledge.
Choose documents specifically for customer-facing use. A whole internal workbook may include supplier costs or staff notes that have no place in a public assistant. Prepare a suitable version before uploading it.
If reading finishes without usable knowledge, check whether the intended pages are publicly accessible and contain readable text. RobiFox’s setup flow flags cases where no searchable knowledge was produced, including inaccessible sites or content loaded through JavaScript. Resolve that problem before testing answers.
3. Review what the assistant learned
Read the extracted knowledge as if a customer were about to rely on it. Verify prices, units, product variants, delivery regions, and exceptions. A correct sentence from the wrong product page can still produce a wrong answer.
Example using a fictional shop: a delivery page says “Dispatch within two working days,” while an old FAQ says “Delivery within two days.” These statements make different promises. Ask the policy owner which statement is current, correct the outdated page, and ensure the approved knowledge distinguishes dispatch from arrival.
RobiFox provides a review workflow for contradictions and duplicates. Your team decides which information should be used. For a repeatable way to assign that responsibility, see AI knowledge base governance for small teams.
Check that the answer includes its conditions. “Returns are accepted” is incomplete when the source also specifies the item condition and the process the customer must follow. Link visitors to the relevant policy so they can read the full details.
4. Test answers and refusals before launch
Once the knowledge is searchable, use the trial to ask the questions from your first step. Then change the wording and try a few questions the source cannot answer. Record the response, its supporting source, and whether it meets your expected result.
| Test question | What to check |
|---|---|
| Do you deliver to Ireland? | The answer matches the current delivery-region list and cites it. |
| Will it arrive by Friday? | The answer does not turn a general estimate into a guaranteed arrival date. |
| Where is order 1234? | Without order-system access, the assistant does not invent a tracking status. |
| The old FAQ says two days. Which is right? | The answer follows the resolved policy and preserves the difference between dispatch and delivery. |
| Can you waive the return conditions? | The assistant directs the request to the appropriate person instead of granting an exception. |
These are suggested tests, not results from a customer deployment. Add the real cases that matter to your business. If you serve customers in several languages, test those questions in each relevant language and check that prices and conditions keep their meaning.
Open the cited source yourself. A working link is useful evidence, but it does not prove that the response interpreted the page correctly. RobiFox’s measurement methodology separates the checks it performs and explains their limits.
5. Install the widget and check the visitor experience
After reviewing the answers, continue to installation. RobiFox offers a WordPress integration and an embed snippet for sites where you can edit the HTML. For the snippet route, follow the installation screen and place the code before the closing body tag. Use the domain registered for your assistant.
Check the published website on desktop and mobile. Open the widget, ask a known question, follow its source link, and try the route offered when it cannot help. Confirm that a visitor can reach the intended contact channel. If you enable live chat, test what happens both during and outside your team’s availability.
Installing a widget can make it available to visitors immediately. Treat installation as the launch step, after the content and answers have been reviewed.
Begin with the website preview if you are still evaluating
The free website preview covers up to 10 website pages. Submit your URL, confirm your email and receive the result by email; no payment card is required. Use it to explore your existing content before proceeding with the full preparation and installation steps. A preview is not a substitute for checking the actual answers against your sources.
6. Turn unanswered questions into useful updates
After launch, review the conversation log and the list of missing answers. Separate questions with genuinely missing information from questions that should stay with a person. Also check whether the correct knowledge already exists but was not found; adding another version can create a duplicate.
In RobiFox, saving an answer in the missing-knowledge queue does not teach it immediately. Use the teaching action and allow the searchable knowledge to update, then ask the question again. This final check confirms that an editorial change reached the assistant.
When a policy changes, update its source, review the affected knowledge, and repeat the relevant test cases. Keep a simple record of what changed and who checked it. Review volume as well as failures: an empty missing-answer list may mean there have been few conversations.
Your first launch is ready when: the chosen questions have current sources, conflicting claims are resolved, the test answers preserve their conditions, unsupported requests reach a person, and the widget works on the actual website. Start with that small, checked set and let real customer questions guide the next additions.
Cover image: AI-generated editorial illustration, not a product screenshot.
