Structuring a planning team for a small contact centre

Leadership · Scheduling · ~7 minute read

The planning of one

Most articles about workforce planning assume a contact centre large enough to have a dedicated planning team. The realities of a 50- or 80-seat operation are different. The same forecasting, scheduling, real-time, and reporting work has to happen, but there is rarely the headcount to specialise — and the operation cannot afford the tooling, governance, and process maturity that the textbooks describe. The result is usually one person, sometimes part-time, doing all of it. This article is about how to structure that work sensibly so the planning function is sustainable, the person doing it does not burn out, and the operation gets meaningful value from the investment.

The headcount maths

A 100-seat operation typically employs around 110 to 130 agent FTEs once shrinkage and part-timers are factored in. The rule of thumb for planning team size at larger scales is one planner per 150 to 250 agents, which mathematically suggests a small operation needs around half an FTE. In practice the floor is closer to one: the fixed cost of producing a defensible forecast, schedule, and intraday view is not proportional to operation size, and a half-FTE arrangement almost always falls over the first time the half-time planner is on holiday during a busy week. A single dedicated planner, properly supported, is usually the right answer up to about 150 seats. Below 50 seats, the work may fairly sit with an operations manager who treats it as part of their core remit rather than as a separate role.

The roles that must be covered

Regardless of how many people sit in the planning seat, six categories of work need to happen for the operation to run. Forecasting — producing a defensible weekly and monthly view of volume, AHT, and shrinkage. Capacity planning — a longer-range view of headcount versus demand, usually three to twelve months out. Scheduling — building the rota, processing leave, handling swaps. Intraday and real-time management — watching the day, communicating with team leaders, recovering when the day goes off plan. Reporting and management information — the numbers that the operations manager, finance, and senior management need to make decisions. Vendor and tool management — whatever WFM, CCaaS, and reporting tools the operation depends on need an owner.

At a small scale, the single planner does all six. The art is in deciding which to do well, which to do adequately, and which to outsource or automate.

Three workable shapes

Three structures consistently work for sub-100-seat operations. The first is the dedicated generalist: a single planning analyst whose entire role is the six categories above, reporting to the operations manager. This is the cleanest arrangement when the workload is genuine and consistent. The advantage is focus and accountability; the disadvantage is the single-point-of-failure problem when that person is unavailable, and the lack of an internal sparring partner to challenge their thinking.

The second is the operations manager who plans: the ops manager treats forecasting, scheduling, and intraday as a core part of their own role, with a part-time assistant for the administrative work (leave processing, schedule communication, basic reporting). This works when the operation is small enough that the ops manager can hold the full picture in their head, and when they have genuine numerical confidence. It fails when the ops manager is over-stretched and planning becomes the thing that gets dropped under pressure.

The third is the hybrid model: a planning analyst for the daily and weekly cycle, plus a managed service or fractional senior planner who handles the monthly capacity plan, the quarterly review, and any complex modelling that exceeds the in-house analyst’s skills. This is increasingly common because the managed-service market has matured, the cost has come down, and the senior expertise that a small operation cannot afford to employ full-time can now be rented by the day. The advantage is access to depth without the salary cost; the disadvantage is that the external partner is not on the floor and can miss context that an in-house planner would pick up naturally.

Skills to hire for at this scale

The right hire for a small operation is almost always a generalist, not a specialist. Deep statistical knowledge is less valuable than the ability to pivot cleanly between forecasting on Monday morning, schedule conflicts on Tuesday, an intraday incident on Wednesday, and a board pack on Thursday. The qualities that matter most are: comfort with ambiguity, good Excel and spreadsheet literacy (the operation will not be on enterprise tools), a service orientation toward team leaders and agents, the confidence to push back on senior managers without being defensive, and intellectual honesty about uncertainty. The candidate who looks great on paper because they have run a 2,000-seat operation is often the wrong fit; the work below 100 seats is a different shape, and the polish of big-operation experience can become a liability when the actual job is to wear five hats every day with no team to delegate to.

Tooling at this scale

The tooling decision at sub-100 seats is genuinely different. Enterprise WFM platforms (Verint, NICE, Calabrio, Genesys’s own WFM, Aspect/Alvaria) are designed for operations large enough to absorb the licence cost, the implementation cost, and the operating overhead of a full-featured tool. At 80 seats, the cost-per-agent of these platforms can exceed the marginal benefit by a wide margin, and the planner spends as much time feeding the tool as benefiting from it. Smaller-footprint products — Injixo, Playvox WFM, Assembled, and the increasingly capable native WFM modules built into modern CCaaS platforms like Genesys Cloud and Five9 — are usually a better fit. Above all, the planner’s spreadsheet skills matter more than the platform: at this scale, well-built Excel models are still doing most of the real work.

The relationships that anchor the role

A single planner is structurally vulnerable to isolation, and the strongest small-operation planners actively build relationships that compensate. A weekly conversation with finance keeps the planning function aligned with the cost conversation that senior managers care about. A genuinely two-way relationship with team leaders — not just a Friday email — surfaces the soft signals that no dashboard catches. A connection with another planner outside the organisation, through a community forum or a peer group, provides the sparring partner the planner does not have internally. These are not optional; they are how the role becomes sustainable.

When to add headcount

A small operation will eventually need a second planner. The signals that the time has come include: real-time hours that no longer overlap with planning hours (typical above 60 seats with extended opening), multi-channel or multi-skill complexity that exceeds what one person can model cleanly, sustained leave coverage problems that affect business continuity, and reporting demands from senior management that consume more than a day a week. The second hire is usually a real-time-and-reporting analyst sitting alongside a more senior forecasting-and-scheduling analyst — the split that mirrors the natural cadence of planning work. Below 150 seats this is almost always the right shape; above 150, the role splits further.

Common mistakes

Four patterns recur at small scale. The first is hiring a specialist when the role requires a generalist — usually a forecasting expert who cannot or will not do scheduling, intraday, and reporting at the necessary breadth. The second is over-investing in tooling: buying an enterprise WFM platform because the impressive demo convinced senior management that the existing manual approach was the problem, when the actual problem was process discipline that the tool will not fix. The third is treating the planner as administrative support — processing leave, building schedules to instruction — rather than a business partner with judgement that should influence decisions. The fourth is no succession plan: a single point of failure on a critical operational function, with all the knowledge in one person’s head and no documentation if they leave.

Conclusion

Planning in a small contact centre is harder than it looks and easier to get wrong than the size of the operation might suggest. The right structure is not a scaled-down version of a large operation’s function; it is its own thing, with its own constraints and its own opportunities. Hire a generalist, support them properly, invest in relationships rather than tooling, and recognise the signals when one person is no longer enough. Done well, a planning function of one is one of the highest-return investments a small contact centre can make. Done badly, it is one of the highest-friction roles in the operation, and the person doing it usually leaves within eighteen months — taking the only complete picture of how the operation actually runs with them.

Pair this with interview questions for hiring a scheduling analyst for the practical hiring process, and the true cost of attrition for what it costs when the planner you hired well leaves anyway.