WFM guideProcurement

Contact centre vendor management

Q: How do you manage a BPO vendor relationship in a contact centre?

BPO vendor management requires a structured governance cadence at three levels: operational (weekly), tactical (monthly), and strategic (quarterly). Weekly operational reviews cover the prior week's SLA performance, volume delivery, and quality scores — attended by operations managers on both sides, resolving in-week issues without escalation. Monthly tactical reviews cover rolling performance trends, open action items, change requests, and forward-looking capacity planning — attended by heads of operations. Quarterly strategic reviews cover contract performance against KPIs, relationship health, commercial terms, and strategic alignment — attended by senior leadership including commercial stakeholders. SLA breaches must be formally logged, root cause documented by the BPO, and remediation agreed — not verbally acknowledged and forgotten. Service credits should be claimed where contractually entitled; not claiming them signals to the vendor that SLA performance is not monitored.

Q: What should a contact centre technology vendor review include?

A contact centre technology vendor review should cover: system availability and uptime against contracted SLA; incident log review (incidents that occurred, time to resolution, root cause analysis); open support ticket status and ageing (tickets open more than 30 days should be individually reviewed); change control log (changes implemented in the period, any that caused incidents); product roadmap update (what is coming in the next 2-3 releases that affects the contact centre's operations); and commercial review (upcoming renewals, licence changes, any contractual matters). The vendor should provide a formal written report before the meeting — a meeting without a pre-read report is less structured and produces less accountability.

Most contact centre vendor relationships underperform because of weak governance, not bad contracts. The vendor delivers what they are held to account for in formal review meetings. No formal reviews means no accountability.

Two vendor categories, two governance models

BPO / outsourced operations vendors

A BPO vendor delivers people and operational capability — agents, team leaders, and management who handle contacts on behalf of your brand. Governance focuses on SLA delivery (service level, quality, AHT, adherence), people management (attrition, ramp quality, absence), and operational compliance (data protection, regulatory requirements, brand standards).

·SLA delivery: service level, quality score, AHT, FCR

·People metrics: attrition, absence, ramp time to productivity

·Compliance: GDPR, regulatory, brand and scripting standards

·Commercial: volume actuals vs. contract, credit claims

Technology vendors

Technology vendors supply software platforms — ACD/telephony, WFM, CRM, QA, workforce analytics. Governance focuses on system availability (uptime SLA), incident management, support responsiveness, change control, and product roadmap alignment with operational requirements.

·Availability: uptime SLA, planned maintenance windows

·Incident management: time to detect, restore, and resolve

·Support: ticket response and resolution time SLAs

·Roadmap: upcoming product changes affecting operations

BPO governance cadence

Weekly operational review

Operations managers (client) + Operations managers (BPO)

Agenda

→Prior week SLA performance: service level %, quality score, AHT, adherence — vs. contracted targets
→Volume actuals vs. forecast: was the BPO staffed correctly for actual volume?
→Open incident log: incidents from the prior week, status of remediation
→Action items: status of actions from the prior week's meeting
→Upcoming week: forecast volume, events, planned outages or maintenance

Required output

Meeting minutes with action items, owners, and deadlines. SLA performance documented in writing — not verbal review.

Failure mode

Meetings become informal catch-ups. SLA performance is discussed verbally without documentation. The same issues recur weekly without escalation.

Monthly tactical review

Head of operations (client) + Head of operations (BPO)

Agenda

→Rolling 4-week SLA performance trends: is performance improving, stable, or deteriorating?
→Open action item review: items from prior months still outstanding — escalate if overdue
→Quality calibration review: are the client and BPO calibrated on quality standards? Are scores comparable?
→Change requests: any operational or contractual changes required in the next 60 days
→Capacity planning: forecast for the next 60-90 days, BPO headcount implications
→Complaints and incidents: any customer complaints or regulatory incidents involving BPO agents

Required output

Formal monthly performance report signed by both parties. Change request log updated.

Failure mode

Monthly review covers the same ground as the weekly review. No forward-looking planning. Change requests are discussed but not formally logged or tracked.

Quarterly strategic review

Senior leadership including commercial/legal representatives (both sides)

Agenda

→Contract performance: rolling 12-month SLA performance vs. contracted targets. Outstanding service credits due.
→Relationship health assessment: candid discussion of relationship quality, communication, and escalation effectiveness
→Commercial review: volume actuals vs. contract, pricing, upcoming renewals or contract changes
→Transformation agenda: technology changes, channel shifts, automation impacts on BPO volume and skills
→Market benchmarking: is the BPO's performance and pricing competitive vs. the current market?
→Risk review: key-person dependency, data protection, regulatory changes, contract exit provisions

Required output

Quarterly relationship scorecard. Commercial reconciliation. Agreed strategic priorities for the next quarter.

Failure mode

Quarterly reviews are scheduled but cancelled or deferred. When they do occur, they are too operational (covering the same ground as monthly reviews) rather than strategic.

Technology vendor review: what to cover

Review item	What to review	Escalation trigger
System availability / uptime	Actual uptime % for the period vs. contracted SLA. Include planned maintenance — is it occurring within agreed windows?	Any availability below contracted SLA. Any unplanned outage exceeding the contracted recovery time objective (RTO).
Incident log	All incidents in the period: severity, time to detection, time to restore, root cause analysis, prevention action. Were all incidents communicated to the client within contracted SLA?	More than one P1/P2 incident in a rolling month. Incidents where RCA is not completed within 5 business days. Recurring incidents with the same root cause.
Support ticket ageing	Open tickets by age: tickets over 14 days, over 30 days, over 60 days. Is the vendor resolving tickets within the contracted SLA for each severity level?	Any ticket open more than 30 days without an agreed resolution date. Support SLA breach rate above 5%.
Change control	Changes deployed in the period: did any change cause an incident? Were all changes through the agreed change control process? Are emergency changes logged and reviewed?	Change that caused an incident was not through the agreed process. Emergency changes are becoming routine (signal of poor change planning).
Product roadmap	What is coming in the next 2-3 releases? What is being deprecated? Are any upcoming changes going to require the contact centre to re-train, reconfigure, or change process?	A breaking change in the roadmap that the contact centre was not given sufficient notice of. A feature the contact centre depends on being removed.
Commercial review	Upcoming licence renewals. Any usage-based costs approaching thresholds. Any contractual changes the vendor is proposing.	Renewal approaching with less than 90 days notice. Proposed price increase not in line with contracted escalation clauses.

Signals that a vendor relationship needs restructuring

SLA breaches are acknowledged but not remediated

The vendor apologises for SLA failures and provides RCA documents, but the same failures recur. The contact centre continues to accept these without exercising service credit entitlements or escalating to formal PIP. This pattern signals that the vendor is not sufficiently incentivised to change.

The contact centre team no longer trusts vendor data

Vendor-reported SLA performance diverges from internally measured performance. The contact centre maintains its own parallel measurement because it cannot rely on vendor reporting. This is a significant relationship breakdown — data credibility must be established or the contract is unmanageable.

Escalations never resolve

Issues escalated to the vendor's account team are acknowledged and then either ignored or slowly deprioritised. The contact centre team feels that escalation is futile and stops escalating, allowing issues to persist.

The vendor's account team is constantly changing

High vendor-side account team turnover means the contact centre must repeatedly re-educate new account managers about operational context, history, and requirements. Relationship continuity, institutional knowledge, and trust are repeatedly reset.

Contract renewal discussions are always deferred

The vendor does not engage constructively in contract renewal discussions until the last moment, reducing the contact centre's ability to benchmark against alternatives or negotiate effectively. This is a vendor-side negotiation tactic that should be pre-empted by initiating renewal 12 months before expiry.

Vendor management questions

How do you manage a BPO vendor relationship in a contact centre?

Three governance levels: weekly operational reviews (ops managers both sides, prior week SLA, volume actuals, incident log); monthly tactical reviews (heads of operations, rolling trends, quality calibration, change requests, capacity planning); quarterly strategic reviews (senior leadership, contract performance including service credits, commercial review, market benchmarking, strategic alignment). Every meeting produces documented minutes with named actions and deadlines. SLA breaches must be logged in writing and service credits claimed where contractually entitled.

What should a contact centre technology vendor review include?

Six items: system availability vs. contracted uptime SLA; incident log (detection time, restoration time, RCA, prevention action); support ticket ageing (tickets over 30 days reviewed individually); change control log; product roadmap (upcoming changes that affect the contact centre); and commercial review (renewals, usage-based cost thresholds, proposed changes). The vendor should provide a written pre-read before the meeting — meetings without pre-read reports produce less accountability.