Build an IVR flow
A flow is the script your callers walk through — greeting, menu, branches, routing. You build it on a visual canvas by dragging node types from the palette and connecting them.
Before you start
- At least one phone number provisioned in Settings → Voice.
- (Recommended) A queue and a team ready to receive calls — your first flow will likely end at Send to Queue.
- A rough sketch of what the call should sound like — what greeting plays, what menu options exist, where each one goes.
Steps
- Open Settings → Voice.
- Select a phone number in the sidebar.
- Click Create Voice Flow, then click Build Your Flow on the Flow tab. The builder opens with an Incoming Call node already placed.
- Drag a node from the left palette onto the canvas — start with a Say Message node next to Incoming Call.
- Click and drag from the bottom handle of Incoming Call to the top handle of Say Message to connect them.
- Click the Say Message node to open its configuration in the right panel. Enter the greeting text — for example, “Thank you for calling Acme. We’re connecting you now.”
- Keep adding and connecting nodes until the flow describes the full call experience. Configure each node with the caller-facing wording it needs: for Gather Input, set the prompt, Try again message, and Wrong key message; for Language Selection, set the prompt, retry message, and invalid-key wording for each language callers can choose. A simple starter flow:
Incoming Call → Say Message ("Welcome") → Send to Queue (Support)
- To set the languages and voices the flow uses, click Languages & voices in the builder. See Set languages and voices below.
- To keep work in progress, click Save draft. A draft is saved even when the flow has validation errors, and callers keep hearing the published flow until you publish.
- When you’re ready to go live, click Save & Publish. Publishing writes the definition callers can hear, so Atender refuses any definition that cannot safely go live. If validation passes, the flow is published; if it fails, the validation panel at the bottom of the canvas lists what’s wrong.
Set languages and voices
The Languages & voices button in the builder opens a pane where you manage the flow’s languages and the voice each one uses. The first language in the list is the Main language, which callers hear before they make a language selection.
Changes you make in the pane are drafted. They don’t affect callers until you click Save & Publish.
To get the flow’s voice-over script, click Export script in the pane. Export script works whether or not the flow is assigned to a phone number.
Keep unfinished work
You don’t need to finish a flow in one sitting. Save draft stores your changes without publishing them and is not blocked by validation errors.
- Leave prompt. If you try to leave the builder with unsaved changes, Atender asks what to do: Go back to keep editing, Continue without saving to leave and lose the unsaved changes, or Save draft and continue to store a draft and then leave.
- Unpublished draft badge. When a draft exists, the Unpublished draft badge appears. Callers still hear the published flow until you publish the draft.
- Discard draft. Click Discard draft to throw away your draft changes. The builder returns to the published flow.
Use a placeholder prompt while you write the real one
If you need to write a prompt in the Voices tab but the flow still contains placeholder text:
- Save a draft in the builder.
- Open Voices and write the prompt. This edits the draft.
- Return to the builder and click Save & Publish.
If you restore an earlier version of the flow, the restored version goes live at once and discards any draft.
Common starter patterns
A few flow shapes that cover most needs:
- Direct-to-queue. Incoming Call → Say Message → Send to Queue. The simplest possible flow.
- Open/closed branch. Incoming Call → Is Open → (Open) Send to Queue / (Closed) Say Message → Voicemail. Honors your opening hours.
- Menu. Incoming Call → Say Message (“Press 1 for sales, 2 for support”) → Gather Input → (1) Send to Queue (Sales) / (2) Send to Queue (Support).
- Callback offer. Incoming Call → Say Message → Callback Queue. Skip the hold-time waiting altogether.
Verify it worked
After publishing, you should see:
- The flow appears in the Flow tab with its name and a status.
- The Unpublished draft badge is gone.
- The validation panel at the bottom of the canvas shows no errors. When nothing needs attention it reads Flow is valid; if it also lists warnings or notes, those are for your review and don’t mean the publish failed.
Assign the flow to a phone number, then dial that number from your own phone. The call should reach the queue or voicemail you designed.
Validation errors and how to fix them
Save & Publish writes the definition callers can hear, so the builder blocks publishing on a validation error. Save draft is not blocked by these errors. Warnings are listed in the same panel but do not block publishing:
- (Warning) A node is not connected to the flow at all — connect it from a previous node.
- (Warning) A node has an incoming connection but no outgoing one, and is not a terminal node — connect its output to the next step.
- A Gather Input node has no branches — add at least one key branch and connect it to the next step callers should reach.
- A Language Selection key offered to callers has no matching branch — add and connect the branch for every language key in the prompt.
- A Send to Queue node references a queue that no longer exists — pick a different queue or recreate the missing one.
- A reachable prompt still uses palette template text — replace it with the real caller-facing prompt or upload a recording. Save & Publish stays disabled until every reachable Gather Input placeholder prompt is replaced; the same template text on a reachable Say Message or Returning Customer node is only a warning. Draft nodes that are orphaned or unreachable are ignored by this placeholder check.
- The flow has no terminal — every path must eventually reach Hang Up, Voicemail, or a routing exit like Send to Queue or Transfer.
Other items the panel lists
The validation panel also lists these warnings and notes:
- Missing wait messages.
- Missing or out-of-date translations.
- Corrected translations for you to check.
- Notes on built-in messages.
These entries are for your review and don’t block publishing. Click an entry to open the step it refers to.
Troubleshooting
-
Symptom: The flow saves, but calls land in a fallback message instead of running the flow. Fix: The flow isn’t assigned to the phone number yet. See Assign an IVR flow to a number.
-
Symptom: Your TTS message sounds wrong (wrong language, robotic voice). Fix: Click Languages & voices in the builder and check the flow’s voice and language configuration first. The first language in the list is the Main language, used before callers make a language selection. If the flow has no configured languages, add one there. See Configure TTS voices for the full resolution order.
-
Symptom: Send to Queue dropdown is empty. Fix: You need to create a queue first. See Set up a call queue.