Ask for workforce planning data before sizing a platform

A workforce director hands you one number, four hundred fifty agents, and asks for a price. That number describes nothing about how the operation actually runs. Behind it sits a forecast model, a set of scheduling rules, and a group of supervisors who make changes on the fly when the day does not match the plan. Price a platform off headcount alone and you are pricing a guess. The proposal built on that guess falls apart the first time someone checks it against the real planning data.

Why this conversation goes wrong

Workforce directors give you a headcount because that is the number finance asks them for. It is easy to say and easy to write down. It also hides everything a platform actually has to support, how often the forecast misses, which contact types swing the most, and who has authority to change a schedule once the shift starts.

Account executives make this worse by treating the number as a finish line. A quote goes out fast, the deal seems to move, and everyone feels progress. Then implementation starts, someone from operations reads the proposal, and the scope is wrong. Chat volume was never modeled. Overtime rules were never asked about. Now you are rewriting a proposal after the customer has already formed an opinion about whether you understood their business.

The gap usually comes from a simple mismatch. Voice planning and chat planning often live in different tools, run by different people, on different schedules. A single headcount flattens that difference into one line. Your job in this conversation is to put the difference back.

How to prepare

Walk into the call with a short list of questions ready, not a pricing sheet. You want to know what forecast method the team uses, how far ahead they plan, and which contact types get treated differently in that forecast. You want to know who can change a schedule after it publishes and how often that happens. You want to know whether supervisors see the same queue data as the planners, because a gap there usually means two groups are making decisions off different information.

Before the call, sketch three columns on paper or in a notes app, one for forecast, one for daily decision, one for record. As the customer talks, you are filling in these columns, not calculating a price. This keeps you from jumping to scope before you understand the operating problem.

Also check who is in the room. A workforce director alone can describe voice planning well but may know little about how chat or back office teams schedule. If the account has more than one contact channel, ask early who owns planning for each one, and flag that you may need more than one person on a later call. This sets up the working session you are aiming for, instead of springing it on the customer at the end.

What to say

Marta, a workforce director, opens with a number. "We run four hundred fifty agents. Send me a price for that."

Evan does not answer with a number. "I can put together the right scope once I understand how those agents are planned. What forecast do your planners use, and which teams can change a schedule once call volume moves off that forecast?"

Marta explains that her planning team owns voice forecasting and adjusts staffing through their scheduling system. Chat is different. "Chat supervisors make their own calls when queues back up. They are not really part of our planning process."

Evan follows the thread. "Where do those chat adjustments get recorded today?"

Marta says they use a shared spreadsheet that gets updated by hand. Evan responds, "That is useful to know, because it means chat and voice are running on two different sources of information right now. Before I send anything with a number on it, let us get a planner and a chat supervisor into a short working session. We can map out the forecast method, the daily decisions each group makes, and what your leadership actually needs to see across both."

Marta pushes back once. "I still need a number for budget planning."

Evan holds the line without stonewalling her. "I can give you a rough range today based on headcount alone, and I will, but I do not want that range to become the number your leadership plans around. Once we have the working session, I can give you a scope that actually holds up when your team reviews it."

That last line matters. Evan does not refuse to help Marta with her immediate need. He separates a rough estimate from a real proposal, and he says why.

Mistakes to avoid

Account executives lose this conversation in a few predictable ways. First, they quote off the headcount because the customer asked for a number and saying no feels like friction. Second, they ask about forecasting in general terms and accept a vague answer instead of pushing for specifics like which contact types behave differently or who owns the exception process. Third, they skip the question of who else needs to be in the room, then find out weeks later that chat, email, or back office work was never in scope. Fourth, they treat the working session as optional instead of asking for it directly, so it never gets scheduled.

The common thread in all four is speed. Moving fast on a wrong number is not progress, it is a debt that comes due during implementation, usually in front of the same operations team you skipped.

How to practice and score it

This exchange is worth rehearsing before you take it live, because holding your ground on a specific ask, in this case a working session with a planner and a chat supervisor, is harder in the moment than it sounds on paper. You can rehearse this exact scenario against an AI counterpart in DealSpeak and get scored on whether you held the commercial question until the operating picture was clear, and whether you actually secured a next step with the right people instead of a vague promise to follow up.

A manager reviewing a recorded roleplay should check for the three column framework directly. Did the rep get a real answer for forecast method, daily decision rights, and where records live, or did they accept a generic answer and move on. Did the rep ask who else needs to be in the room once a second contact type came up. Did the rep resist giving a firm number before that information existed, while still giving the customer something useful in the meantime.

This same discipline, asking for the operating detail before committing to a number, shows up across other contact center conversations too. You can find more of them, including Recovering After a Customer Gets Stuck in Automation and Guiding a Family Through a Bereavement Account Processamong the Contact Centers practice conversations built for this kind of work.

A headcount is a starting point, not a scope. The account executives who win these deals cleanly are the ones who ask what sits behind the number before they ever put a price next to it.