Recipe 1: route support emails

Limit the first version

Assign a redacted local email to shipping, refund, billing or other. You supply the file. This example does not connect to an inbox or modify a ticketing system.

Separate judgment from execution

Email sample → Jev selects a queue → code validates the answer → a person confirms → a future integration may update a ticket.

Check that the returned label is allowed and the confidence field is valid. Apply a threshold only after evaluation. Missing evidence, multiple intents and high-impact actions may need independent review gates.

Start with an offline demonstration

The bundled Python example uses a fixed response by default and makes no network request. It tests control flow and formatting, not Jev's actual performance.

python examples/support_router.py

After checking account access, cost and data permissions, explicitly enable live calls:

python examples/support_router.py --live --input examples/sample-email.txt

The key is read from TYPESAFE_API_KEY or a hidden terminal prompt. The example prints a classification and review status; it never sends messages, issues refunds or changes orders.

Why confidence is not refund authorization

A model signal does not establish order ownership, refund limits, eligibility, approval or idempotency. Deterministic code must enforce those conditions. The example's threshold is a teaching setting, not a calibrated production policy.

Acceptance checks

Test clear intent, unrelated text, multiple intents, empty input, timeout, invalid keys and unknown labels. Understand the cost of misrouting before enabling automated assignment. Keep consequential actions behind approval.