[All resources](https://noodleseed.com/resources) Guides / Ecommerce # Knowledge base chatbot: turn store information into useful answers Prepare a reliable knowledge base for customer questions, with a source checklist, an answer template and a repeatable evaluation plan. Noodle Seed editorial Updated October 8, 2026 **In this article** [Start with questions that block a purchase](https://noodleseed.com/resources/knowledge-base-chatbot#section-0)[Choose the right source for each fact](https://noodleseed.com/resources/knowledge-base-chatbot#section-1)[Write an answer record a person can maintain](https://noodleseed.com/resources/knowledge-base-chatbot#section-2)[Resolve conflicts before adding more documents](https://noodleseed.com/resources/knowledge-base-chatbot#section-3)[Test answers and source changes](https://noodleseed.com/resources/knowledge-base-chatbot#section-4)[Connect knowledge to the next customer action](https://noodleseed.com/resources/knowledge-base-chatbot#section-5)[Your next steps](https://noodleseed.com/resources/knowledge-base-chatbot#checklist) The short answer A knowledge base chatbot answers from the information you provide. Start with a small set of maintained sources, define how conflicting or missing facts are handled, and test whether a customer can make the next buying decision. ## Start with questions that block a purchase A customer rarely asks for a knowledge base. They ask whether a product fits, which service includes installation or what happens if they need to return an item. Organise the source material around those questions. Collect a small sample of recurring, anonymised questions. Group them by the decision they support: choosing, buying, delivery or after-purchase help. For each, identify the person who owns the correct answer. Avoid uploading every company document before you know what the customer needs. ## Choose the right source for each fact Published policies and product guides can explain relatively stable facts. Current price, available stock and private order status need a source that can answer for the current request. A document describing last month’s catalogue is not a live inventory connection. | Question | Source to prepare | Owner’s check | | --- | --- | --- | | Does this fit my device? | Product compatibility guide | Model names and exclusions are explicit. | | Can I return it? | Published return policy | Region, product exceptions and conditions are present. | | Is my size available? | Current store data | Variant availability is checked. | | Where is my order? | Authorised order lookup | The requester’s access is verified. | ## Write an answer record a person can maintain Use a consistent record for each important topic. This is a content template, not a required Noodle Seed file format. - **Customer question:** the wording people actually use. - **Answer:** the fact and its conditions in plain language. - **Applies to:** product, region, plan or customer type. - **Source:** the approved page or system. - **Owner and review trigger:** who updates it and what makes it change. - **If uncertain:** the clarification or contact route to offer. For example, “Can I wash this cover?” needs the fabric, care instructions and any exception. “Easy to clean” is marketing language, not a washing instruction. Use the manufacturer’s supported care guidance rather than a plausible guess. ## Resolve conflicts before adding more documents Duplicate answers make maintenance harder. Choose one source for each policy, remove retired versions from the published set and make exceptions visible beside the general rule. Keep internal notes and customer-specific records out of public sources. When two approved pages disagree, decide which owner must resolve the conflict. The assistant should acknowledge a missing fact or route the question to a person rather than manufacture a compromise. A larger knowledge collection is useful only if it improves the answers. ## Test answers and source changes Create a small evaluation set with the expected answer and source for each question. Include a paraphrase, a question with a missing detail, an unsupported request and a conflict between old and new information. Then change one test source and repeat the affected cases. Record whether the answer is accurate, whether its conditions are preserved and whether the next step is useful. Keep unanswered questions separate from incorrect answers. Do not count a confident response as a pass when its source is missing. Use the [customer experience evaluation toolkit](https://noodleseed.com/resources/customer-agent-evaluation) to structure observations. These checks are a process for your team, not a claim that a particular supplier has passed them. ## Connect knowledge to the next customer action Once answers are reliable, choose the next useful action: show the right product, ask for a missing requirement or continue to the store’s checkout. Knowledge alone does not grant access to a customer account or permission to change an order. Noodle Seed’s [Shopify implementation guide](https://docs.noodleseed.dev/docs/guides/shopify-checkout) illustrates a path from store information to product selection and checkout handoff. For a different business, agree the sources, supported actions and customer journey before implementation. Read the [ecommerce guide](https://noodleseed.com/resources/ai-chatbot-for-ecommerce) for a buying-flow checklist, or [compare Noodle Seed and Chatbase](https://noodleseed.com/resources/noodle-seed-vs-chatbase) when choosing an approach. [Request early access](https://noodleseed.com/waitlist) Put it into practice ## Your next steps. Use this checklist to prepare your evaluation. Checks stay in this page and reset when you leave. Pick the buying questions customers repeat.Assign one authoritative source and owner per answer.Separate documents from live and private data.Test missing information, conflicts and source updates. 0 of 4 added to your review ### Make your evaluation repeatable. Use a shared test plan to compare behavior against the same customer tasks. [Explore the evaluation toolkit](https://noodleseed.com/resources/customer-agent-evaluation) Make your product conversational ## Start with one customer task. Explore what a better conversation could look like for your product. [Request early access](https://noodleseed.com/waitlist) --- Source: https://noodleseed.com/resources/knowledge-base-chatbot [All public pages in Markdown](https://noodleseed.com/llms.txt)