Outsourced call center and AI voice agent: a joint governance model

The short answer

When an outsourced call center and an AI voice agent work together, the biggest risk is not technical but lost accountability: when the agent gives a wrong answer the contractor says "that's your AI", and when the contractor's operator makes a mistake it's "the agent didn't pass the information on properly". To prevent this, five things must be written down in advance: which call goes where, who is responsible for what at handoff, who owns the scenario and knowledge base, who has access to data, and how quality is measured.

This article shows how to set up the joint model, a responsibility table, SLA (service level agreement) clauses and a weekly governance routine.

Three typical models

1. 1Agent in front, contractor behindEvery call reaches the AI agent first; simple questions end there, the rest go to the contractor's operators.
2. 2Split by hoursThe contractor during business hours; the agent out of hours and at peaks.
3. 3Split by call typeCertain numbers or call types with the agent, others with the contractor.

The choice depends on call volume, the pricing model of the contract with the contractor (per call, per minute or per operator) and the complexity of call types. If pricing is per call, the agent taking simple calls directly affects the contractor's revenue — this must be discussed openly in the contract.

A responsibility table

• The agent's scenario and knowledge base — the client (your company)
• The contractor's operator scripts — written together, approved by the client
• Handoff rules: when and with what information — the client, in consultation with the contractor
• Taking and resolving handed-over calls — the contractor
• The phone line and routing rules — the client or an agreed party
• Logging and analysing incidents — both parties, one shared log

The handoff point

The handoff from the agent to the contractor's operator is the most sensitive point of the joint model. When the operator takes the call, they must see what the agent collected — summary, request, customer details. If they do not, the caller tells the story again and each side blames the other. The handoff format should be written into the contract's technical annex: which fields, in which system, how quickly they appear.

SLA clauses

• Service level for handed-over calls — for example, the share answered within a set number of seconds
• The caller not having to repeat information on a handed-over call — via sample checks
• Callback promises kept on time
• Incident response time — by severity level
• Reporting: which indicators, how often, in what format

Write the SLA separately for the agent and the contractor. The agent's indicators (resolution, correct handoff, observed errors) are the client's responsibility; the indicators after handoff are the contractor's.

Data access

The contractor's operators need to see customer data, but only what their work requires. Who listens to recordings, who sees only transcripts, who only summaries — this is set by roles and by the contract. Processing, storing and returning or deleting data at the end of the contract must follow local rules and be checked with a lawyer.

Quality: two layers

In a joint model quality is measured in two layers. Layer one — the agent: correct answers, correct handoff, keeping to the boundary. Layer two — the contractor's operator: how they took the handed-over call and whether they solved the problem. It helps to read both layers together on the same call: if the customer is unhappy, where did the problem start — with the agent, in the handoff, or with the operator?

A weekly governance routine

1. 1ReportBoth sides' indicators in one table: agent, handoff, contractor.
2. 2Sample calls5–10 calls reviewed together — especially handed-over calls and ones that became complaints.
3. 3ChangesScenario, knowledge-base and script changes — who and when.
4. 4IncidentsOpen incidents and their status.

A feedback channel for the contractor's operators

The contractor's operators are the first to see the agent's mistakes — after a handoff the caller says "the bot told me something different". That signal must reach the client. Set up a shared log or a simple form: call, topic, one sentence. If the signal stays in the contractor's internal system, the client cannot fix the agent's knowledge base.

Illustrative example: a telecom operator

Not a real customer case. A company's support line is with an outsourced contractor. The company puts an AI agent in front: balance, tariff and payment-point questions end with the agent, while technical problems and complaints are handed to the contractor. The contract with the contractor was priced per call — in the new contract, pricing and SLA for handed-over calls are written separately.

In the first month the shared log recorded 14 signals: 9 about outdated tariff information in the agent's knowledge base, and 5 about the summary appearing late on the contractor's screen at handoff. The client fixed the first, the integration party the second — each in line with the responsibility table.

When the contract ends

In a joint model the exit plan is also written in advance: when the contractor changes, the scenario, knowledge base and call history stay with the client, and the handoff format to a new contractor stays the same. That keeps the client from depending on a single contractor.

Common mistakes

• Giving scenario ownership to the contractor
• Not writing the handoff format into the contract
• Combining agent and contractor indicators into one number
• Not discussing the change to the pricing model
• Not setting up a shared channel for operators' signals

Limits

A joint model requires a contract, technical integration and governance; without them two systems run side by side but not together. Rules on data processing and transfer to third parties differ by country and must be checked with a lawyer. This article is not contract advice.

A joint model with Vexvon

Vexvon AI Call Center works on top of your existing SIP or PBX line, and routing rules decide which call goes to the agent and which to an external number — by business hours, dialled number and caller number; the rule can be checked in the simulator. The agent's scenario and knowledge base are under your control in the panel, and a difficult call is passed to a live operator. Every call's transcript, summary and recording stay in the panel — shared evidence for joint quality review.

Checking the quality of the contractor's operator calls is covered in outsourced call center quality, and the role split with an in-house team in AI and human call center team.

First step

Write the responsibility table in six rows and discuss it with the contractor at your next meeting. Every row you cannot agree on is a clause to add to the contract. More articles are in the call center operations section; to discuss the joint model, get in touch.