Email & lead triage
Classify, prioritize and route an inbound email in one call — the judgment behind sorting 500 emails in seconds.
Riley had Jev classify 500 emails in seconds for 3.5 cents — category, priority, spam, reply-or-not. These aren't open-ended writing tasks; they're high-frequency judgments with a fixed answer space. Route the high-confidence ones automatically and send only the uncertain ones to a human.
Try it live
This is the real thing, not a mockup. Edit the input, hit Run, and Jev returns every typed answer in one round trip — free, no signup. Now picture the same call fired across thousands of items in parallel.
Pick a demo, tweak the input, and hit Run Jev.
The decisions Jev makes
In a single call, Jev evaluates each of these — in parallel, against the same input:
What is this email primarily about?
picks one of these options:
sales— a prospect/deal in progresssupport— an existing customer needing helpbilling— invoices, payments or refundsspam— spam, cold pitch or irrelevantpersonal— personal or internal
How urgent is a reply?
rates it on an ordered scale:
- whenever
- this week
- today
- immediately
Is this spam or an unsolicited cold pitch?
returns a calibrated yes/no probability.
Does this email need a human reply?
returns a calibrated yes/no probability.
Where should this be routed?
picks one of these options:
sales_rep— an account executivesupport_agent— the support queuefinance— the finance/billing teamauto_archive— no action needed, archive
The exact request
This is the real payload behind the live demo — copy it, change the state, and you're building:
{
"model": "jev-latest",
"state": "From: dana@brightpathlogistics.com\nSubject: Re: proposal — a few questions before we sign\n\nHi — the team reviewed your proposal and we're keen to move ahead. Two things: can you do net-45 payment terms, and is onboarding included for 12 seats? We'd want to start next month. Thanks!",
"questions": {
"category": {
"type": "choice",
"instructions": "What is this email primarily about?",
"criteria": {
"sales": "a prospect/deal in progress",
"support": "an existing customer needing help",
"billing": "invoices, payments or refunds",
"spam": "spam, cold pitch or irrelevant",
"personal": "personal or internal"
}
},
"priority": {
"type": "score",
"instructions": "How urgent is a reply?",
"criteria": [
"whenever",
"this week",
"today",
"immediately"
]
},
"is_spam": {
"type": "noul",
"instructions": "Is this spam or an unsolicited cold pitch?"
},
"needs_reply": {
"type": "noul",
"instructions": "Does this email need a human reply?"
},
"route": {
"type": "choice",
"instructions": "Where should this be routed?",
"criteria": {
"sales_rep": "an account executive",
"support_agent": "the support queue",
"finance": "the finance/billing team",
"auto_archive": "no action needed, archive"
}
}
}
}Wire it into your code
Read the typed answers and branch in plain code — no parsing. Auto-handle the high-confidence cases and route the uncertain ones to a bigger model or a human. It's one API call and output is free, so ask every question you need at once.
Build your own
Every scenario above is a single API call. Try any of them free in the playground, then get a hosted key to ship it in minutes.