Loading

What TypeSafe Jev Is

TypeSafe Jev is a decision model from TypeSafe AI. You give it some text or data and one or more typed questions, and it answers every question at once with probabilities, usually in well under a second. It never writes text.

The platform uses it wherever something has to be decided rather than written: which way a workflow goes, whether an incoming message is about a particular thing, and which account a bank line should be coded to.

Where to find it

Architect Panel → Activity:

  • TypeSafe Jev — the console: status, connection check, test call, playground and recent calls

Architect Panel → Automation:

  • Workflow Builder — the AI decision and AI check steps

Architect Panel → Communication:

  • Inbound Messaging — Is about (AI) rules on SMS and WhatsApp routes

Architect Panel → ERP - Finance:

  • Feed Queue — account and tax code suggestions for bank and accounting feed lines

Three kinds of question

  • Choice (pick one). Choose one of 2 to 255 options you supply, such as which team should handle a ticket. The answer is the option chosen, a probability for every option and a confidence.
  • Score (ordered levels). Place the input on a scale of 2 to 10 levels, lowest first, such as how frustrated a customer is. The answer is the most likely level, a score that can fall between two levels, and a confidence.
  • Yes / no. How likely a plain-English statement is to be true, such as "The customer is asking for a refund". The answer is one probability between 0 and 1.

Every question is answered from what you send and nothing else. Jev has no access to your database and does not look anything up.

The answer says what; the confidence says whether to act

Each feature turns Jev's answer into an outcome before acting on it:

  • Choice or score: confident when the confidence reaches the bar (0.6 unless you change it) and, for a choice, the lead over the runner-up reaches its minimum; otherwise review.
  • Yes / no: yes at a probability of 0.75 or more, no at 0.25 or less, review in between.

Review means a person decides. These figures are starting points: tune them against your own examples, and do not carry a bar tuned on a yes/no question over to a choice, because the two are not comparable.

A failure is never treated as an answer. If Jev is switched off, unreachable or refused by the AI budget, each feature falls back to its safe behaviour: a workflow step goes to a person, a message rule does not match, and a bank line gets no Jev suggestion.

Jev or the AI gateway?

Use Jev when the platform needs a decision it will act on: route something, pick a value from a list, flag a record, or hold an action until a probability is high enough. Use the AI gateway when you need text: a summary, a draft reply, extraction into free-text fields or code. Jev is deliberately not one of the gateway's providers, so it never appears in a Send to AI menu or in the list of providers a feature can use.

What leaves your installation

TypeSafe AI is a third-party processor. Whatever a feature puts in front of Jev is sent to TypeSafe, so every use has its own opt-in and sends only what it needs:

  • Workflow steps send only the fields listed on the step. Listing them is the decision.
  • Message rules send message text only from routes whose Allow AI conditions switch is on.
  • Feed Queue suggestions are sent only when the installation and the tenant have both switched them on.

Passwords, encrypted fields and system columns are never sent by any of them. Before you switch on anything that sends personal data, add TypeSafe to your privacy notice and check its terms on retention.

Limits worth knowing

  • Text only. Jev reads text and structured data, not images or files.
  • It reads instructions literally. Put boundary cases in the options, and offer a "none of these" option where nothing may fit.
  • It is unreliable at arithmetic, counting and comparing dates. Do those in a workflow Condition step or a rule, and ask Jev only for the judgement.
  • Less is more. Accuracy falls as unrelated detail grows, so send the fields the question needs and no others.
  • Input can argue its own case. A message may be written to look like something it is not. Keep consequential actions behind a confidence bar, with a person deciding below it.

Worked example

A housing association's repairs team switches Jev on and tries its questions in the playground first. On the repairs text number, an Is about (AI) rule with the statement "The sender is reporting a leak or flooding" routes matching messages to the urgent work queue, with a keyword rule kept alongside it. On new repair requests, a workflow AI decision chooses a trade (plumbing, electrical, joinery or none of these) from the description field alone. Confident answers set the Trade field; everything else goes to the supervisor's queue. The privacy notice names TypeSafe as a processor before either goes live.

Recommendations

  • Try every question in the playground with real, awkward examples before a feature depends on it.
  • Always give review a destination. A person should see what Jev was unsure about.
  • Send the minimum. It is better for accuracy and better for data protection.
  • Record each opt-in: which fields, which routes, which tenants, and who agreed.
  • Pin the model version once you have tuned a bar against it, so a new release cannot move it under you.