Overview
How might we design verification next steps so people can trust and act on AI output?
When to use
- Essential for sales assistants, support copilots, and research tools where low-confidence answers must route users to a checkable source or human before send.
When to skip
- Low-stakes creative suggestions where verification would feel preachy.
- Answers that are already fully grounded with strong citations and no residual risk.
- Automations that must complete without stopping for human validation.
Rules
Generic “please verify” banners with no actionable link or step.
Next steps that send users outside the product with no return path.
Showing verification only after the harmful action already ran.
Checklist spam on every message, training users to ignore it.
Evidence
| Product | Implementation |
|---|---|
| Glean | Suggested follow-ups to open source docs and owners. |
| Intercom Fin | Handoff and article links when the bot is unsure. |
| Salesforce Einstein | Recommended review actions beside AI CRM suggestions. |
| Enterprise knowledge bots | Validate-with-owner and open-policy shortcuts on answers. |