The best approach for most businesses is a single-level IVR menu with two to four options, role-based ring or hunt groups behind each option, and explicit failover to voicemail or an on-call number. Below are five ready-to-program call flow examples covering sales, support, dispatch, after-hours, and overflow scenarios, plus a checklist you can hand directly to a VoIP admin or an installer like Businessvoip.
TL;DR:
- Using a single-level IVR with two to four options ensures callers can easily navigate without frustration, especially when combined with role-based ring or hunt groups.
- Proper failover paths, like voicemail or on-call numbers, prevent missed calls during high volume or technical issues, maintaining service continuity.
- Testing each call flow thoroughly, including paths for after-hours and holiday schedules, reduces the risk of system failures and lost calls over time.
- Small teams benefit most from ring groups, while larger, support-oriented operations should opt for call queues with callback options to handle volume spikes effectively.
- Customizing call flows with clear destinations, timeouts, and failovers is essential, as default systems often lack the necessary logic for reliable everyday operation.
Table of Contents
- Five Call Flow Examples You Can Hand to Your VoIP Admin
- Ring Groups, Hunt Strategies, or Queues: Which One Fits Each Menu Option?
- How Do You Test a Call Flow Before Going Live?
- What We See Go Wrong on Real Installs
- The Honest Take on Call Flow Design
- Ready to Have This Programmed and Installed On-Site?
- Sources
Five Call Flow Examples You Can Hand to Your VoIP Admin
Every one of these templates names a menu key, a destination, a timeout, and a failover path. That's the difference between a call flow that works on paper and one that survives a Monday morning rush. Swap in your own department names and ring times, but keep the structure.
1. Simple single-level IVR for small offices
This fits a business with two or three departments and no dedicated receptionist.
- Greeting: "Thanks for calling [Company]. Press 1 for Sales, 2 for Accounts, or hold for Reception."
- Press 1: Sales ring group (simultaneous ring, 20 seconds), fails over to Sales voicemail.
- Press 2: Accounts ring group (sequential ring, 15 seconds per line), fails over to a shared voicemail box.
- No input / hold: Routes to Reception extension, fails over to a general voicemail after 20 seconds.
- Invalid key or timeout: Repeats the menu once, then routes to Reception.
Keeping this to a single level matters more than it sounds. Four options is the practical ceiling for a menu a caller can hold in their head, and pushing past that number is when people start hammering "0" out of frustration, according to IVR setup guidance from Exotel.
2. Multi-site sales and support flow with shared queues
Businesses running multiple locations or multiple phone numbers (DIDs) need per-number menus that still funnel into shared teams.
- Each DID plays its own location-specific greeting ("Thanks for calling the Kitchener branch...").
- Press 1 routes to a shared Sales queue serving all locations, with an announcement stating position in line.
- Press 2 routes to a Support queue offering a callback option instead of holding.
- Both queues fail over to voicemail if wait exceeds a set threshold or the queue is full.
This structure lets a company with locations in Cambridge, Guelph, and Oakville staff one central sales team without forcing callers to know which branch handles what.
3. Service business dispatch flow with on-call failover
Trades, HVAC, plumbing, and similar dispatch-heavy businesses need a flow built around job scheduling, not departments.
- Press 1: "Schedule a service call" routes to a Dispatch ring group.
- Press 2: "Existing job or emergency" routes to an on-call mobile number as primary, then a second technician's mobile if unanswered.
- Press 0 at any time: Escapes to a live Dispatch coordinator, never a voicemail box.
- After hours: Automatically shifts to the emergency-only branch with a shorter greeting.
The escape-to-human option isn't optional here. A caller with a flooded basement who hits a wall of menu options will hang up and call a competitor, and Exotel's IVR guidance treats a "press 0" path as standard practice for exactly this reason.
4. After-hours and holiday template
After-hours menus should be shorter and simpler than business-hours menus, not a copy of them.
- Greeting: State hours plainly, then offer voicemail or emergency contact. Skip the marketing lines.
- Press 1: Leave a voicemail with a stated callback window (e.g., "within one business day").
- Press 2: Emergency on-call routing, for businesses that need true 24/7 coverage.
- Holiday override: A separate schedule rule that supersedes the normal after-hours rule on statutory holidays, so you're not manually toggling settings every December.
Company answering rules that separate business hours, after-hours, and custom holiday schedules let each condition trigger different behavior automatically, which is exactly how RingCentral's call routing documentation structures fallback logic.
5. Overflow and queue template for volume spikes
For support or sales lines that regularly hit capacity, a queue beats a simple ring group.
- Caller hears hold music with a periodic announcement stating estimated wait time.
- After a set number of seconds (commonly 60 to 90), the system offers a callback option instead of continued holding.
- If the queue itself is full, the call falls straight to voicemail rather than joining an endless line.
- Missed-call and abandoned-call data gets logged for review, not just handled and forgotten.
This template matters most during seasonal spikes, weather events, or a marketing campaign that suddenly doubles call volume. Without an overflow path, every one of those extra calls either loops forever or drops.
Ring Groups, Hunt Strategies, or Queues: Which One Fits Each Menu Option?
Not every IVR option needs the same routing behind it, and picking the wrong one is how a two-person office ends up with an enterprise call center's complexity, or a fifteen-agent support team ends up with everyone's phone ringing at once and nobody sure who should answer.
A ring group rings multiple phones simultaneously. It fits small teams, three to five people, where speed matters more than fairness. A hunt group rings phones in a strategy: sequential (one at a time, in order), simultaneous, or round robin/longest-idle (whoever hasn't taken a call the longest gets the next one). A call queue holds callers in line with music, an announcement, and often a callback option, reporting on wait times and abandonment along the way.
Here's a rough decision matrix:
- Small team (2 to 5 people), no fairness concerns: Ring group, simultaneous ring.
- Structured team where call distribution needs to feel fair: Hunt group, round robin or longest-idle.
- High call volume, support desk, need reporting: Call queue with callback option.
A related question worth working through separately is how queues differ operationally from ring groups once you're past ten or so daily calls per line.
Set ring times per agent around 15 to 20 seconds before moving to the next person or triggering group failover. Label every IVR option by role, "Sales," "Support," "Dispatch," never by an employee's name, since staff change but job functions don't, and re-recording a greeting every time someone leaves the company gets old fast.
Pro Tip: If your team logs off for lunch or end of day without setting Do Not Disturb, calls will keep ringing dead extensions. Staff who don't mark themselves unavailable are the single most common cause of calls that just ring out, according to career guidance on call center representative responsibilities. Build DND discipline into onboarding, not an afterthought.
How Do You Test a Call Flow Before Going Live?
Building the flow is the easy part. Testing it properly is what separates a phone system that works from one that quietly fails callers for weeks before anyone notices.
- Draw the flow first. Sketch every menu option, ring group, and failover path on paper or a whiteboard before touching the phone system's admin panel.
- Build the pieces in order. Create extensions, then ring groups, then voicemail boxes, then the IVR menu that ties them together. Building the IVR first just means you're pointing options at destinations that don't exist yet.
- Record greetings last, and keep them short. No marketing copy, no "your call is important to us" filler. State the options and move on, following the same logic behind Shopify Canada's voicemail greeting guidance.
- Set your configuration values deliberately: business hours, a single-level menu depth, invalid-key behavior (repeat once, then route to a human), and 15 to 20 second ring times per agent.
- Call every option from an external mobile phone. Provider preview or simulation tools inside the admin panel are not a substitute for a real external call hitting the system end to end.
- Test the after-hours path on purpose, not by accident at 11 p.m. when something breaks. Trigger the schedule manually if your platform allows it.
- Test the press-0 escape, an invalid keypress, and a timeout with no input at all.
- Simulate a full queue and a no-answer scenario to confirm failover actually lands where you expect.
Review the whole setup every three to six months, and update greetings the moment your hours or team structure changes. A missed-call report that nobody reads is a wasted tool. Set a notification so a supervisor sees missed calls the same day, not the same quarter. Nailing down failover internet for your VoIP connection belongs on this same checklist, since a call flow only matters if the calls reach it in the first place.
What We See Go Wrong on Real Installs
The most common mistake isn't a bad IVR script, it's no custom script at all. Plenty of systems still run on vendor-default menus, generic options nobody bothered to reprogram for how the business actually operates. The second most common mistake is a single option routing straight to one extension with no failover, so a manager's sick day silently breaks the sales line.
Businesses that get this right treat the phone system as something to design, not just plug in. On-site design, programming, cabling, staff training, fixed pricing with no annual increases, and a lifetime warranty on rented phones are the difference between a box of phones and a system that works from day one. The fastest wins: shorten every menu, add a press-0 escape everywhere, route by role instead of name, and test every path before go-live.
The Honest Take on Call Flow Design
Most advice on this topic obsesses over the IVR script, the words in the greeting, the menu tone, when the script is the least important part of the whole system. A perfectly worded greeting attached to a ring group with no failover still fails the caller. What actually determines whether a call flow works is the boring part: does every path have a destination, does every destination have a timeout, and does every timeout have a fallback that isn't silence.
The other place conventional advice falls short is treating call flow design as a one-time setup task. Teams change, hours shift, seasonal volume spikes happen, and a flow built for a five-person office in year one quietly breaks by year three if nobody revisits it. Prioritize the failover paths and the testing checklist before you touch a single word of script copy. Get the structure right first. Polish the greeting last, and keep it short when you do.
— James
Ready to Have This Programmed and Installed On-Site?
An experienced VoIP provider is the practical next step once your call flow is drawn out and you need someone to actually build it. Rather than shipping you a box of phones and a login, a local Ontario team designs the menu structure, programs every ring group and failover path, runs the cabling, installs the phones on-site, and trains your staff on it, so nothing is left half-configured for you to figure out later.
Businessvoip has done this since 2005, with fixed pricing that doesn't creep up every renewal and a lifetime warranty on every rented phone. If your team spans more than one location, the same design process applies to multi-site and remote office deployments, and businesses handling customer records alongside call routing sometimes pair their phone system with CRM automation to route calls based on existing customer data. If you're ready to move from templates to a working system, request a phone system design and get an on-site visit scheduled.
Sources
- Company answering rules — RingCentral API docs (GitHub)
- How to become a call centre representative — Indeed (Canada)