Planning with an outsourcer alongside: top tips for the in-house planner
When the planner’s job suddenly has two sites
For most workforce planners, the contact centre they plan for is a single operation — one set of agents, one ACD, one set of SLAs, one P&L line. The day an outsourcer is brought in alongside, the job changes. The forecast no longer goes to one place. The schedule no longer covers all the work. The SLA report has at least two columns. The “real-time” view now needs information from a site you cannot walk to, run by people who do not work for you, paid through a contract written by someone else. The planning craft still applies, but it has to be applied differently — and the planners who do this well treat the partnership as a piece of design, not as an event.
This article is for the in-house planner navigating an outsourcer-alongside arrangement for the first time. It covers what changes when the BPO arrives, the contractual realities the planner has to live inside, and a set of practical tips drawn from operations that have done this badly and operations that have done it well.
The contract is the planner’s foundation
Before any planning advice applies, the planner needs to understand the contract. The commercial structure of an outsourcer relationship determines what the planner is incentivised to do, what the BPO is incentivised to do, and where the two sets of incentives align or diverge.
Three common structures appear. Per-contact pricing pays the BPO a fixed fee per call or chat handled — they take volume risk and have an incentive to handle contacts as efficiently as possible. Per-minute pricing pays for the time spent on handled work and shifts AHT risk back to the client. Per-FTE pricing pays a fixed monthly fee per agent supplied and transfers most operational risk back to the client. Most real contracts combine elements. Layered on top are SLA bonus and penalty clauses that reward the BPO for hitting agreed targets and penalise misses.
The planner who reads the contract once before designing any of their plan will save months of confused conversations later. The planner who never reads it ends up modelling the wrong things and complaining about decisions that the contract gave the BPO every right to make.
Ten tips for the planner
1Be honest about the volume forecast you give them
Outsourcers price and staff based on the forecast you provide. An over-forecast leaves them holding empty seats that you may still be paying for, breeds resentment, and breaks future negotiations. An under-forecast leaves them under-staffed against an SL target you both share, missing it together, and burning the relationship faster than any other mistake. Give them the same forecast you give your own operations team. If the forecast has uncertainty, share the range. The BPO planner is a professional like you, not a vendor to be managed by selective information.
2Set up routing rules explicitly and document them
The single biggest source of avoidable friction is unclear routing. Decide before go-live: what percentage of volume goes to the BPO, on what skills, with what overflow logic when one site is short. Document the rules in writing, with both planning leads signing off. The day a senior manager asks “why did the BPO get 60% this week when it should have been 40%?”, the answer should be one sentence and a link to a document, not a defensive reconstruction.
3Agree the data flow before go-live
The BPO will need data from you and you will need data from them. Agree what is sent, in what format, at what frequency, and through what channel before the first call is handled. Volume by interval, AHT, abandonment, SL, agent state, shrinkage, and absence are the usual list. Operations that try to design the data flow after go-live spend their first three months arguing about reconciliation discrepancies instead of operating.
4Define how SLA is measured — really define it
SLA looks like a single number until you look closely. Is the BPO’s SL measured against the contacts that landed on their queue? The blended performance of both sites combined? The enterprise SL across all channels? Is abandonment included? At what interval granularity? The contract usually specifies this, but the planner has to live with the specification. Run a worked example with the BPO’s planner in the first month — pick a recent day, calculate the SL from the raw data, and confirm both sides land at the same number.
5Don’t treat the BPO as overflow only
A common pattern is to send the BPO whatever volume the in-house operation cannot handle in the moment — a spike on Monday, the late shift on Wednesday, the awkward call types on Friday. This destabilises the BPO’s planning, makes their SL impossible to hit, and reveals you as a difficult client. Build a planned baseline of volume that goes to the BPO consistently, with overflow as a supplementary layer rather than the default. The BPO can absorb spikes much better when they have a stable baseline to staff around.
6Build a joint planning rhythm
The relationship that makes outsourcer-alongside arrangements work is between the two planning leads, not between the account manager and the procurement function. Establish a weekly forecast review with the BPO’s planning lead, a monthly capacity review with both planning teams in the room, and a quarterly business review that includes operations leadership. Walk the floor at the BPO if you can. Visit the in-house operation with their planner if practical. Familiarity is the single biggest predictor of whether the partnership survives a difficult quarter.
7Plan for the learning curve
New BPO agents go through the same ramp-up curve as your own new hires — slower at first, longer AHT, more help requests, more escalations to specialists. Build this into your blended forecast for the first three to six months. A BPO that promised 280-second AHT will, on day one, deliver 360-second AHT, and that is normal. Operations that assume launch-day productivity build forecasts that miss for a quarter and then blame the BPO. The blended AHT is a number that improves; budget for the improvement curve rather than assuming the end-state.
8Watch the seam
The point where a customer transfers between in-house and BPO is the highest-risk part of the operation. Transferred customers wait longer, repeat themselves, and often get worse outcomes than customers who land on the right queue first time. Track the volume that gets transferred between sites, the satisfaction of those customers compared to non-transferred, and the AHT impact. If the seam is wider than expected, the routing rules need rework, not the front-line agents.
9Understand your commercial incentives — and theirs
The way you and the BPO are paid changes the decisions each side rationally makes. Under per-contact pricing, the BPO is incentivised to reduce AHT — sometimes at the cost of first-contact resolution. Under per-FTE pricing, the BPO has every reason to over-staff slightly and bill you for it. Under per-minute pricing, the BPO is neutral on AHT but has every incentive to staff carefully. Recognising the incentive structure in advance lets the planner build the metrics that catch the unintended behaviours before they cost real money.
10Don’t hide problems from them — or expect them to hide problems from you
The temptation when an SL miss is approaching is to manage the conversation rather than share the information. Operations that do this on either side find the relationship sours fast. The BPO that hides an absence problem leaves you blind to it. The in-house planner who hides a forecast revision until the last minute leaves the BPO no time to react. Mutual transparency is the cheapest investment either side can make, and the one that pays back most consistently.
Common mistakes
Four patterns recur. The first is treating the BPO as adversarial rather than as a partner — the relationship becomes transactional, information flow narrows, and decisions get worse on both sides. The second is feeding the BPO inconsistent volume: feast and famine that no planning function could absorb without quality damage. The third is failing to model the commercial mechanics — the planner produces a recommendation that makes operational sense but contractual nonsense, or vice versa. The fourth is not investing in the human relationships — when the two planning leads have never met, the operational coordination depends on email threads, and email threads cannot carry the trust that the relationship needs.
The partnership mindset
The single sentence that helps most when planning with an outsourcer alongside is this: their planner has the same problems you do, with less context. Give them the context. Trust them with information. Treat the failures as joint failures and the successes as joint successes. The partnership that runs on this basis is not just commercially better — it is materially less stressful to plan inside, because the planner is not constantly defending against a partner who is treated as the enemy.
Conclusion
Bringing an outsourcer alongside is a permanent change to the planner’s working day. The forecast is no longer for one site. The schedule is no longer for one team. The SLA is no longer one number. The relationship with the BPO planner becomes one of the most important relationships you have, on a par with your own operations manager. Treated well, the arrangement produces an operation that is more flexible, more resilient, and often more cost-effective than the in-house function alone. Treated badly, it produces twice the work and worse outcomes than the in-house operation would have produced without help. The difference is mostly in how the planner approaches the partnership — and that is a choice you make in the first month and live with for years.
Pair this with understanding contact centre finance for the commercial framing of BPO pricing structures, and the weekly schedule review meeting for the rhythm that scales naturally into the joint planning forum described above.
Comments
Comments are powered by Giscus — sign in with GitHub to join the discussion.