Capture

Decision Tree

Turn complex procedures into step-by-step paths anyone can follow. Decision trees walk support and service teams through a ticket one question at a time, built in a visual, drag-and-drop editor with images, video and rich content in every step.

Request demo Explore platform

Made for support teams

Step-by-step resolution for every ticket. The same expert path, every time.

Decision trees shine in customer support and service. Instead of handing an advisor a long article, they guide them through a ticket one step at a time, so every agent follows the same expert route, cases get solved faster, and the answer stays consistent no matter who picks it up.

A pleasure to build

Drag, drop and connect the nodes. A complete WYSIWYG editor.

Building a tree is genuinely nice. Drag blocks onto the canvas, connect nodes to map every branch, and watch the whole flow take shape as you go. It's a full visual WYSIWYG editor, no diagramming tool or developer needed.

Rich, easy to follow

Put anything in a step. Images, video, any block.

Every step is the full editor inside, so you can drop in images, video, callouts: any block you'd use in an article. The result is a procedure people can actually follow, not a wall of text.

A governed article underneath

Everything an article has, a tree has too. Approval, expiration, permissions, search.

A decision tree is not a separate tool on the side. It lives in a space like any article: send it through approval, set an expiration date, control who sees it, and find it in search. Your guided paths follow the same governance as the rest of your knowledge.

FAQ

Common questions about decision trees

It’s an article presented as an interactive, step-by-step journey: readers answer questions or pick options and are guided straight to the answer that fits their case. It’s built for diagnostics, guides and support, so the same expert path is followed every time.

A standard article gives everyone the same text; a decision tree adapts to the reader’s situation and routes them to the right outcome, cutting resolution time for users and agents alike. It can also act as an orchestrator, linking to existing articles rather than duplicating them.

Yes. Each step works like a mini article and can hold any block a normal article supports: lists, links, files and rich media. You build the tree visually by adding and connecting nodes, and the branch titles become the buttons your readers click.

A tree behaves like any other article: it lives in a space, follows the same access rights, and can be put through approval or given an expiration date. It’s also fully searchable, so readers find it just like any other content.

No. Trees are created from the standard content menu and built in a visual editor where you click to add steps and drag to connect them. You can preview the whole journey as an end user before publishing.

Turn your best expert's reasoning into a path anyone can follow.

See it on your own knowledge.

See how decision trees give every team (and every AI agent) the same answer to the same case.