Sortinghat

Is BPO Dying? What AI Actually Does to Process Outsourcing

The obituary is premature and the complacency is worse. Transactional BPO is compressing hard while process work inside GCCs grows.

By , Founder8 min read

BPO is not dying. A specific and large part of it is being compressed, while another part moves inside the client's own building. The distinction matters commercially, because a staffing firm that treats BPO as one market will lose accounts in the shrinking half while missing the growing one.

Last reviewed July 2026. Industry structure informed by NASSCOM sector reporting.

Key takeaways

  • Transactional BPO is where the compression is. High-volume, rules-based, per-seat work is the part automation reaches first and hardest.
  • Judgement-heavy process work is not compressing. Exception handling, escalation and anything requiring context still needs people.
  • Much of the surviving work is moving into GCCs. Clients are bringing process work in-house rather than buying it as a service.
  • For staffing firms the risk is a shrinking client, not a shrinking market. Your BPO accounts may contract while the same work reappears as GCC headcount.
Two
Distinct markets inside what people call BPO
Structural
2,117
GCCs in India absorbing process work in-house
NASSCOM / Zinnov
2.36M
People employed across those centres
NASSCOM / Zinnov
Staffing pipeline with candidates across stage columns, each showing a match score of 96, 93 or 92
Fig 2Ranked candidates moving through stages, with the score carried through.

The two markets inside BPO

Treating BPO as a single sector is the mistake that produces bad predictions in both directions.

Transactional BPO. High volume, rules-based, priced per seat or per transaction. Data entry, basic claims processing, tier-one support that follows a script. This is the part automation reaches first, because the work is defined precisely enough for software to do it.

Judgement-heavy process work. Exception handling, escalation, anything requiring context about a specific customer or a specific regulation. This does not compress the same way, because the value is in deciding rather than in executing.

The headlines about BPO dying are describing the first market. The people saying nothing has changed are working in the second.

Where the work actually goes

The part of BPO that survives automation frequently does not stay with a vendor.

A client that has automated the routine 70 percent of a process is left with a smaller, more complex remainder. That remainder is harder to specify in a contract, more sensitive to context, and more valuable to control directly. So it moves in-house, which in India usually means into a GCC.

The work did not disappear. The commercial relationship changed, which for a staffing firm is the more consequential fact. A vendor account shrinks while a direct-employment headcount plan appears somewhere else, often at the same parent company.

What this means for staffing firms serving BPO

Three consequences, in the order you will feel them.

Your BPO accounts get smaller before they get sophisticated. Seat counts fall on the routine work first. If your relationship is with a procurement function buying volume, that relationship shrinks with it.

The remaining roles are harder to fill. Exception handling requires judgement, domain knowledge and communication. That is a different candidate and a different screen, and it does not come from the same sourcing motion.

The growth reappears as GCC demand. Often at a company you already serve, bought by a different function. Firms that only sell to procurement will not see it.

The roles that survive, and what they need

If the routine work compresses, what remains is worth understanding in detail, because it is a different hiring brief.

Exception handling

The cases the automation could not resolve. These require judgement about a specific customer, a specific contract or a specific regulation, and they arrive without a script.

Quality and oversight

Somebody has to check that automated output is correct, and to notice when it stops being correct. That is a role with genuine consequences and it is not junior work.

Client-facing escalation

When something has gone wrong, the person handling it needs communication skill and domain context at the same time. This is where volume hiring processes fail most visibly, because a CV screen tells you nothing about either.

Process design

Deciding what should be automated, and how the remaining human steps fit around it. A smaller category and a much higher fee.

All four fail on judgement and communication rather than on eligibility, which means a five-minute call confirming availability will not sort them. The screen has to test the claims that actually decide the hire.

What does not change

Worth saying plainly, because the panic is as unhelpful as the complacency.

Volume hiring is not going away. Somebody still staffs the centres, still handles the ramp, and still deals with attrition. What changes is that the roles skew more towards judgement and less towards throughput, which raises the bar on screening rather than removing the need for it.

The firms that struggle are the ones whose entire value proposition was supplying bodies quickly at a low fee. That was always a commodity position and automation is simply the thing that finally priced it correctly.

What the numbers look like when a process is automated

The pattern is consistent enough to plan against, even though the exact split varies by process.

A rules-based process typically has a large majority of volume that follows a predictable path, and a minority that does not. The predictable majority is what automation takes. The minority that requires a decision is what remains, and it does not shrink in proportion.

So a centre that automated most of its transaction volume does not reduce headcount by the same share. It reduces the routine roles heavily and keeps, or sometimes increases, the people handling everything the automation escalates.

For a staffing firm the consequence is specific: the seat count falls faster than the fee pool, because the roles that survive pay more and take longer to fill. A firm measuring its BPO exposure by placements will overstate the damage. A firm measuring it by revenue will see something more manageable, and a firm measuring by fee per placement may see it rise.

The exposure that genuinely hurts is a business built on speed and low fee for interchangeable roles. That was a commodity position before automation and the technology simply priced it correctly.

What clients actually buy from a BPO staffing partner now

The pitch that worked five years ago was speed and volume at a competitive rate. That pitch is now describing the part of the market being automated, which is an uncomfortable place to be selling.

What a centre with a smaller, more complex remaining workforce buys is different. They need people who can be trusted with an exception, who will still be there in eight months, and who do not need three weeks of supervision before they are useful.

That means the things a staffing firm gets measured on shift. Time to fill matters less than quality of fill. Volume delivered matters less than attrition at ninety days. And the screen has to test judgement and communication rather than confirming that someone is available and within band.

Firms that make this shift find fees hold up, because a role that is hard to fill supports a fee that a role anybody could fill does not. Firms that do not make it end up defending a rate on work that is disappearing.

How to reposition without overreacting

Audit which of your BPO revenue is transactional. If a large share of your placements are into rules-based, scripted roles, that is the exposure. Know the number before somebody else tells you.

Follow the work into the GCC. Same parent company, different buyer, permanent headcount. Our piece on the India GCC landscape covers what that buyer expects.

Raise your screening bar. Judgement roles fail on communication and context, not on eligibility. A CV screen will not catch that, and neither will a five-minute call that only checks availability.

Stop competing on fee for volume roles. That is the segment automation is pricing down, and winning it faster does not help.

Candidate activity timeline showing an automatically logged call written to the record with the stage move attached
Fig 2Calls, meetings and messages written to the record without anyone typing.

Three mistakes firms make reading market data

Numbers like the ones above get quoted in strategy decks and then change nothing. Three reasons that happens.

Treating a market size as an addressable market

A sector employing millions of people is not a sector where millions of placements are available to agencies. Internal talent teams, direct applications and referrals take the majority of any mature hiring market. The agency-addressable share is ramp-ups, niche roles and volume spikes, and it is a fraction of the headline.

Confusing a growing market with an easy one

Fast growth attracts suppliers. A segment growing at thirty percent a year usually has more agencies chasing it than one growing at five, which means fee pressure rises alongside demand. Growth tells you where to look, not where it will be comfortable.

Planning around the trend instead of the capability gap

The useful question is not which segment is growing, it is which segment is growing that you can actually serve better than the incumbent supplier. A firm with no history in a domain entering it because the chart looks good will lose to the firm that has placed there for six years.

Frequently asked questions

Is BPO dying because of AI?

Not as a whole. Transactional, rules-based BPO is compressing because that work is defined precisely enough for software to perform. Judgement-heavy process work involving exceptions, escalation and context is not compressing in the same way.

What happens to BPO work that gets automated?

The routine portion disappears and the complex remainder often moves in-house, frequently into a global capability centre. The work does not vanish; the commercial relationship changes from a vendor contract to direct headcount.

How does BPO decline affect staffing firms?

Vendor accounts shrink on routine roles first, the remaining roles are harder to fill because they require judgement, and the growth reappears as GCC demand bought by a different function at often the same parent company.

Should staffing firms move away from BPO clients?

Not away, but towards the parts that are growing. Audit what share of your BPO revenue comes from transactional roles, and build a relationship with the talent function rather than only with procurement.

Is volume hiring going away?

No. Centres still need staffing, ramps still happen and attrition still needs replacing. What changes is the role mix, which skews towards judgement and raises the screening bar rather than removing the need for volume delivery.

What is the difference between BPO and GCC?

BPO is work bought as a service from a vendor. A GCC is the same work performed by employees of the parent company in an offshore unit it operates directly. The distinction determines who your buyer is and how the fee works.

The question worth answering internally

Work out what share of your placements last year went into roles a well-configured piece of software could now do. That number is your exposure, and it is knowable in an afternoon.

Then look at whether the same parent companies have GCC operations in India. In most cases they do, the headcount plan is growing, and nobody at your firm has spoken to that buyer.

See how volume delivery changes

Bring a volume mandate you are working now and we will show you what filtered screening produces against it.

Book a demo

Founder of Sortinghat, an AI-native ATS and CRM for staffing, search and RPO firms. Writes about recruiter capacity, sourcing economics and what actually changes when AI reaches a delivery desk. More about the author