Salesforce MVP Hall of Fame · Certified Partner since 2010
Support ticket routing
Every ticket to the right queue in one call. The unsure ones go to a person, not a guess. The first week is in the org, reading what already exists.
Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agents · Agentforce, CrewAI, ADK, A2A
- 03Memory · Neo4j, Cognee, RAG
- 04Identity · IndyKite, SSO, entitlements
- 05Governance · policy, audit, human override
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
The decision
The decision, drawn.
Choice over 5-50 queues + Noul 'needs a human now' in one call; auto-route above 0.9 confidence
Jev · Choice+Noul
Which queue should this ticket go to, and does it need a person now?
- billing
- technical
- account
- other
Charged twice this month. Payouts failing since Monday.
- billing0.87
- technical0.12
- account0.01
- other0.00
Noul · escalate 0.95
The job
What has to be true.
Act at 0.90 confidence or higher. Below that, a person or a larger model. Act at 0.85 or higher. Block at 0.15 or lower. Between 0.35 and 0.65, a person decides.
The figure
Builder's figure. Not reproduced by us.
40 tickets across 9 desks for about $0.0016; TypeSafe eval: customer service 76.0 vs 78.3 best comparator
apimodels.app/jev-use-casesWrite your house rules into the request. When rules were left out, Jev got 5 of 24 right with high confidence (Huryn). Validate thresholds on labelled samples.
The brief
Name the decision your team makes a thousand times a day.
We read the process and write down where Jev fits, where it does not, and where the line sits.