Evally
Support & ops

Support ticket router

Route every ticket to the right team, fast-track the urgent ones, auto-answer the easy ones.

The worked example of good question design: instead of 'categorize this email', four checkable rulings. Which team, is something broken right now, is there refund or cancellation language, and could a docs link fully resolve it. Each ruling is wired to an action, and unclear tickets go to a person.

Try it live

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

Examples
188
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 ticket, then asks 5 questions in one call.

  1. Q1TeamPick one

    Which team best matches what the sender is asking for in the ticket?

    BillingEngineeringSupportSalesAccountsOther
  2. Q2Blocked right nowYes / no

    Does the sender say something is currently broken or blocking their work?

  3. Q3Refund or cancel languageYes / no

    Does the ticket contain cancellation or refund language?

  4. Q4A docs link would doYes / no

    Could a link to documentation fully resolve this, without a person doing anything?

  5. Q5FrustrationScore

    How frustrated is the sender?

    1. 0Calm
    2. 1Annoyed
    3. 2Angry
    4. 3Furious or threatening to leave

How it decides

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

  1. 1
    If Team: confidence < 0.5Needs triagereview
  2. 2
    If Blocked right now ≥ 0.7 and Frustration ≥ 2 of 3Urgent
  3. 3
    If A docs link would do ≥ 0.75 and Blocked right now < 0.4 and Refund or cancel language < 0.4Send a docs link
  4. 4
    Otherwisethe answer to “Team”
  5. ·
    DefaultNeeds triage

Call it from your code

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

curl -X POST https://tryevally.com/api/v1/judges/ticket-router/run \  -H "Authorization: Bearer $EVALLY_API_KEY" \  -H "Content-Type: application/json" \  -d '{  "input": {    "ticket": "This is the THIRD time I'\''m writing. You charged us twice this month and now our account is locked, so my whole team can'\''t work. Fix this today or we'\''re cancelling and disputing the charge."  }}'

Seen in the wild

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

More in Support & ops