Decisions + code

Build an automation rule

Use probabilities to route a ticket, request review, or flag it as urgent.

The idea

Jev supplies judgments. Your code owns the policy. Changing a threshold reuses the same answers and makes no additional API call.

01 / Your input

Editable state

What are we asking Jev?

choice

department

Which support team should handle this message?

billing: Charges, invoices, refunds, and subscription payments
technical: Software bugs, outages, login issues, and integration problems
sales: Product pricing, purchasing, and plan comparisons

noul

is urgent

The message describes an issue requiring immediate or time-sensitive attention.

02 / Jev's answers

Awaiting a run

Edit the example, then run Jev to see real API results.

Your code's policy

Teaching thresholds only. No ticket is actually routed.

Auto-route when chosen option probability ≥ 80% Flag urgent when urgency probability ≥ 70%

Run an input to evaluate this rule.

if chosen_probability < route_threshold:
    request_human_review()
else:
    route_to(chosen_department)
if urgency_probability >= urgent_threshold:
    flag_urgent()

Try this next

Run an ambiguous message, then move the thresholds. Can you change the action without changing Jev's answer?

03 / Under the hood

Request JSON (preview)

Response JSON

Run an experiment to see the response.

Confidence summarizes the shape of the probability distribution; it is not a guarantee of accuracy. Noul returns a probability, not a separate confidence value. Latency includes the server's SDK call.