# Route an unresolved answer to someone who can help

A handoff should carry the unanswered question and evidence already checked. Make the next owner clear without promising work the application has not actually submitted.

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

## Identify why the task remains unresolved

Read the recorded reason: missing source information, conflicting evidence, unclear user input or a business decision outside the assistant's authority. These reasons may need different recipients.

Check whether one focused clarification can still resolve the task. Escalating too early creates avoidable work, while repeatedly questioning the user about information the source does not contain is equally unhelpful.

Keep access denials separate. A person should not receive restricted evidence merely because the assistant could not answer within the user's permissions.

## Prepare a concise evidence package

Include the user's original task, relevant supported findings and the precise unresolved point. Reference source versions and locations where the recipient is authorised to inspect them.

For example, explain that two approved manuals give different instructions for the same identified product version, rather than forwarding a long conversation with the note "AI unsure". The recipient can then investigate the actual conflict.

Avoid including speculative conclusions as established facts. Label any proposed interpretation and preserve the distinction between evidence and inference.

## Use an owned destination

Route through a configured support or review process with a clear owner. The assistant should not invent an email address, team or response commitment from general knowledge.

If the product only creates a draft summary, say that the user still needs to submit it. If it creates a ticket, record the ticket identifier and verify creation before claiming that support has received the request.

Handle submission timeouts through the operation's reconciliation or idempotency path. An unresolved answer should not produce duplicate tickets because the handoff response was lost.

## Close the loop when an answer arrives

Associate the resolution with the original task and show the user what was established. If the source material needs correction, route that work to its owner rather than teaching the assistant to rely indefinitely on an isolated support reply.

Record the cause of escalation so repeated gaps can improve the knowledge base or input flow. Review how much work the recipient had to repeat.

A dependable handoff does more than decline an answer. It preserves useful progress, respects the recipient's authority and makes the next action observable to the person who asked for help.

## Sources

- [OWASP: authorisation guidance](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html)
- [AWS Builders' Library: idempotent APIs](https://aws.amazon.com/builders-library/making-retries-safe-with-idempotent-APIs/)