Smart Conditions and AI Assignment in There There

A workflow condition you describe in plain language, such as the customer asks for a refund or to cancel a payment. That description becomes a Boolean question in the inbound classification request, and the workflow reads the stored probability as its match score.

The incoming message matches this workflow description, followed by your description, with true and false descriptions explaining what fitting and not fitting look like. The answer is stored on the message so later runs need no new Jev call.

You select the people Jev may choose from and add a short description of what each handles; Jev answers a Choice question with those candidates plus a None of these option. Only a clear favorite results in an assignment; otherwise the action makes no change and another workflow can pick it up.

Disabled members and anyone who cannot access the ticket's channel are removed before the question is asked, and spam and automatic replies are skipped before either the team or person assignment action runs.

In the same inbound classification request as the spam and auto-reply questions. The answer is stored with the message, and the workflow reads its probability from there rather than calling Jev again when the workflow runs.

The editor lets you try a sample email or an existing ticket and see the score before you enable the workflow. Only incoming email is checked; Jev receives the subject, sender, and message text, not the whole ticket history.

It gives no benchmarks, accuracy, or latency numbers for the new features, and it does not describe fallback behavior when probabilities are close. The approach still keeps the final decision in code: the workflow decides what happens next based on the answers.