insights

November 16, 2026

Call Center Outsourcing RFP Template and Scorecard

Concept illustration of a buyer and support lead reviewing an RFP in a branded contact center workspace.

A call center outsourcing RFP should make competing proposals answer the same question: who will handle your customers' work, under which rules, at what total cost, and how will you know the service is working? A list of languages and an hourly rate cannot settle those points. Give every bidder the same operating picture and ask them to show the evidence behind their answer.

Use the sections below as a working template. Replace the bracketed fields with your own volumes and policies before sending it. The sample scorecard is a decision tool you can adjust; it is not a market benchmark.

First decide what the provider will own

Before you ask for prices, write down what happens after a customer calls, chats, or emails. Put those outsourcing requirements in the RFP so every bidder prices the same work. Which requests can an agent resolve? Which need a supervisor, product specialist, warehouse, or finance approver? Who owns a case that crosses a shift? A proposal that covers only contact time may leave all of that follow-up with your team.

For a first version, include a short list of contact reasons from recent tickets, the expected hours and time zones, each language by channel, your current systems, and the work that must stay in-house. Mark estimates as estimates. If volume is uncertain, give all bidders the same low, expected, and peak scenarios. A practical seven-step sequence is to define the scope, set acceptance measures, issue one response format, compare complete prices, score evidence, test finalists, and document the award decision. Our provider selection checklist helps narrow the shortlist before you issue this document.

Copy this scope into your call center outsourcing RFP

The buyer should complete the left column and require the bidder to answer the right column in the same format. “Available” is not an answer when the issue is who actually performs the work.

Buyer suppliesBidder must answer and show
Channels and hours: [voice/email/chat], [time zones], [holidays], [peak windows]Staffing model by hour and channel; backup coverage; after-hours ownership; which work continues after a contact ends.
Demand: [monthly contacts by reason, channel, language], [handle time if known], [seasonality]Capacity assumptions, ramp time, and the price effect if the actual mix differs.
Languages and locations: [required language by queue and hour]Who serves each queue, how language skill is assessed, and how the bidder verifies coverage during absence or spikes.
Systems: [CRM, telephony, knowledge base, order tools]Which system is the source of truth, required integrations, licensing ownership, and how a transferred case retains its history.
Decision rights: [refund limit, exception rules, technical escalation owner]Agent permissions, approval steps, emergency routing, and the point at which the provider must stop acting.
Service targets and acceptance: [customer-facing outcome, response window, escalation trigger, review method]Define the event that starts and stops each measure, time zone, exclusions, evidence source, owner of open cases, and what happens when a target is missed.

Service scope and forecast

Ask bidders to map each major contact reason to an action: resolve, gather facts and route, or leave with the buyer. Request a named owner for open cases at shift change. For a BPO RFP, include training, team leads, quality review, reporting, and after-contact work in the scope table instead of assuming those activities come with an agent hour. Where your forecast is thin, ask for the vendor's assumptions in a separate column so they remain visible during comparison.

People, supervision, and systems

Request the proposed ratio of agents to supervisors, how replacements are trained, and who signs off on a new agent's access. Ask for an anonymized example of a quality review and a cross-shift handoff. If the bidder proposes AI-assisted responses, require a description of what AI drafts, what it can send, and which decisions stay with an authorized person. A polished demo is less useful than seeing one real workflow from customer contact to final record.

Security and escalation

State which customer data agents will see, which fields they may change, where recordings and transcripts reside, and when access is removed. Ask for the bidder's access-control evidence, incident-notification procedure, subcontractor list, and a named security contact. The FTC's business guide to protecting personal information specifically advises businesses to investigate a call center contractor's security practices, write expectations into the contract, verify compliance, and require notice of security incidents. The NIST supplier-risk guide is a useful way to frame supplier requirements; tailor the controls to the data and systems in this RFP.

Service targets and acceptance

Give each bidder the same target definitions before asking for a commitment. A first response, a resolved contact, and a case accepted for closure are different events. For each target, specify the channel, clock start and stop, time zone, excluded periods, source system, review sample, and who can approve an exception. Ask the provider to show how a missed target is found, corrected, and reported. If you do not yet have a defensible baseline, request the measurement method first and agree the numeric target during the pilot.

Transition, reporting, and exit

Require a dated plan for knowledge transfer, system access, training, supervised practice, go-live, and escalation testing. Specify the reports you need: contact volume, open-case age, quality findings, approvals pending, and customer outcomes. Ask how the provider will return case records, revoke access, and hand open work back to you at the end of the contract. An exit plan written before launch is easier to test than one requested after a relationship has gone wrong.

Require bids to use the same pricing units

Ask every bidder to price the same baseline, peak, and after-hours scenarios. A per-agent quote and a per-interaction quote can both be valid, but they do not become comparable until you include supervision, training, technology, setup, quality review, minimum commitments, overtime, and work after the contact.

Cost lineBidder response
One-time setup and migration[amount, currency, assumptions, payment date]
Recurring staffing or usage[unit, unit definition, included volume and hours]
Supervision, QA, reporting, and training[included or itemized, with limits]
Software, telephony, storage, and integrations[license owner, usage charges, exclusions]
Peak, holiday, overtime, and additional language coverage[trigger and unit price]
Transition out and data export[format, timing, charge]

Compare the total over the same period and demand scenario, then list every exception below the total. Do not convert a low hourly number into a claim of savings until you know what it includes. A BPO call center can organize staffing and supervision, but the agreement must say which of those responsibilities the provider actually accepts.

Score evidence and protect non-negotiable controls

Publish the evaluation method with the RFP so bidders know what to substantiate. For example, score each area from 0 to 5, multiply by its weight, and divide by 5. A 3 out of 5 on a 25-point area contributes 15 points. The weights below are an illustrative buyer choice; change them before issue to reflect your operation.

AreaExample weightWhat earns a high score
Scope and workflow fit25A clear owner and procedure for your actual contact reasons and exceptions.
Staffing, QA, and continuity25Specific schedules, training evidence, backup arrangements, and measurable review.
Security and data handling20Demonstrated controls for your data, written incident process, and workable access removal.
Total cost on the common scenario20Complete, comparable pricing with assumptions and change triggers visible.
Transition and exit10Dated milestones, acceptance evidence, data return, and open-case handoff.

Some requirements should be pass or fail, regardless of the weighted total: access to regulated or sensitive data without agreed controls, inability to meet a required language window, or no workable route for urgent escalation. Record the evidence for each pass. This prevents a low quote from compensating for a missing control. U.S. federal service purchasing uses a written statement of work and evaluation criteria as a discipline; the FAR provision is an example of that structure, not a rule imposed on a private buyer.

Run three pilot scenarios before expanding the work

A pilot should test the work the contract claims to cover. Agree on the sample cases, the records to inspect, the owner for failures, the service-target measurement method, and the decision to expand or correct the service before the pilot starts. Do not set a pass percentage without a baseline and a sample that can support it.

  1. Routine resolution: Give an agent a common order or account request. Check the response, the system record, and whether the customer received the promised next step.
  2. Approval handoff: Give an agent a request outside their refund or policy authority. Check whether they stop, send the facts to the right approver, and keep the customer informed without claiming approval.
  3. Internal milestone without customer recovery: Give the team a case where a part has shipped or an internal task shows “done,” but the customer's problem remains. Check that the case stays open, the technical owner gets the remaining issue, and closure waits for the agreed evidence.

That third test reflects a real boundary from an anonymized medical-device support case in India. A spare part was dispatched by July 21 and replaced by July 24, yet a follow-up found that specified microscope oil still needed replacement. The support agent maintained a Level III escalation through later follow-ups; technical staff completed verification before the customer confirmed stable operation and the case closed on August 11. For your own RFP, define acceptance so an internal milestone cannot close a case while the customer's issue remains open.

Send the RFP with a clear response format

Give bidders a deadline, one channel for clarification questions, a response table matching the sections above, and a request to label every assumption and exclusion. State how you will evaluate a non-answer. After scoring, use finalist discussions to test the most consequential gaps with the same scenarios for every vendor.

The result you want is a proposal you can operate against: defined work, documented limits, comparable cost, and a way to tell whether the customer actually got help. If you are ready to discuss a scope with Callnovo, contact our team with your contact reasons, hours, languages, and current systems.

References

talk to the people behind the field notes

Request a quoteContact us