An answer can sound confident without being correct. Verification is most effective when you break the output into individual claims and check the details that affect your decision.
Separate claims from suggestions
Highlight names, dates, numbers, quotations and statements about current product behavior. These can usually be checked. Keep creative suggestions separate; they may be useful without being factual assertions.
Open the underlying sources
If the answer includes links, open them. Confirm the page exists, is relevant, and supports the claim as written. A page mentioning the same topic is not enough. Prefer the original product documentation or published dataset for technical details.
Check the date and scope
A feature may depend on country, plan, model or rollout stage. A source can be accurate for its publication date but no longer describe your account. Compare the claim with what your own interface and current official documentation show.
Verify numbers independently
Recalculate totals and percentages using your source values. Check units, denominators and rounding. If the assistant summarized a document, inspect the original table and surrounding notes rather than asking the same model whether it is sure.
Mark uncertainty instead of hiding it
If you cannot verify an important detail, remove it or label it as uncertain. Ask a relevant human specialist when the consequences warrant it. A polished sentence is not a reason to retain an unsupported claim.
Keep a short evidence trail
Save the source URL, access date and the specific claim it supports. For a repeatable workflow, use our claim-checking prompt to organize the work; you still need to perform the checks.