An unsupported answer can sound convincing. A useful assistant must recognise when the available material does not justify a response and make the limitation visible.
The decision to make
Design an explicit fallback for missing, conflicting or restricted information. Refusing to guess is a product behaviour that should be tested.
Practical checklist
- Include questions absent from the source collection.
- Test ambiguous questions and conflicting documents.
- Offer a human contact or a request for clarification.
An illustrative example
If a customer asks for an exception that is not covered by an approved policy, the assistant should not invent authorisation.
Your next step
Measure unsupported-answer behaviour alongside successful answers; a polished response alone is not evidence of correctness.
AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.