WHAT NEW IN X11.01 SUN

AI collections from X · 22 collections · 64,204 posts

jevVIDEO

Building an AI support desk with Jev and Opus 5.5

The author breaks a support desk into 10 steps: Jev scores tickets with probabilities in 70-500ms and picks the branch, Opus 5.5 only writes the hard replies, and hard logic like refunds stays in code.

Asteri
@Asteri_ethArchived 22 days agoOriginally posted 2026.10.09
Asteri @Asteri_ethOriginally posted 2026.10.09
Open original on X

JEV + OPUS 5.5 IS ABSURD FOR RUNNING AN AI SUPPORT DESK I went through the TypeSafe and Anthropic docs and mapped the whole desk on one page the 10 steps: 1. meet the pair > Jev reads the ticket, Opus 5.5 writes the hard replies, your code holds the branch 2. stop paying a writer to sort mail > Jev answers typed questions with a probability in 70-500ms. input is $0.042 per million tokens, output is free 3. ask everything at once > intent, urgency, angry or not, refund or not. all asked over the same ticket in parallel 4. branch on the number > TypeSafe's own pattern: under 0.6 goes to a human. a risky action between 0.6 and 0.85 gets confirmed with the customer. above 0.85 just runs 5. keep the math in code > Jev 1.13 doesn't count or compare dates reliably. refund windows and order totals stay in plain code 6. trim the ticket before you ask > Jev gets worse when the state is full of noise. code sends only the fields each question needs 7. keep the policy warm > Opus 5.5 cache reads are $0.20 per Mtok, 20x cheaper than the $4 fresh input 8. escalate the hard reply > the furious customer with three broken orders goes to Opus 5.5. 1M context at standard pricing, so the whole history fits in one call 9. gate the actual refund > Jev is not a security boundary. permissions and limits live in your code, Jev only says how sure it is 10. judge every closed ticket > Jev scores yesterday's tickets overnight. 100,000 tickets at 1,000 tokens each is $4.20 on TypeSafe's own math the result: an inbox that paid a frontier model to read every "where is my order" turns into a desk that spends a fraction of a cent to sort and pays properly only when a reply needs thinking if you build agents for clients, this is the support bot you can actually defend in the budget meeting the page maps the desk. the full Claude + Jev loop is in the article below ↓

This post quotes another post: x.com/asteri_eth/status/2104901781725598103

x.com/asteri_eth/status/2108498873748500987Archived 2026.10.10 10:08