Managed Voice / Auto Attendant (IVR)

Conditional & Time-of-Day Routing

Beyond a simple open/closed split, call routing can branch on conditions like the time of day, the day of the week, which number someone dialed, or even data pulled from a connected CRM (customer database — see Glossary). That sends different callers down different paths automatically.

What kinds of conditions can trigger different routing?

Common examples: lunch-hour coverage (ring a smaller backup team from 12-1pm), weekend-only routing to an answering service, a “VIP” caller ID list that jumps straight to a manager, or routing based on which department line someone dialed. Each condition can layer on top of the others.

How does this differ from the basic open/closed schedule?

Business Hours vs. After-Hours Menus covers the simple two-state case. Conditional routing is the more general engine underneath it — the same tool that powers open/closed can also power any number of additional time- or data-based rules beyond just “open” and “closed.”

Can you layer rules — for example, business hours and a specific caller?

Yes. You can combine rules, so you might route “known VIP callers during business hours” one way, and “the same VIP callers after hours” a different way, without building two entirely separate systems.

Do these rules require ongoing manual management?

No — once configured, they run automatically based on the clock and the conditions you’ve set. You only need to make changes when your actual business rules change, not on a daily or weekly basis.

How do holidays fit into this?

We handle holidays and one-off exceptions as a specific type of condition that temporarily overrides your normal schedule. See Holiday & Exception Schedules for how you set those up separately from your recurring weekly rules.