Hands-on: support email routing

Route desensitized mail into shipping/refund/billing/other for human review—never refund or send mail from the model path.

Scope for v1

Mail sample → Jev Choice over queues → code validates the label → human confirms → (later) ticketing.

Do not connect a live mailbox or mutate orders in the first loop.

Guard layer (always)

Before any side effect, code checks:

• Label ∈ allow-list?
• Confidence present and above your calibrated threshold? (demo numbers are not yours)
• Multi-intent / insufficient evidence / high-impact flags?

Why “high confidence → refund” is wrong

Confidence is a model signal, not business authorization. Amount, ownership, refundability, approver, and idempotency stay in deterministic checks.

Acceptance

Exercise clear mail, off-topic, multi-intent, empty input, timeouts, bad keys, unknown labels. Record cost of mistakes before auto-assigning.

Sources

• Intent routing
• Confidence
• Use-case map