Adding a generic chatbot to a specific problem is treating an LLM like a UI pattern instead of a capability to design around deliberately.
1Constrain the Interaction to the Real Problem
A generic chatbot invites any question, including ones the underlying content can't actually answer, which produces vague or hallucinated responses. Scoping the interaction tightly to the actual problem (search this specific FAQ) produces a more reliable, more useful feature.
2Require the Answer to Show Its Work
Requiring every answer to cite the specific source it came from isn't a nice-to-have — it's what turns an AI feature from 'trust me' into something a user can actually verify, which matters enormously for trust in exactly the kind of reference-lookup use case this problem represents.
3Step-by-Step Breakdown
AI-Native, Not 'AI Bolted On'. This module's problem: users want to quickly find the right answer in a long internal FAQ document instead of reading the whole thing. A lazy answer is 'add a chatbot.' An AI-native answer designs the feature around what LLMs are actually good at — let's find the real difference.
Ask the Model to Critique the Lazy Version. Before designing the real feature, get the model to articulate why 'just add a chatbot widget' is usually a weak design for this kind of problem.
What's the core weakness of 'bolt on a generic chatbot widget' as a design response to a specific problem like this?
- →It's a generic solution applied without designing around the specific problem — it invites open-ended questions beyond the FAQ's scope and doesn't surface which source backs an answer.
- →Chatbots are always more expensive to run than any other kind of AI feature, regardless of design.
Design the AI-Native Version. Now design deliberately: constrain the interaction to the actual problem, and require the answer to cite its source. Ask the model to help draft this more purpose-built design.
Constraints Are the Design, Not a Limitation. The AI-native version isn't 'more AI' — it's more deliberately scoped AI. Constraining the interaction and requiring citations makes it more trustworthy and more useful than an open-ended chatbot would be for this specific problem. Next: designing for the uncertainty and streaming behavior this kind of feature actually has.
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Cited Sources Need to Be Reachable, Not Just Visible
A citation link next to an AI-generated answer should be a real, keyboard-reachable, properly labeled link — not just styled text — so a screen-reader or keyboard-only user can actually navigate to verify the source, the same as any sighted user reading the citation visually.
<a href={sourceUrl} aria-label={`View source: ${sourceTitle}`}>View source</a>SEO Implications
- 1
Target 'AI-native feature design' distinct from generic 'how to add a chatbot to your app' content
Readers researching this specifically want the design discipline of scoping and constraining an AI feature to a real problem, not a chatbot-widget integration tutorial.
Best Practices
Design the Failure Mode Before the Happy Path
For any AI-native feature, explicitly design what happens when the model can't find a good answer within scope — a clear 'not found in this FAQ' response is part of the design, not an edge case to handle later, especially since silently hallucinating an answer is worse than admitting uncertainty.
Frequent Bugs
Building an open-ended chatbot interface for a problem that would be better served by a scoped, source-citing search-and-answer feature.
Before defaulting to a chatbot UI, ask whether the actual problem is better served by constraining the interaction and requiring citations — reserve open-ended conversational UI for problems that genuinely need multi-turn, unconstrained interaction.
Real-World Examples
From Chatbot to Cited Search
A team's first version was a generic FAQ chatbot that occasionally answered questions outside the FAQ's actual content, confusing users. Redesigning it as a scoped search-and-answer feature with mandatory source citations both reduced confusing answers and increased user trust, measured by a drop in 'was this helpful' negative feedback.
// v1: open chatbot, no citation, occasional out-of-scope answers
// v2: scoped search, mandatory citation, 'not found' fallback