Tagged
Assemble the hold reason, aging, and promise-to-pay. Finance releases the order. The agent does not. The account-manager list still caps at 5 priorities — a hold is one of those 5, not a button.
Tell the shopper whether the order is in the return window and offer an exchange first. Do not buy the label and do not call createRefund. Where-is-my-order is about 18% of tickets; this is the next slice, not a second cashier.
Count sessions, handoffs, writes denied, and one wrong answer. At 50,000 sessions the published AgentCore silhouette is about $791 a month — a bill to plan, not money saved. We are not publishing a containment rate.
Run ten real lookups and three must-escalate cases before anyone outside the team sees the agent. Under 16 out of 30 on readiness, do not add a write. We are not publishing a pass rate from a client store.
Quote the customer's contract price, or say you cannot. A $5,000 auto-issue figure in the field guide is a placeholder, not your cap. A person still sends the quote. The public catalog is not the contract.
Ask for a risk brief, not a purchase order. A sample SKU at 5 days of cover is a fixture, not a client result. A buyer still sends the PO. Auto-send is an unattended purchaser.
TypeSafe priced Jev at $0.042/MTok with claimed 70–500 ms decisions on 15 Sep 2026. On AWS it is a System-1 sidecar, not a Bedrock replacement — reuse the Gateway ~180→95 ms canary and the ~$791/mo AgentCore silhouette as platform context, not as a Jev outcome.
On Sep 18, 2026 AgentCore microVM Runtime V2 went GA — AWS P75 cold starts 1.9–2.0s vs 5.4–30s on V1, but consumption rates rose to $0.1276/vCPU-hour and $0.0169/GB-hour. Memory reclaim waits 120 seconds.
A chatbot searches help articles. An agent uses tools and can be stopped. Relabeling search as an agent is how Browser-hot pilots hit ~3× Runtime-shaped spend.
Take the lookup work off the queue. Where-is-my-order is about 18% of tickets. Refunds stay with a person. We are not publishing a tickets-down percentage.
Score volume, pain, data, and write-risk. Readiness below 16 out of 30 means do not fund writes. McKinsey found 62% experimenting and 23% scaling in at least one function.
Automate the lookup pile first — not tax, capture, or labels. McKinsey found 62% experimenting with agents and 23% scaling in at least one function.