You have a 30-minute first call with a prospective BPO vendor. Their AE will try to spend 20 of those minutes on a slide deck about their global footprint. Don’t let them. The goal of this call is to find out whether they can run your workload without you babysitting them, and that takes six questions and two specific numbers.
We’ve sat on both sides of these conversations for years. The pattern is consistent: serious BPO operators answer in operational specifics. Unserious ones answer in adjectives. Here is how to tell which one you’re talking to in half an hour.
The 6 questions to ask, with what a good answer sounds like
Print these. Ask them in order. The texture of the answer matters more than the answer itself.
- “What CCaaS platform do you run, and who owns the license — you or the client?” Good answer: a specific platform name (Talkdesk, Five9, Genesys, NICE CXone) and a clear position on licensing. Red flag: vague “we work with whatever you use” without naming a primary stack.
- “What’s your attrition rate for agents in their first 90 days?” Good answer: a real number between 8 and 25 percent and what they do about it. Red flag: “very low” or shifting to total company tenure.
- “Show me a redacted scorecard you use for QA, with the rubric.” Good answer: they share one within 48 hours and the rubric has 8-15 criteria with weighted scoring. Red flag: “we customize that per client” with nothing to show.
- “What’s your shrinkage assumption when you staff a queue?” Good answer: 28-35 percent, broken into paid breaks, training, coaching, attrition backfill. Red flag: confusion about the term or a flat percentage with no breakdown.
- “Walk me through how you handle a 40 percent volume spike on a Monday.” Good answer: floater pool size, overtime policy, cross-trained backup queues, and a callback deflection threshold. Red flag: “we’d flex up” with no mechanics.
- “Who is the operations manager I’d talk to weekly, and can I meet them today?” Good answer: that person joins the next 10 minutes of the call. Red flag: “we’ll introduce them after contract signature.”
The 2 numbers they should know off the top of their head
Ask for these without warning. If they have to “circle back,” that tells you the AE is not connected to delivery.
- Current CSAT on a workload similar to yours — they should quote a specific account (anonymized) with a number between 78 and 94 percent, and tell you the methodology (post-call IVR, email survey, sample size).
- Current AHT for that same workload — they should quote it in seconds, not minutes, and tell you the channel mix (voice, chat, email weighted).
If they give you ranges instead of numbers, or pivot to industry averages, they don’t run the floor. That’s a deal-breaker for any program where you’ll be paying north of $25,000 a month.
What to ignore in the first 30 minutes
Most of what BPOs lead with is theater. Skip past:
- The logo slide. Big logos mean they won a procurement process five years ago, not that they’re running it well today.
- “24/7 global coverage” without geo specifics. Ask which city, which timezone, which language coverage by hour-of-day. Vague always-on claims usually mean a single Manila site with night-shift attrition issues.
- AI and automation talk before you’ve validated the human operation. If they can’t tell you their first-call resolution rate, their AI deflection number is fiction.
- The org chart. You don’t care about their VP of Customer Success. You care about the team lead who’ll sit with your agents.
The 30-minute structure that gets you a real signal
Here’s the agenda we send the vendor before the call. Most appreciate it because it shortens their prep time.
- Minutes 0-5: Scope. You describe your workload — channels, volume, languages, complexity, expected ramp. They listen, don’t pitch.
- Minutes 5-20: Q&A. The six questions above, in order. You take notes against a scorecard (see below).
- Minutes 20-30: Next steps. If they cleared the bar, agree on what comes next: site visit, pilot scope, a reference call with a current client running similar volume.
BPO interview scorecard
Score each item 1-5. Multiply by weight. A serious partner clears 70 out of 100.
- CCaaS platform clarity — weight 10 — red flag: vague or “all of them”
- Attrition data on hand — weight 15 — red flag: “very low” with no number
- QA scorecard shared — weight 15 — red flag: nothing to show in 48 hours
- Shrinkage breakdown — weight 10 — red flag: doesn’t know the term
- Volume spike playbook — weight 15 — red flag: “we’d flex”
- Ops manager available now — weight 10 — red flag: post-contract intro only
- CSAT number with methodology — weight 15 — red flag: industry averages
- AHT in seconds with channel mix — weight 10 — red flag: ranges
We use this exact rubric when we evaluate sub-partners for our own clients. A vendor that scores under 60 is not worth a second meeting, no matter how polished the deck.
Now what? If you want to see how this plays out in a real engagement, our SaaS support cost case study shows what the scorecard caught before contract — and read more about how we structure call center outsourcing engagements.