Build it in the number’s call flow (Numbers > your number > Edit): a Time Rule for opening hours, an IVR widget on the open branch with a Ring to and a Voicemail behind each option, and the AI Voice Agent widget on the At any other time branch. Publish, then call every path from an outside phone.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowTwo naming points save time. Aircall’s current help pages call the routing tool a call flow and the menu step the IVR widget; older articles and links still say Smartflows, and the widget list has nothing called Keypad. The separate Input IVR widget collects digits such as an order number and cannot route a call on its own.
How do you plan an Aircall IVR menu?
Plan an Aircall IVR menu around the reasons people ring, named in the caller's words rather than your department names, and give every path a destination, including silence, a wrong key and a team that does not answer.
Start with the reasons people ring, not your department names. An IT support firm might need two choices during opening hours: help with an existing service, and a new-service enquiry. The caller does not need to know who manages accounts internally; use the words they would use when something is broken.
Write a destination for every path, including silence, a wrong key and a team that does not answer. These paths matter as much as the advertised options, because an unfinished branch is where callers get cut off while the main routes look tidy.
Here is the main worked example, used through the rest of the tutorial. A three-person IT support firm staffs its phones from 9 am to 5:30 pm on weekdays. Option 1 reaches the support team and option 2 reaches sales. A third, unannounced option is kept for testing the AI agent with real calls. Outside staffed hours, the AI Voice Agent answers approved questions and collects callback requests; it never promises an engineer.
Date Rule (special dates)
Special date ............ Voicemail: holiday greeting
Business As Usual ....... Time Rule (team's own timezone)
Mon-Fri 9:00 am-5:30 pm ... IVR "Existing service or new service"
1 ...................... Ring to: Support team (45 s) -> Voicemail: support
2 ...................... Ring to: Sales team (45 s) -> Voicemail: sales
9 (not announced) ...... AI Voice Agent: daytime test -> transfer -> Ring to -> Voicemail
No or wrong input ...... Voicemail: general
At any other time ......... AI Voice Agent: after hours (transfers off)
Keep the menu to one level at first. Aircall can nest menus, but every extra level is more wording to maintain and more paths to test. For choosing the agent’s first job, see the tutorial on choosing the first Aircall AI job.
Where does the opening-hours schedule go in an Aircall call flow?
The Time Rule goes before the IVR widget, so the opening-hours menu sits on its staffed branch and the AI Voice Agent on its At any other time branch; only a Date Rule for closures, if you use one, comes earlier.
- In the Aircall Dashboard, open Numbers > All numbers, select the line and confirm it is the one you mean to change.
- Open the Call flow tab and click Edit to reach the Flow editor. On a number’s first edit you can Use a template, Import an existing configuration or Start from scratch; the IVR Call routing template builds a multi-branch menu and the Business Hours template a Time Rule with Ring to and Voicemail.
- Note the current routes before changing anything. Applying a template to an existing flow overwrites it, and the only way back is to discard your changes before you publish.
- Add or open the Time Rule widget, give it a title and set the timezone of the team that answers, not the timezone suggested by the number’s prefix.
- Name the staffed branch and enter its days and hours. You can type exact times and add several time slots to one branch.
- Put the IVR widget on the staffed branch and give At any other time an explicit step. Aircall’s routing guide says an empty At any other time branch does not block calls; it drops them.
Aircall’s routing guide calls the wrong timezone the most common cause of calls routing at the wrong hours, and adds a second trap: gaps between time slots. A slot ending at 5:00 pm and another starting at 5:30 pm leaves half an hour where calls fall into At any other time. The Time Rule documentation also notes that numbers migrated from the older routing may still show labels such as Open or Always Closed, which do not affect the hours you set.
Use telephone hours, not office hours. A wedding planner might hold appointments from 9:30 am to 4:30 pm but have someone on the phones only until 3:00 pm on Thursdays. Its Time Rule needs a Thursday slot ending at 3:00 pm; a menu promising a live coordinator until 4:30 pm would be wrong even though someone is in the office preparing documents.
Be explicit about breaks. If phones are covered through lunch, do not add a closed slot just because the office breaks. If nobody covers a 30-minute window, route it deliberately and say honestly when calls will be returned.
How do you write an Aircall IVR menu message?
Write the IVR message as one short sentence per option in the caller's words, end by saying what happens if they press nothing, and promise a person only where that route exists.
Aircall’s IVR widget reference describes the settings. Add an option by hovering between existing branches and clicking +. The Message setting plays an uploaded file, text-to-speech or a recording made in the widget; each branch gets a title, a keypad number and its own routing. After the message ends, callers have three seconds to press a key before the system treats it as no input.
The support firm’s wording: “For help with an existing service, press 1. For a new-service enquiry, press 2. If you are not sure, stay on the line to leave a message.” The last sentence must match the no-input path you build, and no line should promise a person unless that route exists. Listen to it on a real phone; text that looks short on screen can be hard to follow when spoken, and text-to-speech may mangle product codes.
For no input and wrong input, you can repeat the message, set how many times it repeats and play a custom message after repeated invalid input. Aircall flags an error if no Audio or Voicemail widget is connected to the No or Wrong Input leg, so give it a short message-taking route rather than an endless loop.
A print shop shows why menus should follow the caller’s reason. Its first draft says “Press 1 for pre-press, 2 for production, 3 for finishing.” Callers mostly want a quote or an order update and cannot tell which department that is. The rewrite, “Press 1 for a new quote, press 2 about an existing order”, is tested on a colleague who has never seen the internal structure.
Keep a register of key, spoken wording, branch title and destination. When a team is renamed, the register shows which greeting must change too. A stale greeting is a defect even when calls still connect.
What happens when nobody answers an Aircall IVR option?
If no step follows the Ring to and the user or team is unavailable, Aircall says the call rings once and drops, so put a Voicemail widget or a second Ring to after every option, and give no input and wrong keys a message-taking route.
Each live option needs a Ring to step pointing at a user or a team; type at least three letters to find them. For a team you set Ring for (between 5 and 3,600 seconds), a ringing rule (Simultaneous, Randomly or Longest idle time) and whether to Wait for busy agents. Aircall’s Ring to guide adds that iOS app users can be rung for at most one minute, whatever the setting, so keep ring times realistic for iPhone users.
Then add what happens when nobody answers. Aircall says that if nothing follows a Ring to step and the user or team is unavailable, the call rings once and drops. Put a Voicemail widget, or a second Ring to as overflow, after every Ring to. Its greeting should say the team is busy, not that the business is closed.
If calls still do not reach people during open hours, Aircall’s routing guide gives the checks in order: the Time Rule is sending calls to the staffed branch at that hour, agents are assigned to the number under its Teams & Users section, they are set to Available in Aircall Workspace, and the Ring to points at the right team.
A booking coordinator tests the wrong-key path by pressing 7 on a two-option menu. The menu repeats as configured, then the call reaches the message-taking route; she leaves reference 418 and checks a colleague can retrieve it. A pleasant retry message alone proves nothing about whether the request can be recovered.
The Flow editor shows a yellow exclamation mark for warnings and a red cross for errors beside Publish. Errors block publishing; warnings do not, so a successful Publish is not proof that every path is finished. The common warning “Branch without steps” means a branch, often No or wrong input or At any other time, has no widget and callers routed there hear nothing.
How do you set up an Aircall AI Voice Agent for after hours?
Create an Inbound AI Voice Agent with call transfers switched off, a knowledge base of short approved answers and a few intake questions for callback details, so it answers only what you have approved.
Create the agent under AI Agents > AI Voice Agents > Create an AI Voice Agent, choosing Inbound. Configure the Agent profile, Company information and Call script (greeting and farewell), and switch off Call transfer rules, as Aircall’s after-hours guide recommends, because nobody is there to take a transfer.
Fill the knowledge base with short, approved answers to the questions people actually ask after hours. For the support firm: what to have ready for a support call, how routine requests are handled and the staffed hours. Aircall advises keeping it to your most frequent questions, since overloading it slows responses and reduces accuracy. Leave out passwords, customer records and troubleshooting advice you have not approved.
Conversational guidelines set the if/then behaviour. By default the agent does not answer outside its knowledge; add what it says next. An adapted version of Aircall’s template:
## Outside what I know
- If the caller asks something not covered by the knowledge base, say:
"Sorry, I can't answer that one, but the support team can."
- Ask: "Would you like a member of the team to call you back
during opening hours?"
- If YES, go straight to the intake questions.
- If NO, thank them, give the opening hours and end the call politely.
- Never say a change has been made to an account.
Intake questions collect what the team needs to call back; Aircall suggests three to five, and the answers are saved to the call notes and logged in any connected integration. For the support firm: name, callback number, a short description of the problem and the best time for a call. A preferred time is a request, not a booked appointment.
Mind the lifecycle. Save stores a draft; Activate agent connects a new agent to a number; on a live agent, edits wait as unpublished changes until you click Publish changes. Knowledge base edits are the exception and apply automatically once processed, so treat them as live the moment you save them.
Add a daytime hand-off from the menu to the AI and back
The title’s hand-off can also run the other way: the AI answers first and passes callers to people. In the agent’s Call transfer rules, turn on Allow AI Voice Agent to escalate the call and pick a transfer setting: Immediate, Help first (the agent tries the knowledge base and transfers only if the caller insists or it cannot help) or After intake questions (it asks every intake question first, so the person picking up has the context).
Aircall says a transfer is triggered when the caller asks for a person, when the agent detects frustration, or when intake is complete and more help is needed. Two setup rules come from its configuration guide: the call flow must have a routing step placed immediately after the AI Voice Agent widget, and transfer branches, such as Support and Sales, each become a path in the flow, with a Fallback branch included by default for anything that matches neither. Transfer branches are not available if one agent serves several numbers, so give each number its own agent.
For the support firm, the daytime agent sits on the unannounced option 9 during testing, set to After intake questions with two branches. Support goes to Ring to: Support team for 45 seconds, then Voicemail; Sales goes to Ring to: Sales team, then Voicemail; Fallback goes to the general voicemail. Aircall counts an escalated call that no person answers as a missed call, so the voicemail behind each Ring to is what stops a handed-off caller from being dropped.
Test the conversation before connecting it to callers
The Test call panel on the right of the agent editor runs a mock conversation without sending call activity to your team or actions to your CRM. Aircall’s configuration guide lists what it cannot test: real inbound call flows, real transfers to a person, and intake logging to integrations. Test calls are free while trial minutes last, then billed at the usual per-minute rate.
Run Aircall’s three scenarios. The happy path: a question it should answer, then one it should not, followed by a successful callback request. The fuzzy path: a vague question, to see whether it asks for clarification. The unhappy path: interrupt it, contradict yourself and ask it to do something outside its role.
A print quote request shows what to listen for: “I need 200 copies, actually 250, and I don’t have final artwork.” The useful capture is “250 copies; artwork not ready; quote needs review”. An agent that records both quantities without noting the correction has created work. A bookkeeping caller who says “please change the bank details on my account” must hear a polite refusal and an offer of a callback, never a confirmation.
Then test with real calls on the hidden option 9, the internal-setup approach Aircall suggests for testing real call flows, intake logging and live transfers. Keep a list of phrases that failed and the guideline you changed, so the next person knows why each rule exists.
Does Aircall fall back to voicemail if the AI Voice Agent cannot help?
Aircall's guides describe no automatic fall back to voicemail when the AI Voice Agent cannot help, and adding the agent to the At any other time branch replaces any voicemail already set there, so the agent itself must take callback details.
When the tests pass, open the number in the Flow editor, click + on the At any other time branch, choose AI Voice Agent, select the after-hours agent and click Publish. Aircall’s after-hours setup guide says this replaces any voicemail already configured on that branch.
With transfers switched off, the agent answers, takes the callback details and ends the call. Nothing in Aircall’s guides describes an automatic fall back to voicemail if the conversation goes badly, so do not draw one. Voicemail is an endpoint in its own right: once a message is recorded the call ends, and any widget placed after it is ignored.
Keep voicemail on the open-hours paths: behind each Ring to and on No or wrong input. The voicemail setup tutorial covers greetings, transcripts and email alerts for those messages.
Write a rollback note another admin can follow: which number, which branch, which widget to restore and which greeting it played. Then test the rollback once. A screenshot of the old flow explains it, but only a test call proves the line works again.
How do you test an Aircall call flow?
Test an Aircall call flow by calling every path from an outside phone; for the support firm in this tutorial that means twelve calls, including the minutes either side of closing time and an unanswered transfer.
For the support firm, twelve calls cover every path. Use a test window or a spare number so customers do not meet half-finished changes.
| Call cases | Tests | Expected evidence |
|---|---|---|
| Open hours: options 1 and 2 | 2 | The right team answers each |
| Open hours: nobody answers | 2 | Busy greeting and a retrievable message |
| No key and wrong key | 2 | Retry, then the general voicemail |
| One minute before and after closing | 2 | Correct branch on each side |
| After hours: supported and unsupported questions | 2 | Accurate answer or usable callback request |
| Hidden option 9: transfer and unanswered transfer | 2 | Transfer to the right team; voicemail when nobody picks up |
At about two minutes per test, that is 24 minutes of calls before retests, plus perhaps 30 minutes for two people to check outcomes and 10 to write up changes; these are planning estimates. If ten pass and the two around closing time fail, check the Time Rule timezone and slots before touching the AI, because the fault is in which branch the call reached. After the fix, rerun both boundary calls and one normal open-hours call.
For closures, add a Date Rule. First create the date under Settings > Special dates > Create special date, with a name, a date or date range, and All day unticked if you need a time window. Then add the Date Rule widget at the start of the flow, before the Time Rule, choose the special date and its timezone, give the special-date branch a holiday voicemail and connect Business As Usual to your Time Rule. One special date can be reused on several numbers, and Aircall notes a past date can still show as upcoming for up to 12 hours.
If you log the twelve test calls in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.
Review the first calls for promises and lost requests
Name an owner for each part of the flow: schedule (operations coordinator), greetings (service manager), AI knowledge base (support lead) and callback queue (duty coordinator). One person can hold several roles; the point is that a closure or new policy reaches the person who can change the right setting.
In the first fortnight, review real calls under your normal access rules. The AI Agents dashboard, included on every plan, shows calls fully handled by the agent, the escalation rate and the missed escalated calls rate; recordings and transcripts of AI calls show what it actually said. Compare each caller’s request with the callback details captured, and do not score the agent on fluency alone.
Estimate usage separately. Forty after-hours calls a month at two minutes each is 80 AI minutes. Essentials and Professional include 50 a month, so the other 30 cost 30 × $0.29 = $8.70 at the pay-as-you-go rate on the pricing page; calls under 15 seconds are not billed. Set a usage alert under the AI Voice Agents page’s Monitor consumption option; Aircall says alerts inform you but do not pause the agent.
Check menu changes against the spoken greeting every time. A sales team renames its enquiry service but leaves the recording offering the old option; calls still connect, so technical checks pass, yet callers hesitate. Ask a colleague who does not know the flow to listen and explain the choices back. Then use the dashboard setup tutorial to watch Abandoned in IVR and Outside of business hours misses alongside AI handling.
If you want help fitting this into how your support team actually runs, I offer one-to-one AI consultations for small businesses.
Further reads
- Aircall Free Trial: What to Test Before Committing to Three Licences — Run controlled calls before moving your main line.
- Aircall HubSpot Integration: Sync Calls, Voicemails and Tasks — Check how calls reach customer records.
- How Much Does Aircall's AI Voice Agent Cost per Minute? — Estimate AI usage beyond included minutes.
- How to Set Up an AI Phone Agent for After-Hours Calls — Decide what after-hours answering should promise.
- Aircall UK: Pricing, Local Numbers and the AI Voice Agent — What a UK team pays Aircall in pounds, how numbers and SMS work, what recording needs, and what the AI Voice Agent adds.
- How Much Is Aircall? Licences, the 3-Seat Minimum and AI Add-Ons — A three-seat Aircall bill built line by line: licences, extra numbers, AI Assist Pro and AI Voice Agent minutes, with four worked scenarios.
Show 2 more related tutorials
- Aircall Salesforce Setup: Sync Calls, Notes and Outcomes to Leads — Check eligibility, install Salesforce v3, see exactly where notes and call results land on a lead, then add a tested Flow for outcome fields.
- How to Create a Zapier Task for Every Aircall Missed Call — Build and test one Zap that turns Aircall missed calls into dated follow-up tasks, with the filter, opening-hours rules and the task maths.
Browse all AI-for-business tutorials
Sources: Aircall Help Centre articles Call flow widgets: The Time Rule widget; The IVR widget and voicemail notifications; Ring to and Redirect to; The Voicemail widget; The Date Rule widget; The Input IVR widget; Setting up call routing in a call flow; Using call flow templates; Flow editor: Errors and warnings; Setting up an after-hours AI Voice Agent; Configuring your AI Voice Agent; Understanding your AI Voice Agent charges; Track AI Voice Agent's performance. Aircall pricing page.
