JJEV Gateway
Sign in

Use case

Support ticket routing

Classify urgency, team and tone on every inbound ticket before it hits a queue.

The problem

Routing rules miss sarcasm, multi-intent tickets and silent VIP accounts.

What your code does with the answer

If urgency is high and confidence is low, page a human. Otherwise enqueue to the chosen team.

curl
curl https://jevai.website/api/v1/systemone \
  -H "Authorization: Bearer $JEV_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "state": "Help! My payouts have been failing for 3 days and my customers are asking where their money is.",
  "questions": {
    "is_urgent": {
      "type": "noul",
      "instructions": "Does this convey urgency?",
      "criteria": {
        "true": "Explicitly time-sensitive or business-critical",
        "false": "No urgency expressed"
      }
    },
    "department": {
      "type": "choice",
      "instructions": "Which team should handle this?",
      "criteria": {
        "billing": "Payments, payouts, invoicing, refunds",
        "technical": "Bugs, outages, integrations",
        "sales": "Pricing, upgrades, new accounts"
      }
    },
    "frustration": {
      "type": "score",
      "instructions": "How frustrated is the customer?",
      "criteria": [
        "Calm",
        "Frustrated",
        "Very angry"
      ]
    }
  }
}'
Run this in the playground