Not every team that handles your inbound calls is the same size. Not every office has the same number of available agents. And not every routing strategy should treat destinations as if they were equal when they clearly are not.
Percentage-based call routing — also called weighted call routing — is the method that reflects this reality. Instead of sending calls in strict equal rotation, it distributes incoming volume according to a defined ratio you set in advance. Seventy per cent to one destination, thirty per cent to another. Or sixty-forty. Or fifty-fifty. Whatever the split, the system honours it consistently across every call that comes in.
This article explains how it works mechanically, where it fits in practice for Australian businesses, how it compares to other routing strategies, and where its limitations sit.
What Is Percentage-Based Call Routing?
Percentage-based call routing is a call distribution method in which each destination — whether that is an office, a team, a call queue, or an external number — receives a defined share of total inbound call volume based on a percentage you configure.
The percentages across all destinations must add up to 100. When a call arrives, the system consults its rolling count of how calls have already been distributed and routes the next call to whichever destination is currently under-served relative to its target share.
This is distinct from round-robin routing, which rotates calls evenly across destinations one at a time and assumes all destinations should receive equal volume. It is also distinct from sequential routing, which always tries destination A first and only moves to destination B if A is unavailable. Percentage routing makes no assumption about equality — it simply enforces whatever ratio you define.
The routing logic sits inside your phone system's automatic call distribution engine and is applied before the call reaches an agent. Callers are unaware of any of this — from their perspective, they dialled a number and the call connected.
How It Works Mechanically
The system maintains a running count of how many calls have gone to each destination. It uses this count to determine whether the current distribution matches the target percentages.
If your configuration is 70% to destination A and 30% to destination B, the system aims to deliver 7 of every 10 calls to A and 3 of every 10 to B. Some implementations use a strict sequential block — routing 7 calls to A then 3 to B, then repeating. Others use probabilistic weighting, where each call has a 70% chance of going to A and a 30% chance of going to B, which produces the correct ratio over time but not necessarily within every block of 10.
Either way, the outcome across meaningful call volumes is the same: the ratio holds.
Worked Example: 70/30 Split Across 10 Calls
The table below shows how a strict block-based 70/30 split distributes 10 consecutive inbound calls.
| Call Number | Routed To | Running Count (A / B) |
|---|---|---|
| 1 | Destination A | 1 / 0 |
| 2 | Destination A | 2 / 0 |
| 3 | Destination A | 3 / 0 |
| 4 | Destination A | 4 / 0 |
| 5 | Destination A | 5 / 0 |
| 6 | Destination B | 5 / 1 |
| 7 | Destination A | 6 / 1 |
| 8 | Destination B | 6 / 2 |
| 9 | Destination A | 7 / 2 |
| 10 | Destination B | 7 / 3 |
At the end of 10 calls, destination A has received 7 (70%) and destination B has received 3 (30%), exactly matching the configured ratio. The pattern then resets and repeats.
When to Use Percentage-Based Call Routing
Multi-Site Staffing Imbalance
The most common use case is a business operating across two or more locations where agent headcount differs significantly between sites.
If your Sydney office has eight agents on the phones and your Melbourne office has three, routing calls equally between them does not reflect available capacity. Under a 70/30 split, Sydney absorbs the volume its staffing level supports, and Melbourne receives a share proportionate to its smaller team. Agents in both locations stay busy without either site being overwhelmed or underutilised.
As headcount changes — new hires, growth, restructuring — you adjust the percentage and the distribution adjusts automatically.
Primary Team with Overflow Support
Many Australian businesses engage an overflow contact centre to handle calls when their internal team is at capacity. Percentage routing is a practical way to keep that overflow partner engaged and trained on your calls without routing the majority of volume to them.
A common configuration is 80% to the internal team and 20% to the overflow centre. The overflow centre maintains familiarity with your business, your products, and your call types. When a genuine overflow event occurs — a spike in call volume, a staff shortage, or an outage — that partner is already warm rather than encountering your callers for the first time.
This arrangement also creates a natural failover path when combined with routing rules that escalate to the overflow centre if the internal team's call queue exceeds a defined wait threshold.
Outsourced and Insourced Hybrid Operations
Businesses that manage a mix of in-house and outsourced call handling often use percentage routing to define the boundary between the two. An in-house team handling 60% of volume and an outsourced partner handling 40% is a straightforward configuration. It gives both parties a predictable and consistent workload, which simplifies staffing, reporting, and contract management on both sides.
A/B Testing Call Scripts or Team Approaches
When you want to measure the impact of a change — a new call script, a different opening question, a revised pricing offer — percentage routing gives you a controlled way to run the test.
Route 50% of calls to team A using the current approach and 50% to team B using the new version. Track conversion rates, call duration, or customer satisfaction scores for each group. Because the split is consistent across incoming volume, you avoid the distortion that comes from one team receiving more calls than the other during the test period.
This is a use case that tends to be underused but is straightforward to configure on a capable phone system.
Gradual Office Migrations and Rollouts
If you are moving a team from one location to another — or transitioning call handling from an old system to a new one — percentage routing lets you manage that migration in stages rather than cutting over all at once.
Start with 90% of volume going to the existing team and 10% going to the new location or team. Once the new site has demonstrated it can handle calls reliably, shift to 80/20. Continue incrementally until the migration is complete. If issues emerge at the new site at any point, reduce its percentage while you resolve them. The caller experience remains uninterrupted throughout.
Percentage Routing vs Round-Robin Routing
Round-robin routing distributes calls in equal rotation — agent or destination 1 gets the first call, agent or destination 2 gets the next, and so on in a repeating cycle. It is the right choice when all destinations have comparable capacity and you want to spread workload fairly across an equal pool.
The problem arises when destinations are not equal. If you apply round-robin to a Sydney office with eight agents and a Melbourne office with three, Melbourne will receive far more calls than it can comfortably handle while Sydney sits with spare capacity. The rotation does not care about the reality on either end.
Percentage routing solves this by letting you encode the actual capacity differential into the routing logic. It is a configuration decision that takes five minutes to update and can meaningfully change how evenly your agents are utilised.
The two methods are not mutually exclusive. You can use percentage routing to split volume between sites or teams at the top level, then apply round-robin within each destination to distribute calls fairly among individual agents once they arrive.
Percentage Routing vs Geographic Routing
Geographic routing directs calls based on where the caller is calling from. A caller in Queensland might be routed to your Brisbane office; a caller in Western Australia to your Perth team. The routing decision is based on caller location, not on distribution targets.
Percentage routing is agnostic to caller origin. It does not matter whether the call is coming from Cairns or Canberra — the system routes it according to the configured ratio. A 70/30 split applies to every call, regardless of where it originates.
In some deployments, the two methods are used in combination. Geographic routing handles the first layer of logic — sending interstate calls to the nearest office — and percentage routing handles the second layer, splitting volume between multiple teams or queues within that region. Each method does a different job and they can coexist in the same routing configuration.
Limitations of Percentage-Based Call Routing
Percentage routing is a powerful tool, but it operates on a key assumption: that the configured ratio reflects actual, real-time capacity. That assumption does not always hold.
It Does Not Account for Real-Time Agent Availability
If the Sydney office is in a company-wide meeting when calls start arriving, the system still routes 70% of volume there — because the configuration says 70%, not because 70% of your available agents happen to be in Sydney at that moment. Calls will stack in a queue or go unanswered unless separate overflow rules are in place to catch them.
This is the most important limitation to understand before relying on percentage routing. The percentage you configure reflects your intentions about volume distribution. It does not dynamically respond to what is actually happening at each destination in real time.
Pair It with Overflow Rules
The standard mitigation is to configure overflow triggers alongside the percentage split. If calls at destination A go unanswered beyond a defined threshold — say, 30 seconds or three rings — they divert to destination B regardless of the percentage logic. This creates a safety net that the percentage configuration alone cannot provide.
Most capable business phone systems, including Pickle's, allow overflow rules to be layered on top of percentage routing configurations so that the ratio governs normal conditions while the overflow rules protect against exceptions.
Works Best for Predictable Call Volume
Percentage routing is most effective when your call volume is relatively stable and predictable. If your inbound call patterns are highly irregular — large spikes at certain times of day or on certain days of the week — a fixed percentage split may not reflect capacity needs accurately across every period. Time-of-day routing or skills-based routing may be more appropriate for those conditions, or you may need to adjust percentages to reflect staffing levels at different times.
How Pickle Supports Percentage-Based Call Routing
Pickle's business phone system supports percentage-based routing as a native configuration option. You set the destination percentages through the system, and the distribution runs automatically across your inbound calls without any manual intervention required.
Routing configurations can be updated at any time — if your staffing ratios change, you change the percentages. If you are running a short-term A/B test, you configure the split for that period and adjust it when the test concludes.
Pickle also supports the layering of overflow rules on top of percentage routing, so you are not left exposed when a destination is unexpectedly unavailable. If you are operating across multiple sites, managing an outsourced call handling arrangement, or thinking about how to distribute volume more intelligently, percentage routing is worth discussing with the team.
Call 1300 688 588 or email [email protected] to talk through how percentage-based routing would work in your specific setup.
Frequently Asked Questions
Q: Do the percentages have to be round numbers?
A: Most business phone systems, including Pickle's, require whole number percentages that add up to exactly 100. You cannot configure a split of 33.3%/33.3%/33.4%, for example — you would round to 34/33/33 or similar. For most practical deployments this is not a meaningful constraint, as the difference between a 33% and 34% split becomes negligible over any significant call volume.
Q: Can percentage routing be used with more than two destinations?
A: Yes. You can split across as many destinations as your phone system supports, provided the total adds up to 100%. A business with three offices might configure 50/30/20, or four teams at 40/30/20/10. Each additional destination simply means the system is tracking more counters, but the underlying logic is the same.
Q: What happens if one destination is closed or unavailable?
A: Without overflow rules in place, calls routed to an unavailable destination will go unanswered or divert to voicemail, depending on how that destination is configured. This is why pairing percentage routing with overflow rules is strongly recommended. When an overflow rule triggers — because a call goes unanswered within a defined timeframe — it diverts to the next available destination regardless of the percentage allocation for that call.
Q: Is percentage routing suitable for a single-office business?
A: It can be, but its primary value is for multi-destination scenarios. Within a single office, round-robin routing among individual agents typically achieves the same goal with simpler configuration. Percentage routing becomes useful within a single office when you have distinct teams — for example, routing 60% of inbound enquiries to your sales team and 40% to your support team — rather than routing by individual agent.
Q: How quickly can the percentage split be changed?
A: Changes to a percentage routing configuration take effect immediately once saved. There is no waiting period or service interruption. This makes it practical to adjust splits in response to staffing changes, temporary absences, or time-limited campaigns without needing to contact a provider or raise a support ticket.