Set a virtual agent's knowledge boundary around what it can substantiate for the customer's task. Define approved sources, freshness expectations, and unsupported questions before measuring answer fluency. A confident response outside that boundary should fail the acceptance test.
Level AI describes configurable virtual-agent workflows. Google Cloud documents data-store traces including supporting documents and grounding checks. Such documentation identifies evidence to inspect; it does not demonstrate that a particular deployment answers every question correctly.
What belongs in an answer-boundary register?
An answer-boundary register is a small inventory connecting a question type to the evidence permitted for answering it. Give every entry an owner and a fallback. Keep public policy explanations distinct from account-specific facts that require an authorized system lookup.
| Question type | Boundary to record |
|---|---|
| Published service policy | Approved version, scope, and effective date |
| Account or order status | Required verified lookup and permitted disclosure |
| Unsupported exception | Explicit escalation instead of an invented concession |
| Conflicting documents | Source precedence and a review owner |
| No relevant evidence | Honest limitation and supported next step |
Do not assume that connecting a document repository makes every page suitable for customers. Separate internal notes, outdated instructions, examples, and draft policies from the material the virtual agent may use. Confirm how that distinction is represented in the actual product configuration.
Which difficult questions should be tested?
- Ask a supported question with a current, unambiguous answer.
- Ask the same question when the relevant document is missing.
- Provide two sources with conflicting dates or instructions.
- Request an exception the approved policy does not permit.
- Ask for an account fact that cannot be established from general knowledge.
- Use a question that resembles an allowed topic but requires a different authority.
The expected response may be a clarification, a bounded answer, or a handoff. Define the expectation beforehand and preserve the source version used. An answer matching an old test case can become wrong after a policy changes.
How should source changes be reviewed?
Assign a knowledge owner to review additions, removals, and conflicting pages. Keep a short set of supported and unsupported questions for each material change. Check whether retrieved evidence changed and whether the answer still stays within it, rather than inspecting only its tone.
Record the answer, supporting evidence, configuration version, and the reason for a fallback. When trace visibility is unavailable, mark the response's evidence as unestablished and request a product-specific way to investigate. Do not convert a lack of visibility into a passing score.
Where does this differ from agent assistance?
A human agent can review a suggestion before communicating it. A virtual agent may communicate directly, so the accepted fallback and answer boundary need to be explicit in the automated path. Compare the agent-assist knowledge guide with the handoff requirements when deciding who resolves uncertainty.
How should conflicting policy documents be resolved?
Define a precedence register with an owner before the virtual agent answers customers. The invented example below concerns a return window; it describes source handling, not a real retailer policy.
| Evidence condition | Proposed answer rule | Record to retain |
|---|---|---|
| Current approved policy and matching product scope | Answer within that policy, with its effective date and relevant conditions | Document ID/version and supporting passage |
| Old FAQ conflicts with a newer approved policy | Apply the documented precedence rule; flag the stale FAQ for repair | Both versions and reason for preferring one |
| Two approved sources conflict without precedence | State that the answer cannot be confirmed and route for review | Conflict, affected question and accountable owner |
| Customer-specific exception absent from approved records | Avoid inventing an exception; request permitted evidence or transfer | Missing fact and safe next step |
Test source retrieval separately from answer correctness. Finding a relevant document does not establish that its conditions apply to the customer's product or date. Review the final answer against the allowed evidence, and keep unsupported questions as explicit outcomes rather than forcing a plausible answer. Re-run these cases whenever the document, retrieval filter or precedence rule changes.
Limits
This register is a proposed evaluation artifact. It does not certify grounding accuracy, document ingestion, source permissions, or freshness guarantees for any vendor. Validate those capabilities and operational responsibilities in the intended system before relying on generated answers.