Evally
Support & ops

Inbox triage

Sort every email: action needed, FYI, meetings, newsletters, receipts, spam, and what's urgent.

One call per email puts it in a folder and flags what needs a reply today. People report sorting hundreds of emails for a few cents. Paste the sender, subject and body together.

Try it live

Real calls to Jev. Pick an example or paste your own.

Examples
211
No verdict yet

Pick an example or paste your own input, then run it.

Under the hood

Every question and rule, in the open. Fork it to change any of them.

What it asks

Reads email, then asks 3 questions in one call.

  1. Q1KindPick one

    What kind of email is this?

    Action neededFYIMeetingNewsletterPromotionReceipt or noticePersonalSpamOther
  2. Q2Needs a reply todayYes / no

    Does the email need a response today (an explicit deadline, someone blocked, or something breaking)?

  3. Q3Written by a personYes / no

    Was the email written personally by a human to the recipient, rather than sent automatically or in bulk?

How it decides

Rules run in code, top to bottom. The first one that matches gives the verdict.

  1. 1
    If Needs a reply today ≥ 0.7 and Kind is Action neededUrgent
  2. 2
    Otherwisethe answer to “Kind”
  3. ·
    DefaultAction needed

Call it from your code

Every template runs as-is with an API key, no setup: POST /api/v1/judges/inbox-triage/run.

curl -X POST https://tryevally.com/api/v1/judges/inbox-triage/run \  -H "Authorization: Bearer $EVALLY_API_KEY" \  -H "Content-Type: application/json" \  -d '{  "input": {    "email": "From: Sarah Kim (Head of Finance)\nSubject: Need sign-off on vendor contract by 5pm\n\nHi, Legal needs your approval on the Datadog renewal before 5pm today or we lose the 20% discount. Can you reply with a yes/no?"  }}'

Seen in the wild

Community builds on Jev that use this pattern. Not affiliated with Evally.

More in Support & ops