Skip to content
Adoptiv
Call flows

Draw what happens when the phone rings.

A call flow is the path a call takes, drawn on a canvas rather than configured in a form. 37 nodes cover screening, greetings, menus, capturing what the caller keys in, calling your own systems mid-call, and getting the caller to the right person. Publish it, point a number at it, and test the whole path before a customer does.

37 nodes · 8 categories · 6 worked examples

Try it

Pick a flow. Run the call. Click any node.

These are the six real flows, drawn from the same data the pages below use. Every node is one you can drag onto a canvas, and every description is the one the builder shows.

  1. 01
    Screen before anything elseFederal DNC Check

    Nothing is dialled until the registers have been checked. Put this first so a suppressed number never reaches the rest of the flow, rather than screening after the greeting.

  2. 02
    Only call inside permitted hoursBusiness Hours

    Evaluated in your own timezone. Outside the window the call does not proceed, which is a rule you can evidence rather than a habit you rely on.

  3. 03
    Confirm this is somebody you holdIf Existing Lead

    If the number does not match a record, there is no balance to quote and the flow should not pretend otherwise.

  4. 04
    Fetch the live balanceTrigger Webhook

    Calls your ledger with the contact id and captures what comes back into flow variables: the amount outstanding and the due date. Five second timeout, with a failure branch, because a ledger that is down should not produce a call that quotes nothing.

  5. 05
    Say the amount out loudPlayback Audio

    Spoken through your Brand Voice Kit with the captured variables interpolated. The caller hears the real figure and the real date, not a generic message asking them to call back.

  6. 06
    Ask the question that sorts the listRoute to IVR

    Paying today, arranging terms, or disputing. One keypress, three branches, and the branch is the only thing that decides whether this call needs a person.

  7. 07
    Take the reference numberCapture Digits

    On the paying-today branch. The caller keys in the account or reference number from their statement and it lands in a variable you named.

  8. 08
    Post the promise to payTrigger Webhook

    Sends the captured reference and the amount to your payment provider or ledger. Whatever it returns is captured for the next step.

  9. 09
    Branch on what the processor saidMatch Webhook Variable

    Accepted, declined or unavailable are three different conversations. Only one of them needs an agent.

  10. 10
    Record the outcome on the recordUpdate Lead Stage

    The stage moves without anybody typing. This is the step that stops the same person being called again on Thursday.

  11. 11
    Hand over the ones that need a personRoute to Team

    Disputes and arrangements go to the team that handles them, with the record already open and the balance already on screen.

Step 1 of 11

Screen before anything else

Nothing is dialled until the registers have been checked. Put this first so a suppressed number never reaches the rest of the flow, rather than screening after the greeting.

The node

Federal DNC Check

Checks the caller against the US national Do-Not-Call registry and branches.

ListedClean
Worked examples

Six flows, built node by node.

Each one names the exact nodes at every step, so you can read it as an explanation or follow it as a recipe.

Node reference

Every node, and what comes out of it.

Written by the people who built the nodes: this reference is generated from the same catalog the builder reads, so it cannot describe a node differently from the thing on your screen.

Book a demo

Bring the flow you cannot build today.

Half an hour, your own numbers. We build the awkward one live rather than showing you the easy one on a slide.

14-day trial · no card · migration included