Skip to content

The Flow Builder

Describe your process. Watch it become a flow.

Tell the builder how the work runs — who does what, what gets checked, what happens next. It drafts the flow: steps, connectors, assignments. You refine it on the canvas and ship it to the field.

Flow Builder

From words to workflow

Built by conversation. Refined by hand.

No developers, no spec documents. The people who run the operation describe it — the builder does the drawing.

  1. 01

    Describe it

    Say how the process runs, in plain words, in the builder's chat. It drafts the steps, the connections between them and who does what.

  2. 02

    Refine it

    Open the map. Drag, drop, rewire. Add gates, unhappy paths, auto-assignments, commission rules — every block is yours to adjust.

  3. 03

    Change it live

    Ship it to every phone at once. An extra check, a new branch, a reworded question — live in minutes, while the flow keeps running.

The building blocks

Every step is a block. Every answer picks a path.

Chain 10+ block types with if/then connectors. The flow routes each case to its next step — no dispatcher needed.

  • Field task

    A job on a phone: forms, photos, signatures, GPS — works offline.

  • Office to-do

    A review, an approval, a call — queued to the right desk.

  • AI node

    Reads what was submitted and routes the case down the right branch.

    Learn more
  • If/then connector

    Each answer can open a different path — happy, unhappy or edge case.

  • Auto-assignment

    The next step lands with the right person by rule, not by phone call.

  • Commission

    Field pay computed from completed, validated work.

  • Notification

    Emails and alerts fire exactly when a step needs them.

  • Automation

    Steps that run themselves: activate, update, generate.

AI nodes

A decision-maker inside the flow.

An AI node is a step in the flow like any other — except no one has to pick it up. It reads what the field submitted — answers, photos, documents — and decides which branch the case takes next.

That is the difference with a filter that flags a pile for later: the decision happens inside the flow, the moment the data arrives, and execution moves on.

Field submission

AI node

Evaluating…

Pass
Send back
Escalate
  • Pass

    Consistent answers, legible evidence — the case moves straight to the next step. No queue.

  • Send back

    Something missing or contradictory — back to the agent with the exact reason, while they are still on site.

  • Escalate

    A judgment call — routed to a reviewer with the AI's findings attached, not a pile to sort.

You set the autonomy.

Per node, you decide what the AI settles alone and what waits for a sign-off. It is all on the map: every automated decision is a block you placed, with branches you drew. No black box.

tasks & tickets processed
2,000,000+
answers collected in the field
150,000,000+
countries with active field teams
20+

FAQ

Flow Builder, in practice.

Do we need developers to build a flow?

No. You describe the process in the builder's chat and refine the draft with drag and drop. The people who run the operation build it — and change it — themselves.

What exactly does an AI node decide?

Whatever its branches say. It evaluates what the field submitted — answers, photos, documents — and picks the next step: pass it on, send it back or escalate it to a person. You define the branches; it picks one.

Does the AI decide alone?

Where you let it, yes — that is what removes the queue: clean cases move on without waiting for a reviewer. Where you don't, it prepares the decision and a person takes it.

What if the AI isn't sure?

Unsure is a branch. A case the AI cannot settle goes to a person, with everything it found attached. It never guesses silently.

Bring a process. Leave with a flow.

On a call, we map one of your real processes in the builder — steps, branches, AI nodes — and show you what the field sees.