Home Platform Workflow Builder

Workflow Builder

Every node tells you exactly what it will do

Most builders give you a box with a label. Ours shows the input, the rule, the action, the success path, the failure path, the human fallback, what the caller hears, what gets written and the audit event it fires.

See pricing

18Node types

9Fields per node

2Paths, always

Inside a node

Nine fields, every time

No black boxes

Open any node and you can see precisely what it does and what happens when it fails. That is the difference between automation you trust and automation you hope about.

Because both paths are always defined, there is no such thing as a call that quietly goes nowhere.

Node, create booking

InputSelected slot, service, customer

Decision ruleSlot still free and within lead time

ActionWrite appointment to calendar

Success pathSend confirmation, draft work order

Failure pathOffer next two slots, retry once

Human fallbackTransfer to reception

Data writtenCase, booking, customer record

Node types

Eighteen blocks, one canvas

Incoming call

The trigger. Channel, number, time and caller history all available downstream.

Identify intent

Works out what the caller wants, with a clarify path when it is unclear.

Ask a question

A single question with a defined answer shape and a retry limit.

Collect information

Gathers a defined set of fields and refuses to move on while one is missing.

Validate

Checks format and plausibility before anything is written.

Search knowledge

Answers from approved sources, with an explicit not-found path.

Check availability

Live lookup against the resource the job actually needs.

Request approval

Holds the action at awaiting approval until a human clears it.

Transfer or escalate

Warm transfer with full context, or break the flow and page on-call.

Questions

Worth asking before you buy

How long does a workflow take to build?

You start from your industry template rather than a blank canvas, so most people are adjusting rather than building. A first workflow is usually an afternoon.

What if I get a workflow wrong?

Test it in the studio before it goes live, and every version is kept so you can roll back. Changes never apply to a call already in progress.

Can two workflows run on one number?

Yes. The intent node routes to the right workflow, so bookings and complaints can follow completely different paths.

Is there a limit on workflow size?

Not a practical one, but a workflow you cannot explain out loud is usually a sign it should be split in two.

Can I see which node a live call is on?

Yes, in the operations view, which is the fastest way to understand why a particular call is taking longer than it should.

Map your first workflow with us

Bring your most common call. We will build the flow for it while you watch.

Book a walkthrough

Product

Solutions

Company