VOICE
Agents that make the call.
An outbound phone call is a flow step like any other. An agent speaks with your customer over a real phone line, and when it hangs up the flow receives the full transcript and a structured result it can branch on. No call center, no scripts read by humans.
CALLS AS A FLOW NODE
Drop a call into the middle of your automation.
Pick the Voice call node from the flow palette, give it a number, a greeting and instructions, and set the limits: maximum duration, end-call phrases, recording on or off. When the call ends, the transcript and a structured JSON result flow into the next node, so a decision step can branch on what the customer actually said.
{
"interested": true,
"amount_mxn": 12500,
"next_step": "call_next_week"
}The demo above is the real product idiom: call runs, call ends, then the transcript and extraction arrive as flow output.
Explore FlowsREAL NUMBERS
A phone number your operation owns.
Search, provision and release real phone numbers without leaving the product. Regulatory identity requirements (KYC) are a guided workflow in the same admin surface, and carrier events update status automatically.
- +52 55 4821 7736 MX · CDMX active
- +52 81 2044 1190 MX · MTY active
- +1 415 630 2277 US · CA pending KYC
KYC REQUIREMENTS
Number lifecycle and KYC workflows run through the carrier API; webhook events keep status current.
- Provision in minutes
- Search available numbers by country and region, provision, release. All from the admin surface.
- KYC built in
- Regulatory requirement groups, documents and addresses are a guided wizard, not a support ticket.
- Status that updates itself
- Carrier webhooks drive number and KYC status. What you see is what the carrier sees.
A CALL YOU CONTROL
Every call runs inside a box you defined.
A voice call is production workload, so it gets production controls: isolation, an explicit network perimeter, hard limits, and a result your systems can act on.
Isolated per call
Each call runs as its own isolated job, created for the call and destroyed after it. Nothing shared between calls.
Egress allowlist
The call job can reach only the hosts you listed. Everything else on the network is unreachable by policy.
Hard limits
Maximum duration, end-call phrases, inactivity reminders and a goodbye. The agent cannot talk forever.
Recording, your choice
Call recording is a switch, on by default and off when your policy says so.
A structured result
A second model reads the transcript after the call and returns the JSON fields you asked for.
Speaks your language
Realtime voice in Spanish, English, Portuguese, French and German, with configurable voice and turn detection.
WHAT THE FLOW GETS BACK
Not a note. A result.
When the call ends, the flow receives the complete transcript, the duration, how the call ended, and the structured fields you asked for. Downstream nodes branch on data, not on someone’s memory of a conversation.
- The full transcript
- Every turn of the conversation, delivered as a completed artifact the moment the call ends.
- Fields, not vibes
- Interested or not, the amount discussed, the agreed next step: extracted as JSON your flow can branch on.
- Same platform posture
- Calls run on the same tenant-isolated platform as your screens, flows and agents. One place to govern it all.
HEAR IT WORK
Give your flows a voice.
Provision a number, drop the call node into a flow, and let the result drive what happens next. Start free, or bring us your first calling use case.