Draw the path of a call,
instead of describing it.
Drop blocks, connect them, publish. The greeting, the hours rule, the keypad menu, who rings and for how long, where the call goes if nobody answers: all of it visible at once, on one screen.
What actually happens when it rings.
The flow in the editor above, followed block by block, on a real call.
The call lands
It is 7:12 on a Tuesday. Someone dials Plomberie Roy. This number's flow takes over: not the generic voice menu, not the team forwarding, this one.
The greeting
“Plomberie Roy, hello.” Read by a synthetic voice, or by your own recording if you uploaded one. The caller knows they are in the right place.
Open or closed?
The block checks the schedule: Monday to Friday, 7 to 5. Tuesday at 7:12 means open. A declared holiday would have switched to the closed branch without you touching anything.
One key, one branch
“Press 1 for an emergency, 2 for an appointment.” The caller presses 1. Had they pressed nothing, a separate exit would have taken over instead of leaving them hanging.
Marc's phone rings
Marc's mobile rings for 25 seconds, the delay you set. He is under a sink. Nobody picks up, and the flow already knows where to go next.
The message, transcribed
The caller leaves a message. Marc gets it as text, reads the address without replaying thirty seconds of audio, and calls back from the same business number.
No card. Flow unlocks on Business and Scale.
A broken flow does not publish.
You edit a draft, never the live flow. As long as a block has no continuation, a menu has no exit, or an hours rule has no day, a counter flags it and Publish stays grey.
Here, the block that rings Marc has nothing planned if nobody answers. The engine would hang up on the caller. The editor sees it before the caller hears it.
One flow per number
Each number has its own path, as a tree. A block never has two parents, a branch never loops back. What you can read, you can understand.
The whole organisation
A dial block rings a member, an outside number, or the browser app of any team in your organisation, not just yours.
Telnyx and Twilio alike
The engine is wired into inbound calls on both providers. The flow belongs to your organisation, not the provider: switching does not make you start over.
No queue with hold music, no rule based on the caller's number, no simulator to test a path before publishing, and no voice picker with preview. There is no AI receptionist block either: the receptionist and Flow are mutually exclusive today, and we will not wire it in until it has held a real conversation. These gaps are real, and we would rather name them than let you find them.
The same number, the same history, on three screens.
To go further: all the features, the free tools to try before creating an account, outbound calling with outbound calls, cost tracking for leadership, or who builds Relay.