Use Cases / email-triage
Jev Email Triage
Shared inboxes drown in spam, FYI, and urgent asks. Rules break on new senders; LLMs overkill for label-only steps.
Try a related template free on this host — 5 anonymous real-API runs with no signup — then ship the same schema with a prepaid jv_live_ key. See is Jev free? and playground.
Why Jev
One decide call can return category choice, priority score, and needs-reply probability your worker can act on.
When to use Jev
- Support and sales shared inboxes
- Needs-reply filters before human review
- Spam / promo separation with confidence
When not to use Jev
- Drafting the reply body
- Calendar negotiation threads
- Full mailbox search / RAG over archives
Sample input and output
From the live tool template. Run it in the playground for a real API response — sample labels below are illustrative until you click Run.
Input
subject: Charged twice body: I was charged twice and need this fixed today.
Sample display fields
- category: billing · 98%
- priority: urgent · 86%
- spam: no · 4%
- needs_reply: yes · 97%
- route_to: finance · 93%
Failure modes and human fallback
- Upstream or network errors: retry with backoff; do not invent a decision.
- Low confidence: route to a human queue or safer default — never auto-act on money/destructive tools.
- Schema drift: keep a golden fixture set in CI so label changes fail the build before production.
API example
Same prepaid jv_live_ balance as tools. Output tokens are free on this host's metering model.
curl https://jevtypesafe.org/api/v1/decide \
-H "Authorization: Bearer jv_live_YOUR_KEY_HERE" \
-H "Content-Type: application/json" \
-d '{"state":"Email\nSubject: Charged twice\nBody: I was charged twice and need this fixed today.","questions":{"category":{"type":"choice","instructions":"What category is this email?","criteria":{"billing":"payments and invoices","support":"product help","sales":"buying or demos","partnership":"partnerships","other":"other"}},"priority":{"type":"choice","instructions":"What priority should this email have?","criteria":{"low":"can wait","normal":"standard queue","high":"important","urgent":"needs fast reply"}},"spam":{"type":"noul","instructions":"Is this spam or phishing?"},"needs_reply":{"type":"noul","instructions":"Does this email need a human reply?"},"route_to":{"type":"choice","instructions":"Which inbox or team should receive this?","criteria":{"finance":"finance / billing","support":"customer support","sales":"sales","founders":"founders / exec","ignore":"no action"}}}}'FAQ
- Does this connect to Gmail?
- Not built-in. Your worker fetches mail, calls /api/v1/decide, then applies labels via your provider API.
Related use cases
Ready to build?
Free anonymous tool runs, then prepaid packs and a jv_live_ key — independent host, not affiliated with TypeSafe AI.