Why it matters
Source-backed answers let users and auditors verify claims. Backing is dispute infrastructure for billing and policy disagreements, not polish.
Support debugs faster when citations show the same passages customers can open.
Backing is how you survive billing disputes and regulatory inquiries with evidence, not confidence. Screenshots of chat without sources are weak artifacts.
Users learn quickly whether citations are decorative. One bad citation trains them to ignore all citations.
How it works
Tier backing requirements by intent risk. Billing and legal need passage-level support.
Validate claims against cited chunks automatically when feasible.
Store retrieval snapshots for high-risk answers per retention policy.
Train support to use citations during escalations for human-bot alignment.
Tier backing strictness: passage-level for legal and billing, article-level for low-risk navigation questions.
Train support to open citations during escalations. Humans and bots align when both cite the same Refund Policy section.
Example
Nintendo chatbot answers refund eligibility with passages from the Nintendo Refund Policy and links to the Help Center refund request guide. Each date and dollar limit maps to a visible citation customers can open.
Common mistakes
- 1Citations that decorate answers not actually supported by retrieved text
- 2Backing required for some intents but not billing and legal
- 3No validation that retrieved chunks contain the claims made
- 4Source links that rot because URLs changed without reindex
Test the answer before your customer does.
Run answer tests and evaluations against your governed knowledge before you ship.
See answer evaluations