Platform / Workflows

Finish the work, not just the talk.

Visual workflows connect every conversation to your systems, with AI steps, logic and code.

Workflows are the work your Hooman hands off: quick tools it calls in the middle of a conversation, and journeys that carry on for days after it.

4 min
of after-call work saved on every call
Placeholder: replace with a real, approved result

How a workflow works.

A workflow is a set of steps that runs on its own. It starts when something happens, decides what to do, does the work in your systems, and tells your team what it did. Some finish in seconds while your Hooman is still talking; others carry on for days.

Think of the checklist your team follows after every call. A workflow follows it for them, the same way every time, in seconds.

  1. 1

    Something happens

    A call ends, a form is filled in, or a payment is missed. That event starts the workflow.

    Example: Maya's billing call ends.

  2. 2

    It decides

    An AI step reads the conversation or the data, and rules choose the right next step.

    Example: She promised to pay on the 4th.

  3. 3

    It does the work

    It updates your CRM, sends a message or books a call, often several at once.

    Example: CRM updated, reminder set, SMS sent.

  4. 4

    It reports back

    Every step is logged, so your team can see what happened and when.

    Example: Done in 1.2 seconds, visible to the team.

Workflows as tools

Heavy thinking off the call, so the conversation keeps flowing.

A smaller, faster model holds the conversation. When it needs more, it calls a workflow: the workflow works with several systems at once, brings in a larger reasoning model, and returns a short summary. The main model answers from that, so the agent keeps talking and costs stay low.

  • Fast where it mattersThe model on the call stays small and quick, so replies never wait on heavy work.
  • Many systems at onceThe workflow checks your billing, CRM and policies in parallel, not one after another.
  • Big reasoning, only when neededA larger model weighs the results inside the workflow, and only for the moments that need it.
  • A short answer backThe main model gets a concise summary, not raw data, so it can respond in a sentence.
Workflows as journeys

Journeys that follow a customer over days.

  1. Day 1 · 09:00Run startedMissed billBilling webhook
  2. Day 1 · 10:02No answerReminder callCall-back step · Ria
  3. Day 1 · 10:05SentPayment linkSMS · ready-made
  4. Day 1 → Day 3Still unpaidWait 2 daysThen check payment
  5. Day 3 · 10:01Promise to payCallbackRia, with recall
  6. Day 4 · 18:20Run completePaid$86.40 received
  • Logic & timingIf this, then that, after a delay you choose.
  • Call-back stepAny workflow can put a Hooman on the phone.
  • Always-on outreachA new lead gets a call in seconds, automatically.
  • RecallEvery step is remembered, so the next call picks up where the last left off.
See campaigns
Building blocks

Three kinds of step, on one canvas.

Every workflow is built from the same few pieces. The journey above shows them working together, with waits in between.

  • Triggers

    Start from a call, a webhook or a schedule.

    Read about triggers
  • AI steps

    Classify, decide, or clean up data for the next step.

    Read about AI steps
  • Code and actions

    The steps that follow, in parallel when you want.

    See integrations
Build & test

Test every step before it runs for real.

Read about testing

Questions, answered.

Can't find what you need? Talk to our team.