Start with the boundary.
Anthropic’s agent engineering guidance favours simple, composable patterns and meaningful human oversight. The practical implication for a business: decide which actions a system may take, which require confirmation and which belong with a person before choosing a model.
A hypothetical sales journey.
Imagine a customer asking about a product on WhatsApp, then requesting an exception to a delivery promise. The assistant may explain approved product information. It should not invent stock availability, negotiate unsupported terms or promise an exception. It should transfer the request with enough context for a person to decide.
Make the handoff a real workflow.
Our recommended handoff packet includes the customer’s question, a short factual summary, relevant record references and the reason for escalation. Identify an owner and make the pending state visible. Avoid copying unnecessary personal data or including speculative model reasoning.
Handle the uncomfortable paths.
What happens outside business hours? What if the CRM is unavailable? What if the customer sends the same message twice? Design a safe acknowledgement, duplicate prevention and a retry policy. A failed tool call must not be presented as a completed action.
Test more than answer quality.
Use a small evaluation set with ordinary requests, ambiguous requests, unsupported promises and tool failures. Track successful resolution, repeated questions after transfer, unresolved handoffs and unauthorised actions. Review examples with the people who actually receive escalations.
The goal is continuity.
This is an illustrative implementation pattern, not a reported client result. The business value to test is whether people reach a useful resolution with less friction—not whether the assistant can keep every conversation away from a human.
Sources & context
Sources checked 2026-09-10. Recommendations and illustrative scenarios are Noesis’s analysis, not claims of client results.