A reliable chatbot starts with a well-maintained knowledge base, not a single clever prompt. This checklist shows what information to collect, how to structure it, which prompt templates to use, and when an AI chatbot should hand a conversation to a person.
Overview
A chatbot knowledge base is the controlled collection of information an AI chatbot can use to answer questions. For a small business, it may include product details, support procedures, delivery terms, booking instructions, policies, contact routes, and approved answers to recurring questions.
The goal is not to document every internal detail. The goal is to give the chatbot clear, current, usable information within a defined scope. Each entry should help the system answer one question or complete one task without requiring guesswork.
A practical knowledge base usually has five layers:
- Business context: what the business offers, who it serves, and what the chatbot is allowed to discuss.
- Customer information: products, services, prices where appropriate, availability, locations, and eligibility requirements.
- Process instructions: how to place an order, request support, make a booking, return an item, or contact the team.
- Response guidance: tone, formatting, terminology, links, and chatbot prompt templates for common situations.
- Escalation rules: the conditions that require a human review rather than an automated answer.
Store information in small, labeled sections rather than one long document. A question such as “How do I change my booking?” should lead to a direct procedure with its limits, required information, and next step. This makes updates easier and reduces the chance that outdated details remain hidden in unrelated paragraphs.
Checklist by scenario
Before building the chatbot
- Define the chatbot’s primary jobs, such as answering questions, collecting inquiries, guiding bookings, or routing support requests.
- List the audiences it will serve and the language they are likely to use.
- Identify topics that are out of scope, including advice or decisions that require a trained person.
- Gather the current sources of truth: product pages, support procedures, service descriptions, policies, and contact details.
- Assign an owner for each information area so updates do not depend on one person remembering to make them.
For product, service, or offer questions
- Give each product or service a consistent name, short description, intended customer, and distinguishing features.
- Separate confirmed facts from suggestions or opinions.
- State availability, geographic limits, lead times, and prerequisites when they affect the answer.
- Specify whether the chatbot may provide a direct link, collect an email address, or create a support request.
- Include approved alternatives for questions such as “Which option is best for me?”
For support and troubleshooting
- Write each procedure as numbered steps with a clear stopping point.
- Include the information the customer needs before starting.
- Describe common error messages in the exact wording customers may see.
- State when the chatbot should stop troubleshooting and offer human support.
- Provide a safe fallback if the customer cannot complete a step or does not know the required detail.
For lead capture and bookings
- Define the minimum information needed, such as name, contact method, request type, and preferred timing.
- Tell the chatbot how to confirm what it has recorded before ending the conversation.
- Explain what happens next, including the expected channel for follow-up if that process is known.
- Do not ask for sensitive information unless the workflow is designed to handle it appropriately.
- Include a human route for urgent, unusual, or high-value requests.
Prompt templates for teams
Prompt automation works best when templates are short, explicit, and reusable. A team can adapt the following patterns to its chatbot platform:
- Scope: “Answer questions about [topics]. If the request is outside this scope, explain the limit and direct the person to [human channel].”
- Source control: “Use only the information in the approved knowledge base. If the answer is not available, say so rather than inferring a policy, price, deadline, or availability.”
- Clarification: “If the request could mean more than one thing, ask one concise clarifying question before giving instructions.”
- Procedure: “Give the steps in order. Mention any prerequisite first, then end with the next action the customer should take.”
- Escalation: “If the conversation meets an escalation rule, acknowledge the issue, summarize the information already provided, and offer the approved human handoff.”
- Fallback: “I do not have enough information to answer that reliably. I can help with [approved topics] or connect you with [support route].”
Keep prompts separate from business facts. The prompt should define behavior; the knowledge base should hold details that change. This division makes prompt automation easier to review when products, workflows, or tools change.
What to double-check
Before publishing an AI chatbot, test the knowledge base with real phrasing rather than only carefully written questions. Include misspellings, short messages, incomplete requests, contradictory details, and questions that combine two topics.
Review whether each answer has a clear source, owner, and update date. Check links, contact routes, product names, booking steps, and any campaign-specific destinations. If the chatbot sends people to a tracked page, confirm that the destination and campaign tracking link still work. Related maintenance practices are covered in the guide to auditing broken short links and redirect chains.
Privacy deserves a specific review. Decide what information the chatbot should never request, what can be collected for a support handoff, where conversation data is stored, and who can access it. Describe these limits in plain language. Avoid placing confidential credentials, unnecessary personal records, or unreviewed internal notes in the knowledge base.
Use an escalation decision table to make handoffs consistent:
- Known, low-risk question: answer from the approved knowledge base.
- Missing or ambiguous information: ask one clarifying question, then use the fallback if uncertainty remains.
- Account-specific issue: collect only the approved details and route to the designated team.
- Complaint, sensitive matter, or urgent request: acknowledge the concern and offer a human handoff.
- Repeated failed attempts: stop repeating the same answer and escalate with a concise conversation summary.
Common mistakes
- One oversized source document: A long, unstructured file is difficult to update and may contain conflicting instructions. Break it into labeled entries.
- Vague authority: “Be helpful” is not enough. State what the chatbot can do, what it cannot do, and which source takes priority.
- Invented certainty: The chatbot should not fill gaps with plausible prices, deadlines, availability, or policy interpretations.
- No ownership: Every changing section needs a person or team responsible for review.
- Invisible escalation: A chatbot that only says “I cannot help” creates friction. Give it a useful handoff message and a defined route.
- Testing only the happy path: Include difficult, incomplete, and out-of-scope questions before launch.
- Mixing temporary campaign details with permanent guidance: Put seasonal offers and short-lived links in a clearly labeled area with an expiry or review date.
When to revisit
Review the knowledge base before seasonal planning cycles, launches, promotions, changes to operating hours, and changes to support or booking workflows. Also revisit it whenever the chatbot platform, model behavior, integrations, privacy settings, or escalation process changes.
After each review, sample unresolved conversations and record the reason for failure: missing information, unclear wording, an incorrect route, an unsupported request, or a prompt conflict. Update the smallest relevant entry, test related questions, and record what changed. Do not simply add another paragraph to compensate for a structural problem.
A lightweight maintenance checklist is enough for many small teams:
- Review unanswered and escalated conversations.
- Remove stale offers, links, policies, and process steps.
- Confirm every escalation route still reaches the right person or queue.
- Test the fallback response and at least one question from each major scenario.
- Record the review date, owner, and next planned check.
Use this checklist again whenever the underlying inputs change. A chatbot knowledge base is not a one-time setup; it is a small operational system. Clear source material, reusable prompt templates, deliberate fallbacks, and timely human escalation give an AI chatbot a practical boundary—and give the team a reliable way to improve it.