Every time a call arrives at your business number, your phone system runs a decision. Who should answer? Is the office open? Are your team members available? If no one picks up, what happens next?
Those decisions are governed by call routing rules — and for most Australian small and medium businesses, getting them right is the difference between a professional, consistent caller experience and a chaotic one where calls bounce to voicemail at noon on a Tuesday.
This guide covers what call routing rules actually are, the main types, how they layer together, and how to build and test a ruleset before you ever touch your phone system portal.
What Is a Call Routing Rule?
A call routing rule is a conditional instruction. In plain terms: when condition is true, send the call to destination.
Both the condition and the destination can be as simple or as complex as your operation requires.
A simple rule might be:
- Condition: It is currently Monday to Friday, 9am to 5:30pm
- Destination: Ring the sales team
A more specific rule might be:
- Condition: The caller is dialling from a Queensland area code, and it is a business day, and all Queensland-based agents are currently on calls
- Destination: Overflow to the national support queue
Rules can be stacked, layered, and sequenced. The phone system evaluates each rule in order and routes the call as soon as a matching condition is found. This means the order in which you set up your rules matters just as much as the rules themselves.
The Five Main Types of Call Routing Rules
Time-of-Day Rules
Time-of-day rules are the foundation of almost every business phone setup. They define which hours your system treats as "open" and route calls accordingly.
A typical configuration for a professional services firm might look like this:
- Monday to Friday, 8am to 6pm: route to the main team ring group
- All other times: play an after-hours greeting and divert to voicemail-to-email
Time-of-day rules are straightforward to configure but easy to misconfigure — particularly when daylight saving shifts apply or when someone forgets to account for the gap between, say, 5:30pm and 6:00pm when staff have left but the system still considers the office open.
For a detailed breakdown of how to handle the outside-hours scenario, see the guide on after-hours routing.
Calendar and Date Rules
Calendar rules handle known exceptions: public holidays, seasonal closures, team offsites, and one-off events.
In Australia, public holidays vary by state. A business operating nationally needs separate calendar rules for Queensland, New South Wales, Victoria, and so on — because a call landing on Easter Monday should behave differently depending on whether the caller (or the relevant team) is in a jurisdiction where that day is a public holiday.
Calendar rules should sit above time-of-day rules in your routing priority order. If they don't, your time-of-day rule fires first and the holiday rule is never reached — meaning calls ring through to an empty office all day.
For a full list of Australian public holidays and how to configure routing around them, see the guide on public holiday routing.
Caller-Based Rules
Caller-based rules route inbound calls according to information about who is calling or which number they dialled.
Two common configurations:
Geographic routing: A call from a Sydney area code (02) routes to the Sydney team; a call from a Melbourne area code (03) routes to the Melbourne team. This is particularly useful for businesses with state-based sales or service teams who have local knowledge. See the guide on geographic routing for configuration specifics.
DNIS routing (Dialled Number Identification Service): If your business operates multiple inbound numbers — for example, one number for sales and a separate number for support — DNIS rules let the system detect which number was dialled and route accordingly. This is common with 1300 number routing, where a single 1300 number can be split into campaign-specific or department-specific routing paths.
Condition-Based Rules
Condition-based rules fire when the state of your team or queue meets a defined threshold. They handle the "what if" scenarios:
- All agents are currently on calls: route new calls to a queue with estimated wait time messaging
- A caller has been waiting in queue for more than three minutes: overflow to a secondary team, a different ring group, or a voicemail option
- No agents are logged in: skip the queue entirely and route directly to voicemail or an on-call mobile
These rules are what prevent callers from ringing into an empty system during an unexpectedly busy period. They are also the rules most often left unconfigured — businesses set up their standard routing and forget to define the fallback.
Priority Rules
Priority rules identify specific callers or caller characteristics and route them differently from the general flow.
Common implementations include:
- VIP caller identification: Specific phone numbers or caller ID patterns are matched against a list and routed directly to a senior account manager or dedicated extension, bypassing the main queue
- Direct lines: DDI (Direct Dial-In) numbers that bypass the IVR entirely and ring a specific person or team — useful for key accounts or internal lines
- Campaign-specific routing: Inbound numbers tied to a specific advertisement or campaign route to a dedicated sales rep or team with relevant context
Priority rules are often the last to be configured but among the most valuable for customer experience at the top of your client base.
How Routing Rules Layer Together
Most business phone systems evaluate routing rules sequentially — top to bottom, or in an explicit priority order that you define during configuration. The system applies the first rule whose condition is matched and stops evaluating from that point.
This has an important implication: rule order is part of your routing logic.
A common mistake is placing a time-of-day rule above a calendar rule. Here is what happens:
- Call arrives on Christmas Day at 10am
- System evaluates rule 1: Is it Monday–Friday between 8am and 6pm? Yes
- System routes to the main team ring group
- Your holiday closure rule is never reached
- Calls ring through to an empty office
The fix is simple — calendar rules must sit above time-of-day rules. But getting there requires understanding that the ordering is deliberate, not cosmetic.
The same logic applies to priority rules. If you want VIP callers routed before anything else, their rule must sit at the top of the stack.
The Routing Rule Stack: A Practical Example
Here is what a complete routing decision looks like for an inbound call on a 1300 number, working through a properly ordered rule stack:
- Call arrives on the business 1300 number
- Check: Is today a public holiday in the caller's state?
- Yes: Play public holiday closure message, offer voicemail option. End.
- No: Continue to next rule
- Check: Is the current time within business hours (Mon–Fri, 8am–6pm AEST)?
- No: Play after-hours greeting, divert to voicemail-to-email. End.
- Yes: Continue to next rule
- Check: Which number did the caller dial? (DNIS rule)
- Sales line: Route to sales ring group
- Support line: Route to support ring group
- Check: Are agents in the target group available?
- Yes: Ring available agents (round-robin or simultaneous)
- No: Place in queue with hold music and position announcement
- Check: Has the caller been waiting more than 3 minutes?
- Yes: Offer voicemail or overflow to on-call mobile
- No: Continue holding
This six-step stack is entirely achievable in a standard business phone system. It just needs to be defined correctly and in the right order before configuration begins.
For guidance on the IVR step — the menu the caller hears when they first connect — see the comparison of IVR options and how they interact with routing rules.
Worked Example: Routing Ruleset for a 10-Person Professional Services Firm
The following table shows a complete routing ruleset for a firm with 10 staff, operating Monday to Friday, with public holidays observed nationally.
| Priority | Rule Name | Condition | Destination | Notes |
|---|---|---|---|---|
| 1 | VIP Direct | Caller ID matches VIP list | Ring partner's direct extension | Bypass all other rules for key clients |
| 2 | Public Holiday | Today is a national/state public holiday | Play closure message, offer voicemail | Evaluated before time-of-day to ensure holiday override works |
| 3 | After Hours | Time is outside Mon–Fri 8am–6pm AEST | Play after-hours greeting, route to voicemail-to-email | Covers weekends, early mornings, evenings |
| 4 | DNIS: New Enquiries | Caller dialled the new business number | Route to business development ring group (3 staff) | Separate path for new vs existing clients |
| 5 | DNIS: Existing Clients | Caller dialled the client services number | Route to client services ring group (6 staff) | Dedicated team for existing relationships |
| 6 | Overflow: All Busy | All agents in target ring group are on calls | Place in queue, play hold music and position message | Queuing kicks in only when no agent is free |
| 7 | Queue Timeout | Caller has waited more than 3 minutes | Offer: press 1 for voicemail, press 2 to keep holding | Prevents indefinite queue without a choice |
| 8 | Fallback | No previous rule matched | Route to reception extension | Safety net — should theoretically never fire |
Key design decisions in this ruleset:
- Rule 1 ensures VIP callers never queue, regardless of hour (note: the firm may choose to disable this outside business hours — that would require splitting Rule 1 into two rules with a time condition)
- Rule 2 sits above Rule 3 because holiday closures must override time-of-day
- Rule 8 is a deliberate fallback — if something unexpected happens and no rule matches, calls go somewhere rather than being lost
Build the Logic Before You Touch the Portal
The most consistent advice from phone system administrators — and from Pickle's own implementation team — is this: write your routing logic on paper before you open the configuration portal.
A simple flow diagram works well. Draw each decision point as a diamond, each action as a rectangle, and trace every possible path a call could take. If you find a path that leads nowhere, you have found a gap in your ruleset.
Questions to answer before you configure:
- What happens when all agents are busy?
- What happens on a public holiday?
- What happens at 7:59am on a Monday?
- What happens if someone calls from interstate?
- What is the absolute fallback if nothing matches?
Answering these before configuration saves significant rework. Most phone system portals make it time-consuming to reorder rules or change destination logic after the fact — not impossible, but enough of a friction that it discourages the iteration needed to get it right.
Testing Your Routing Rules
Once your rules are configured, verify every path — not just the one you expect most callers to take.
How to test each scenario:
- Business hours path: Call from your mobile during business hours and confirm the call lands where expected
- After-hours path: Temporarily adjust the time-of-day rule so that the after-hours threshold is, say, 3 minutes from now. Wait 3 minutes, call in, confirm the after-hours message plays, then revert the threshold
- Public holiday path: If your system has a test mode or a manual date override, use it. If not, create a one-time calendar entry for today and confirm the holiday message plays before deleting it
- Overflow/queue path: Have all available agents put themselves on Do Not Disturb or log out, then call in and confirm the queue or overflow rule engages
- Fallback path: If possible, temporarily disable all rules except the fallback to confirm it catches calls correctly
Document what you tested and what the result was. If a rule does not behave as expected, check the priority order first — the issue is most often a higher-priority rule matching before the one you expected to fire.
Common Mistakes With Call Routing Rules
Overlapping Rules With Ambiguous Priority
When two rules could both apply to the same call, and neither sits clearly above the other, the phone system picks one — usually based on the order they were created, not the order that makes sense for your business. Define priority explicitly.
Forgetting Public Holidays
Time-of-day rules do not know what day it is in the public holiday sense. A rule that says "ring the team on weekdays 8am–6pm" will ring the team on Melbourne Cup Day, on ANZAC Day, on Boxing Day. Calendar rules are a separate configuration step that many businesses skip and then discover the hard way.
No Fallback Rule
Every routing stack needs a defined endpoint if no rule matches. Without one, calls may drop, generate an error tone, or produce an undefined behaviour depending on the platform. Build the fallback in from day one.
Routing to a Phone That Is Never Answered
A routing rule can point to any extension or ring group you define. If that extension belongs to someone who left the business six months ago, or that ring group no longer has any active members, calls will reach it — and then go nowhere. Routing configurations should be reviewed whenever staff change.
How Pickle Handles Routing Configuration
Pickle sets up call routing rules as part of the standard business phone system implementation. The process is straightforward: customers describe their call handling logic in plain English — "we're open weekdays 8:30 to 5:30, closed public holidays, and we want missed calls to come through as an email with the voicemail attached" — and Pickle's team translates that into a configured, tested routing stack.
For businesses that already have a phone system but are not confident their routing is correct, Pickle can review and rebuild the ruleset without requiring a platform migration.
To discuss your call routing configuration, call 1300 688 588 or email [email protected].
Frequently Asked Questions
Q: Can I have different routing rules for different inbound numbers on the same system?
A: Yes. Most business phone platforms allow per-number routing configuration. A 1300 number for sales can follow an entirely different rule stack than a local number used for client services. This is one of the main reasons businesses operate multiple inbound numbers rather than a single line.
Q: Do call routing rules apply to outbound calls?
A: Not typically. Routing rules govern inbound call handling. Outbound call behaviour — such as which caller ID is presented, which line is used, or which carrier is selected — is controlled by a separate set of outbound dial plan rules. The two are configured independently.
Q: How many routing rules can a phone system handle?
A: This depends on the platform, but most cloud-based business phone systems support enough rules that the practical limit is the complexity you can manage rather than any hard system ceiling. Where businesses run into problems is not running out of rule slots — it is losing track of the logic across many rules and creating conflicts.
Q: What is the difference between a routing rule and an IVR menu?
A: A routing rule determines where a call goes. An IVR (Interactive Voice Response) menu presents options to the caller and then uses their input as a condition within the routing logic. They work together: the routing rule might send a call to an IVR, and the caller's IVR selection then triggers the next routing rule. The IVR is one possible destination in your routing stack, not a replacement for the rules themselves.
Q: What happens if I do not set a fallback rule?
A: Behaviour varies by platform, but the outcomes are uniformly bad — calls may drop with a disconnect tone, loop back to the start of the IVR, or generate an error. Callers have no way to know what happened and are unlikely to try again. A fallback rule that routes to a general voicemail or a reception extension costs nothing to configure and prevents call loss.