# Give the chatbot a smaller, trustworthy job > Decide what a website AI chatbot can answer, which sources it may use, when it must say it does not know, and how an owner keeps answers current. Source: https://scayverstaging.1wp.site/resources/site-operations/ai-chatbot-knowledge-boundaries/ ![Woman at a desk using a desktop computer, looking intently at the screen.](https://scayverstaging.1wp.site/wp-content/uploads/2026/09/sg-resources-146859-hero.webp) A website AI chatbot should answer a defined set of visitor questions from approved material, not improvise prices, policies, availability, credentials, or outcomes when a source is missing. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) [Every resource](https://scayverstaging.1wp.site/resources/) **Format** [Guide](https://scayverstaging.1wp.site/resources/type/guide/) **In this format** 92 ## Which questions should the website AI chatbot handle? Begin with the questions people actually ask and the documents the business is willing to stand behind. Then design the limits of the answer. Group incoming questions by decision. A visitor may ask what a service covers, how to start, what information to prepare, or where to find support. Those questions can often use public, stable website content. Questions about a specific account, order, contract, or regulated advice require different permissions and may be better handed to a person. Pick an initial narrow scope. For each question, identify the approved source, answer owner, and review trigger. If no approved source exists, create one or exclude the topic. A chatbot trained on a messy folder of outdated drafts can make the confusion sound confident. Better retrieval cannot fix authority that the business has not defined. ## What counts as an acceptable answer? Write examples of a good answer, an incomplete answer, and a question the bot should decline. A good answer names the relevant service, explains the next step, and links to the source page. An incomplete answer says what it can confirm and directs the visitor to a person for the missing detail. Do not let the bot invent a package price or promise a result to avoid saying it does not know. NIST’s [AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) offers a useful model for defining an AI system’s context, measuring behavior, and governing changes. Apply that idea practically: assign an owner, test representative questions, and review failures rather than treating launch as the end of quality control. ## How will the knowledge stay current? Choose a source of truth. Public service pages, owner-approved FAQs, and current process documents may have different update cycles. Record which content can feed public answers and which stays private. When a service changes, there should be a clear way to update or remove the old answer before it misleads visitors. Test with ambiguous wording, misspellings, conflicting source passages, and a request for information outside the approved scope. Review whether the bot cites the right page, preserves uncertainty, and points to a human when needed. Do not score it only on how often it responds. Sometimes the correct behavior is to stop. ## What information should it collect? If the bot collects a lead, define the minimum fields and what consent and privacy notice the organization approves. Separate public guidance from personal account support. A general website assistant should not request sensitive information simply because a visitor volunteers it. Define retention, access, and deletion through the business’s reviewed data process. ## Build a test set before the pilot. Bring ten common questions, their approved source pages, and three out-of-scope examples. That provides a test set for a pilot. See [AI chatbot development](https://scayverstaging.1wp.site/services/development/ai-chatbot-development/) for the service path. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/) to define a useful assistant with boundaries your team can maintain. [Explore the site-operations guides](https://scayverstaging.1wp.site/resources/site-operations/). Guides ## Guides beside Give the chatbot a smaller, trustworthy job. 1. ### [Define the website before you price the build](https://scayverstaging.1wp.site/resources/site-operations/website-requirements-checklist/) Site operations · 4 min read 2. ### [Choose a CMS around the work your team does](https://scayverstaging.1wp.site/resources/site-operations/choosing-a-cms/) Site operations · 3 min read 3. ### [Use the smallest build that solves the real problem](https://scayverstaging.1wp.site/resources/site-operations/plugin-vs-custom-development/) 4. ### [Map the handoff between tools before you automate it](https://scayverstaging.1wp.site/resources/site-operations/integration-data-map/) 5. ### [Check the dependency before it becomes invisible](https://scayverstaging.1wp.site/resources/site-operations/api-vendor-due-diligence/) 6. ### [Plan checkout as a business process, not a button](https://scayverstaging.1wp.site/resources/site-operations/checkout-flow-planning/) 7. ### [Give the product catalog a structure that can grow](https://scayverstaging.1wp.site/resources/site-operations/ecommerce-catalog-structure/) 8. ### [Decide the order rules before you configure checkout](https://scayverstaging.1wp.site/resources/site-operations/shipping-and-tax-workflow/) 9. ### [Make the return path clear before someone needs it](https://scayverstaging.1wp.site/resources/site-operations/returns-content-structure/) 10. ### [Define access rules before the member dashboard](https://scayverstaging.1wp.site/resources/site-operations/membership-access-model/) 11. ### [Design the learning workflow before choosing the LMS](https://scayverstaging.1wp.site/resources/site-operations/lms-delivery-requirements/) 12. ### [Ask for what the appointment actually needs](https://scayverstaging.1wp.site/resources/site-operations/appointment-booking-fields/) 13. ### [Make website leads usable inside the CRM](https://scayverstaging.1wp.site/resources/site-operations/crm-field-mapping/) 14. ### [Stop form spam without punishing real visitors](https://scayverstaging.1wp.site/resources/site-operations/form-spam-and-privacy/) 15. ### [Every automation needs an owner when it stops](https://scayverstaging.1wp.site/resources/site-operations/automation-failure-handling/) 16. ### [The handoff is part of the answer](https://scayverstaging.1wp.site/resources/site-operations/ai-human-handoff/) 17. ### [Name the action before you tag the button](https://scayverstaging.1wp.site/resources/site-operations/analytics-event-naming/) 18. ### [Test the conversion, not just the dashboard](https://scayverstaging.1wp.site/resources/site-operations/conversion-event-validation/) 19. ### [Make measurement follow the choice a visitor makes](https://scayverstaging.1wp.site/resources/site-operations/consent-and-analytics-planning/) 20. ### [Spend page weight on things visitors can use](https://scayverstaging.1wp.site/resources/site-operations/website-performance-budget/) 21. ### [Accessibility continues every time someone publishes](https://scayverstaging.1wp.site/resources/site-operations/accessibility-content-operations/) 22. ### [Test the backup before you need it](https://scayverstaging.1wp.site/resources/site-operations/backup-restore-drill/) 23. ### [Update the plugin, then prove the journey still works](https://scayverstaging.1wp.site/resources/site-operations/plugin-update-staging/) 24. ### [An alert needs a person and a next action](https://scayverstaging.1wp.site/resources/site-operations/monitoring-ownership/) 25. ### [Know what ongoing website care actually covers](https://scayverstaging.1wp.site/resources/site-operations/website-care-scope/) 26. ### [Keep the domain and its connected services in view](https://scayverstaging.1wp.site/resources/site-operations/domain-dns-transfer/) 27. ### [Decide what to carry before you rebuild](https://scayverstaging.1wp.site/resources/site-operations/content-migration-inventory/) 28. ### [Give each old link a sensible destination](https://scayverstaging.1wp.site/resources/site-operations/redirect-mapping/) 29. ### [Decide how to reverse a bad launch before launch day](https://scayverstaging.1wp.site/resources/site-operations/website-launch-rollback/) No other guides in this group yet. Keep reading ## Read after Give the chatbot a smaller, trustworthy job. The rest of the resources, newest first. - [2 July 2026 Customer Persona Worksheet](https://scayverstaging.1wp.site/resources/customer-persona-worksheet/) - [2 July 2026 The Social Content Sprint Playbook](https://scayverstaging.1wp.site/resources/the-social-content-sprint-playbook/) - [2 July 2026 AI Prompt Pack for Blog Post Outlines](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-blog-post-outlines/) - [2 July 2026 Email Welcome Sequence Template](https://scayverstaging.1wp.site/resources/email-welcome-sequence-template/) - [2 July 2026 Website Pre Handoff QA Checklist](https://scayverstaging.1wp.site/resources/website-pre-handoff-qa-checklist/) - [2 July 2026 The SEO Content Audit Guide](https://scayverstaging.1wp.site/resources/the-seo-content-audit-guide/) - [2 July 2026 Positioning Statement Worksheet](https://scayverstaging.1wp.site/resources/positioning-statement-worksheet/) - [2 July 2026 The Client Onboarding Playbook](https://scayverstaging.1wp.site/resources/the-client-onboarding-playbook/) - [2 July 2026 AI Prompt Pack for Ad Headline Variations](https://scayverstaging.1wp.site/resources/ai-prompt-pack-for-ad-headline-variations/) - [2 July 2026 The One Page Creative Brief Template](https://scayverstaging.1wp.site/resources/the-one-page-creative-brief-template/) - [2 July 2026 Brand Launch Readiness Checklist](https://scayverstaging.1wp.site/resources/brand-launch-readiness-checklist/) - [2 July 2026 The Landing Page Teardown Guide](https://scayverstaging.1wp.site/resources/the-landing-page-teardown-guide/)