Your call scenario, built
by connecting blocks.
Conversation, conditions, transfers. Arrange the blocks you need, connect them, and the scenario is done. Say "add a branch for cancellations" and the AI restructures it for you. Not one line of code.
Asks for the preferred date, time, and booking details
Routes based on whether the booking is available
YesNoEnds the conversation
Add to calendarCreates a Google Calendar event from the call
Add to calendarCreates a Google Calendar event from the call
Add to calendar
Post to Slack
Add to SheetsSound familiar?
Phone configuration too complex to touch
Every scenario change means calling a vendor
The more branches you add, the less you see
The blocks you build with
Speak, branch, connect, record. Eleven block types, arranged and connected, are the whole flow.
Shape the conversation
What the agent says, what it captures, and where the path splits. These blocks are the substance of the call.
Conversation
Set what the agent says and what it needs to capture — dates, party size, names, contact details — all within the conversation.
Conditional branch
Send the call down a different path based on what was captured, so each type of request gets its own handling.
Time-of-day branch
Inside opening hours or outside them, weekday or weekend — switch the response on time alone.
Keypad branch
"Press 1 for…" — route by DTMF tones, exactly the way a traditional voice menu works.
Message playback
Read out a fixed announcement, such as your opening hours or a holiday closure.
Hand off or finish
After the AI has answered, pass the call to a person or close it out. These decide how the call ends.
Transfer and hand off
Send the call to a person or another desk, carrying everything captured so far across with it.
End the call
Close the call once the request is handled, so no path is left hanging.
Record and notify
Push what the call produced into your internal tools and outside systems.
Send SMS
Text the caller during or after the call — a booking confirmation, a link, directions.
Send email
Email what was captured, either to your team or back to the caller as confirmation.
Webhook
Post the call's details to any URL and hand them straight to your own systems.
HTTP request
Call an external API and use what comes back in the conversation — stock levels, availability, anything.
Tell the AI what to change
Rearrange the blocks yourself, or just say what you want. The AI reads your intent, restructures the flow, and shows you the result.
"Add cancellations."
"After 8pm, take a message instead."
"Post what we captured to Slack."
Quick to build. Quicker to change.
Just arrange and connect
Conversation, conditions, time-of-day branches, keypad menus, transfers. Pick the blocks you need and draw the lines between them.
Tell the AI what to change
Say "add a branch for cancellations" and the AI reads your intent, restructures the flow, and shows you the result.
Reaches your other tools
SMS, email, webhook, and HTTP request blocks push what happened on the call straight into the systems you already run.
See where calls drop off
Analytics show which block each call ended on, so you can find the sticking point and fix that part of the flow.
Three steps to set up
No complex configuration. Set it up without code and go live the same day.
- STEP 1
Start from a template
Choose the template for your industry and begin with a working flow already in place.
- STEP 2
Add and connect blocks
Set what to ask, how conditions branch, and where calls transfer. Drag, connect, done.
- STEP 3
Test it, then publish
Call in and hear it for yourself. Save, and the new flow is live on your line.
Who it's for
- Teams that want phone automation without code
- Anyone who keeps iterating on call scenarios
- Businesses routing calls by type of request
- Companies stuck with a complex voice menu
- Teams pushing call data into internal tools
How teams use it
Route requests to the right desk
Combine keypad menus with conditional branches to send each caller to the right team, so people focus on the hard cases.
Capture viewing requests
A conversation block gathers requirements and contact details, then posts to Slack. First-line response, handled by the flow.
Building a flow
is just connecting blocks.
No code, live the same day. Start on the free plan and build your call flow however you like.