---
sidebar_position: 1
title: Visual Call Flow Builder (IVR)
description: Design multi-level IVR menus, business hours schedules, dynamic webhook routing, and queue fallbacks.
---

# Visual Call Flow Builder (IVR)

The **Firetell Call Flow Builder** lets you design inbound call routing visually using drag-and-drop nodes—or manage flows programmatically via the [Call Flows REST API](/developers/rest-api/workspace-api/call-flows).

---

## Core Call Flow Nodes

| Node | Function | Typical Configuration |
| :--- | :--- | :--- |
| **Business Hours Check** | Evaluates caller arrival time against workspace operating hours & holidays. | `Mon–Fri 08:00–18:00` → Main IVR; `After Hours` → Voice AI Agent or Voicemail. |
| **Play Audio / TTS Greeting** | Greets callers using studio recordings (`.mp3`/`.wav`) or neural Text-to-Speech. | `"Thank you for calling Acme Corp. Your call may be recorded for quality assurance."` |
| **IVR Menu (DTMF & Speech)** | Collects keypad digits (`1–9`, `0`, `*`, `#`) or spoken intent to branch call routing. | `Press 1` → Sales Team, `Press 2` → Technical Support, `Press 3` → Billing AI Agent. |
| **Route to Team / Queue** | Places the caller in an agent team queue with custom hold music and max wait time. | Ring `Support Team` (`round_robin`, 45s timeout) → Fallback to overflow queue. |
| **Voice AI Agent** | Connects the caller to an autonomous conversational AI agent with live tool calling. | Answers FAQs, verifies order status, and performs warm transfer to human agents. |
| **HTTP Webhook / CRM Dip** | Queries your CRM before ringing an agent to route VIP callers to dedicated account owners. | `POST https://api.yourcrm.com/firetell/route` with caller E.164 number. |

---

## Best Practices for High-Conversion IVRs

1. **Keep top-level menus concise**: Limit initial IVR options to 3–4 choices (`Sales`, `Support`, `Billing`, `Operator`) so callers reach a resolution in under 15 seconds.
2. **Always configure a timeout & invalid-input fallback**: Route callers to a default receptionist queue or Voice AI agent if no keypad input is detected after 2 retries.
3. **Test before publishing**: Bind a staging DID number to your new Call Flow to test every branch before assigning it to your primary main line.

