# Review the next step after the assistant says no

A refusal should have a reason and a useful consequence. Inspect whether the product clarifies, escalates or denies access according to the actual gap.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Choose three different failures

Use one question missing a user detail, one unsupported by the source collection and one outside the user's authority. Ask the team to show the internal outcome and user-facing response for each.

The first may need a focused clarification. The second may need a limited answer or owned escalation. The third needs an enforced access denial. If all three produce the same generic message and retry path, the design is hiding distinctions that matter.

Check whether the assistant preserves the original task after clarification. The user should not need to restate everything to supply one missing value.

## Inspect the evidence decision

Ask which facts or signals led the system to withhold the answer. A relevance score or confident model explanation is not enough on its own to establish sufficiency.

Review a near-miss source that discusses the topic without answering the exact question. Confirm the system does not attach a real citation to an unsupported conclusion.

Look at the limited-answer format. The unsupported part should be visibly bounded, and the opening sentence should not encourage an action that a later caveat quietly withdraws.

## Follow the escalation route

Verify the destination exists, the recipient has authority and the package contains the unresolved question and relevant evidence. Check whether the application actually submits the handoff or only creates a draft for the user.

Inspect duplicate prevention for ticket or message creation if that action is integrated. A refusal path can still cause side effects and needs the same execution discipline as other tools.

Review sensitive data in handoffs and logs. Declining to answer does not make all surrounding information safe to share broadly.

## Examine unnecessary refusals

Ask for examples the system should answer but currently declines. Inspect how those cases are measured and whether a candidate improves them without introducing unsupported answers.

Record the next-step policy and its known limits. The review is complete when a user can understand why the assistant stopped and what can happen next, while the application preserves evidence and authority boundaries through that continuation.

## Sources

- [Microsoft Learn: retrieval and answer evaluators](https://learn.microsoft.com/en-us/azure/foundry/concepts/evaluation-evaluators/rag-evaluators)
- [OWASP: authorisation guidance](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html)