Call flows: IVR, business hours and transfers without a server to run
Describe what happens when a call arrives: hours, menu, transfer, voicemail. Simulate, publish, roll back. Custom quote pricing.
Custom quote
A call flow describes the path of an inbound call: when you answer, which menu you offer, who the call goes to and when it falls back to voicemail. It is what many people call an interactive voice response (IVR).
You build it in a visual editor with blocks you connect. Every flow also exists as readable, versionable text specific to TELQIO. Both views describe the same flow.
Before publishing, you simulate it and the platform validates it. Each publication creates a version in the history, and you can go back to the previous one.
How it flows
Practical uses
Switchboard
Route callers to the right department based on their choice.
Business hours
Switch automatically to voicemail or an on-call number outside working hours.
Link with your system
Query your API during a call to decide on the transfer, or notify your team.
One version per site
Duplicate a flow for each branch and change only the transfer numbers.
Features
- Blocks: inbound call, hours, menu, condition, transfer, voicemail, HTTP request, notification
- Visual editor and equivalent text version
- Simulation before publishing
- Validation of missing links and loops
- Version history and rollback
- A flow attachable to one or more numbers
Limits to know
- Which blocks and DTMF inputs are available depends on the selected provider and the country.
- Simulation checks the flow logic. It does not guarantee each carrier's behavior or audio quality.
- An HTTP request block depends on the availability and response time of your own server.
- A rollback restores the previous version for upcoming calls. It does not change calls already in progress.
flow "branch-reception" version 3
when inbound_call on +33199001234
hours mon-fri 09:00-18:00 zone Europe/Paris
then menu "Press 1 for sales, 2 for support"
key 1 -> transfer +33199001235 timeout 20s else voicemail
key 2 -> transfer +33199001236 timeout 20s else voicemail
no input -> voicemail
else say "We are closed" then voicemail
on call_end -> notify https://example.test/hooks/callsTechnical details
| Representations | Visual editor and equivalent text version |
|---|---|
| Lifecycle | Simulation, validation, publishing, history, rollback |
| Integration | HTTP request block and signed webhook notifications |
| Attachment | Flow tied to a number, or used through flow_id in POST /calls |
Frequently asked questions
Can I write flows without the visual editor?
Yes. Every flow has an equivalent text version that you can read, compare and keep in your own repository.
What if a publication causes a problem?
Go back to the previous version from the history. It applies to the next calls.
Can a flow call my application?
Yes, with the HTTP request block. Your response decides what happens next. Plan a fallback branch in case your server does not answer.
Related use cases
Documentation
Related services
Let's design your call journey
Describe your hours, services and transfer rules. We will prepare a quote and a first flow outline.