Route Website Agent Questions to the Right Source
Map visitor questions before mapping pages
A website agent can only give useful answers when it can connect a visitor’s question to relevant information. Start by collecting real questions from support conversations, sales calls, contact forms, and site search. Keep the wording visitors actually use; “Can I change my plan later?” may appear alongside “How do upgrades work?”
Group each question by topic and intent. Topics might include pricing, setup, eligibility, shipping, or troubleshooting. Intent describes what the visitor wants to do: learn a policy, compare options, complete a task, or resolve a problem.
A simple question inventory might look like this:
| Visitor question | Topic | Intent |
|---|---|---|
| “What does the plan include?” | Pricing | Understand |
| “Can I add this to my site?” | Setup | Check compatibility |
| “Where is my order?” | Orders | Resolve an account-specific issue |
This inventory is the starting point for website agent source mapping. It shows where a clear source page could help, where several pages may be needed, and where a person must handle the request.
Avoid building the map around every possible phrasing. Group questions that need the same answer, then note meaningful differences. A visitor asking whether a service is available in a region may need a different answer from one asking whether they personally qualify, even if both use the word “eligible.”
Choose one authoritative page for each answer
For each question group, choose the page that owns the answer. A pricing page should be the source for current plan details; a setup guide should explain configuration; a policy page should state return or cancellation terms. The goal is to give the agent a clear, maintained source rather than several pages that happen to mention the same subject.
Record the connection in a small source map:
| Question group | Primary source | Answer boundary |
|---|---|---|
| Plan features and prices | Pricing page | Explain published options; don’t promise custom terms |
| Installation steps | Setup documentation | Give steps for supported setups |
| Account-specific status | Support contact page | Direct the visitor to a person |
Check that each chosen page is current, readable, and written clearly enough to support a direct answer. If two pages disagree, resolve the conflict at the source before relying on either one. If the answer is not published, don’t ask the agent to fill the gap from general knowledge. Add accurate public guidance or route the question to a person.
A useful source map also distinguishes what the agent may answer from what the source merely mentions. A page may describe a process without authorizing exceptions to it. For example, instructions for requesting a refund do not establish that a particular customer qualifies.
This is the practical core of AI agent answer sources: the page provides source material, while the business defines the scope of the answer. When retrieved source material is available, Simple Agent can provide citations at the chunk level, helping a visitor see which source material supports an answer. A citation is useful context, but it does not make an outdated or ambiguous page authoritative.
Handle questions that span multiple source pages
Some questions genuinely require more than one page. “Can I use this plan for my team, and what will it cost?” may involve both plan limits and pricing. Map the question to both relevant sources, and make sure the answer keeps those parts distinct.
Write down how the information fits together:
- Which source answers which part? The pricing page gives the published cost; the plan page describes included seats.
- Can the sources be combined safely? Confirm that the plan limits apply to the prices shown.
- What should happen if they conflict? Define which page is authoritative, then correct the other page if it is stale.
Do not combine pages just because they share a keyword. A shipping page and a returns page may both mention delivery, but they answer different questions. Likewise, avoid letting a general overview override a detailed policy.
If the agent cannot find a consistent answer across the relevant pages, the preferred response should be a clear handoff or boundary, not a confident guess. That is a key part of website agent question routing: route by the answer the visitor needs, not only by topic labels.
Decide which questions need a person or a clear boundary
A source map should identify questions that are suitable for a sourced answer, those that need a limitation, and those that should go to a person. This makes website question handling easier to review and keeps the agent’s role understandable.
The agent is a good fit when the answer is stable, publicly documented, and useful without knowing who the visitor is. Examples include published opening hours, setup instructions, and stated plan features.
Set a clear boundary when a question asks for something the public sources cannot establish. For example:
- Personal account details: “Has my payment gone through?”
- Individual eligibility: “Will you approve my application?”
- Exceptions or commitments: “Can you guarantee delivery by Friday?”
- Sensitive or consequential advice: requests that need qualified human judgment
A boundary should still help. Point the visitor to the right contact page or explain what information they should have ready. Don’t imply that the agent can inspect a private account, make a decision, or take an action unless that capability is actually configured.
Also consider questions that start as general but become personal. “What is the cancellation policy?” may be answerable from a public page. “Can you cancel my account now?” requires a person or a configured action path. The source map should make that distinction explicit so similar wording does not produce the same response by default.
When a question is unclear, the agent can ask a short clarifying question if the distinction changes which source applies. If clarification would not make the answer safe or supported, route the visitor to a person instead.
Review cited answers and update the source map
Review the answers visitors actually receive. A useful check is whether the response addresses the question, relies on the intended page, and cites relevant material when source material is available. If it answers from the wrong page, gives a partial answer without saying so, or makes a claim the source does not support, update the source map or the page itself.
To review answers against your own website sources, use your configured agent. See the Simple Agent plans.
During review, try representative questions from each group, including cases that span sources and cases that should reach a person. Check:
- Does the cited material support the specific claim?
- Is the source still current and authoritative?
- Does the answer stay within the documented boundary?
- Does the response tell the visitor what to do when the source is incomplete?
Keep a short record of the question, expected source, observed answer, and correction. When a page changes, revisit the question groups that depend on it. When support teams see a new recurring question, add it to the inventory and decide whether it belongs in a public source, needs a human, or falls outside the agent’s role.
For setup details, consult the Simple Agent documentation. To start mapping your own visitor questions, pick a Simple Agent plan, then review the answers in the agent configured with your sources.
Ready to build your AI agent?
Guided setup in 90 seconds. One flat price, published monthly volume.
Create my agent