A support ticket arrives in your flow. Is it a bug, which team owns it, and how urgent is it? AI Decision answers all three in one call, with a probability for each. When the Classifier isn't confident enough, it sends the ticket to review.

Decision models return a typed answer and a probability instead of text. Your flow acts on confident answers and sends the rest to a person.

NEW · AI DECISION

What shipped

  • AI Decision node. Ask yes/no, choice, and score questions about any text or JSON. One call answers all of them and gives a probability for each answer.

  • Classifier with decision models. Describe your categories and pick a decision model. The Classifier returns the category and its confidence. You don't write a prompt.

  • New models. Decision models such as Jev from TypeSafe AI and Decisions from OpenAI are now available in Studio.

AI Decision node in Lamatic Studio

A decision model tells you how sure it is

Chat model

Decision model

Output

Text to parse

Typed answer

Certainty

Unknown

A probability

Set it up in Studio

  1. Add AI Decision or a Classifier from the AI section.

  2. Pick a decision model from OpenAI or TypeSafe.

  3. Write your questions or categories.

  4. For a Classifier, set a minimum confidence and connect the Uncertain path.

Node picker in Lamatic Studio
Classifier setup in Lamatic Studio

How two support tickets move through a flow

Ticket

What the AI decides

What happens next

"Checkout is down. Every sale is blocked."

AI Decision. It's a bug, at 89%. The Payments team owns it. Urgency is high.

Your flow opens a high-priority bug for the Payments team.

"I was charged twice and now I can't sign in."

Classifier. The model leans to Payments over Account, 61% to 39%. Its confidence is below your 80% minimum.

Uncertain path. A person reviews the ticket, so it doesn't reach the wrong team.

Classifier branches, including the Uncertain path

What teams can automate

Team

What the flow decides

What the business gets

Support

Bug, owning team, and urgency

Agents sort only the unclear tickets. The rest arrive prioritized.

Sales

Lead fit, segment, and buying intent

Strong leads go to a rep right away. The rest go to nurture.

Trust & safety

Policy violation and severity

The flow blocks clear violations. A moderator reviews borderline posts.

Finance & ops

Approve, reject, or ask for details

Routine claims close on their own. A person handles the exceptions.

AI agents

Which sub-flow handles the message

Messages reach the right agent. Unclear ones get a follow-up.