Workflows

Start from anything. Finish the job.

A Voice OS agent is not a phone line that waits to ring. Your systems start it, it holds the conversation on whichever channel fits, and it does the work that follows — the booking, the message, the CRM update — then tells you what happened.

Book a demo See example workflows

1 · Triggers

What starts the agent

Every trigger carries its context with it — who the person is, why you are reaching them — so the agent opens the conversation already knowing.

A webhook from any system

Your CRM, website form, booking engine or backend posts to the agent's trigger URL, with whatever fields you want it to know.

A campaign list

Import a list and the agent works through it inside your calling hours, at a pace your lines can carry.

A schedule

Run on a clock — this morning's reminders, today's follow-ups, the weekly check-in.

An inbound call

Someone rings your number and the agent picks up, looks them up, and knows them if they have called before.

A WhatsApp message

A customer messages your WhatsApp Business number and the same agent answers in the chat.

A person pressing Run

Start any agent by hand from the console, or from your own code with the API.

2 · The conversation

Draw the flow, or just describe it.

Write the agent's job in plain words and it follows them — or lay the conversation out step by step on the canvas when the order matters.

Start — greet, wait, or look the person up in your own API before saying a word.
Agent steps — each with its own instructions, tools and documents, and fields to capture as it goes.
Branches — move to the next step on what the person actually said.
Webhook steps — call your system mid-conversation and use the answer.
End or transfer — hang up cleanly, or hand the call to a person.
Quality check — score the conversation against your criteria when it ends.

Call flow · Lead qualification

New lead→ Start · look up in CRM

→ Agent · qualify→ Agent · book demo

→ Webhook · update deal→ Transfer if hot

→ Quality check

3 · Actions

It does the work that follows the conversation.

The agent acts while it is still talking — so "I'll send that over" is sent before the call ends, not added to somebody's list.

Book and reschedule

Offer free slots, book, move and cancel — mirrored to Google Calendar with a meeting link, or through Calendly and Cal.com.

Message on WhatsApp

Send the confirmation, the link or the reminder — now, or at the time the person asked for.

Text by SMS

Send a text through the Twilio account you connect, from your own sender.

Follow up by email

Send the brochure, the quote or the summary from Gmail, Outlook or Resend — your address, your reputation.

Update the CRM

Write the lead, the deal stage and what was said into HubSpot, Salesforce, Attio or Close.

Open a ticket

Create or update it in Freshdesk or Intercom when something needs a person.

Tell the team

Post the hot lead or the complaint to Slack or Microsoft Teams as it happens.

Schedule the callback

"Call me after six" becomes a call at six, with the context of the first one carried forward.

Call your own API

Check stock, look up an order, create a booking in your system — anything with an endpoint.

Example workflows

What a complete run looks like.

Each of these is built from the triggers, steps and actions above — no custom code.

Speed to lead

A form fill becomes a qualified, booked conversation before the lead has closed the tab.

Website form→ Call in minutes→ Qualify→ Book demo→ WhatsApp confirmation→ Update HubSpot

No-show prevention

Everyone booked for tomorrow gets a call; anyone who can't make it is rebooked on the spot and sent the new time.

Every evening→ Call tomorrow's bookings→ Confirm or move the slot→ WhatsApp the new time

Outbound campaign

A list worked inside calling hours, with the interested ones followed up the way they asked.

Campaign list→ Call→ Record interest→ Email the details→ Callback when asked

Never miss a call

Every caller gets an answer at any hour, and your team gets only the ones that need a person.

Inbound call→ Answer from knowledge base→ Transfer if needed→ Freshdesk ticket→ SMS summary

WhatsApp to booking

A question on WhatsApp ends as a confirmed appointment, without anyone on your side touching it.

WhatsApp message→ Recognise the customer→ Book through Cal.com or Calendly→ Post to Slack

4 · Results

Every run reports back.

When a conversation ends, your systems hear about it and your team can see it — no guessing what the agent did.

Signed webhooks — call.completed and conversation.completed, with the transcript, the outcome, the fields captured and every action taken.
Outcome on every call — interested, not interested, callback, voicemail — and the actions taken.
Dashboards per use case — the diary, the pipeline, what came in this week.

call.completed · what your system receives

{
  "event": "call.completed",
  "data": {
    "disposition": "interested",
    "summary": "Wants the team plan…",
    "variables": { "budget": "4000" },
    "tool_calls": [{ "tool": "book_appointment", "ok": true }],
    "quality_score": 86,
    "recording_url": "https://…"
  }
}

Tell us what should start your agent.

We will map your first workflow with you — the trigger, the conversation and everything that should happen after it.

Book a demo See the channels