A customer service outsourcing RFP, or request for proposal, should help you choose an operating model, not simply collect presentations. Its purpose is to make suppliers answer the same important questions about scope, capacity, customer outcomes, accountability and cost.
The difficulty is that apparently comparable bids often describe different services. One supplier prices staffed time. Another prices productive time. One includes coaching and quality review. Another assumes your internal managers will provide them. A lower headline price may therefore represent a smaller service rather than a more efficient one.
For a chief operating officer, customer-experience director or procurement lead, the useful question is: what evidence would let us defend this decision after the service starts? Build the RFP around that question.
Decide what you are buying before asking for a price
Start with the business problem. It might be inconsistent coverage, an ageing backlog, pressure on internal managers or difficulty maintaining service during growth. State the problem without prescribing a solution before the evidence is available.
Then record the customer promise you need to protect. Include the contact reasons involved, what customers should be able to achieve and what the outsourced team will be authorised to resolve. Handling an enquiry, qualifying it and completing it are different responsibilities.
Decide what remains internal. Product ownership, policy decisions, specialist approvals and complaints requiring senior judgement may still need a client-side owner. Outsourcing delivery does not remove the need to govern those decisions.
If the operating model itself is unresolved, use contact centre consulting before turning assumptions into tender requirements. Our broader outsourced customer-service guide explains the choices that should precede procurement.
Give every supplier the same demand picture
An annual contact total is not a staffing brief. Provide a dated, appropriately anonymised demand baseline showing when work arrives, through which channels and for which reasons. Identify seasonal events, launches and known interruptions that make historical demand unrepresentative.
Separate new contacts from reopened work, transfers and repeat enquiries where the source data supports that distinction. Explain any missing data. A supplier should not have to guess whether an apparent increase reflects customer demand or a change in ticket recording.
The response pack should include:
- Covered channels, contact reasons and customer groups.
- Arrival patterns across the operating calendar and relevant time zones.
- Handling-time definitions and the work included in those measurements.
- Outstanding work by age, priority and ownership.
- Language and knowledge requirements supported by actual demand.
- Forecast assumptions and the process for approving a change.
Ask bidders to state what their proposed staffing can support and where they need further evidence. Compare their assumptions explicitly. A confident answer built on an untested average is weaker than a qualified answer that identifies the missing operational detail.
Write requirements as evidence questions
“Describe your commitment to excellent service” invites a polished paragraph. “Show how a customer asking for a refund reaches an authorised decision when the normal approver is unavailable” tests an operating process.
For each requirement, ask for the proposed method, accountable role, evidence, client dependency and exception. Give bidders a place to state where they cannot meet the requirement. Hidden exceptions become expensive after selection; visible exceptions can be evaluated.
Download the customer service RFP response matrix (CSV). The worksheet connects requirements with evidence and pricing references so commercial and operational reviewers can assess the same proposal.
Keep mandatory conditions separate from scored preferences. If a requirement is genuinely necessary, a good presentation elsewhere should not compensate for its absence. Procurement, security and legal specialists should agree the appropriate conditions and contractual wording for your business.
Use shared scenarios to test the proposed service
Ask shortlisted suppliers to work through the same representative cases. Include a routine request, an exception, a repeat contact and an issue that crosses an operating-hours boundary. Use sanitised examples rather than disclosing identifiable customer records during an ordinary sales demonstration.
For each scenario, ask who receives the contact, what information they see, what they can decide and how the next owner receives the work. Require the supplier to explain what the customer hears while another team is acting.
Evaluate the explanation against the actual requirement, not the sophistication of the slide deck. A demonstration should reveal dependencies and limits as well as capabilities. It should also show what happens when a workflow fails or knowledge is missing.
The ISO 18295-1 public overview describes a service-requirements framework covering both internal and outsourced contact centres across channels. That scope is a useful reminder to assess the complete service, not only agent availability. Referencing the standard does not establish that a bidder, or The Cattalyst, holds certification.
Define quality without rebuilding your entire contract
Include the operational definitions that bidders need to price and staff the service. Response targets, resolution authority, quality review and escalation coverage all affect the delivery model. A supplier cannot credibly commit to an outcome while the necessary access or approval route remains undefined.
Use the existing customer service SLA template to settle clock rules, exclusions and ownership. Link the RFP to a proposed service schedule rather than repeating inconsistent definitions in several documents.
For quality assurance, explain the types of error that matter and how assessment will be calibrated. Ask who reviews interactions, who coaches the team and how operational changes are verified. Our quality-assurance scorecard guide provides the detailed measurement approach.
Avoid using a single average as the entire service promise. Request visibility into the distribution of waits, unresolved cases and repeated problems. A reassuring overall result can coexist with poor service for a particular customer group or busy interval.
Make the pricing schedule genuinely comparable
Give each bidder the same pricing structure to complete, while allowing an explanation of its preferred commercial model. Require the unit, inclusions, exclusions, billing rules and assumptions for every charge.
Separate recurring delivery from mobilisation and changes. Ask where leadership, recruitment, training, quality monitoring, workforce planning, technology and reporting sit in the proposal. Identify client-provided systems and the internal time required to operate the arrangement.
The comparison should answer:
- Is the quoted unit a scheduled hour, productive hour, interaction or dedicated capacity commitment?
- How are absence, training, breaks, coaching and other non-contact activities treated?
- What minimum commitments or volume conditions affect the price?
- What happens when channel mix, coverage or complexity changes?
- Which launch, integration and exit activities are separately charged?
- Which taxes, currency assumptions and third-party charges need specialist review?
The UK Government Sourcing Playbook discusses whole-life costing and evaluation that avoids a simple bias towards the lowest bid. It is public-sector guidance, not an obligation imposed on a private US buyer. The commercial principle remains useful: compare the service and risk you are actually purchasing.
Test staffing and location assumptions together
Do not evaluate location as a price label detached from the work. Consider coverage, language, customer expectations, recruitment, management availability, infrastructure and the access arrangements your organisation can support.
Ask whether proposed resources are dedicated, shared or dependent on another team. Establish which leadership and specialist roles are available during the actual service hours. A named manager on an organisation chart is not evidence of escalation cover on a late shift.
Where after-hours customer support is included, test handoffs across calendars and time zones. State whether the team resolves the case, triages it or records it for the next shift. Those are different customer promises with different operating requirements.
Supplier capabilities should be matched during selection. Do not assume that every location or partner offers every channel, skill or technical arrangement simply because the supplier has a broad international footprint.
Review the dependencies that could undermine the bid
Ask for a responsibility record showing what the supplier needs from you before launch and during normal delivery. Knowledge approval, system access, policy decisions, forecast updates and incident ownership should each have an accountable client role.
Bring security and legal reviewers into the process early enough to influence the decision. Give them the proposed data flows, access model, subcontracting arrangements and relevant operating locations. An operational article cannot settle your legal obligations or approve a supplier's controls.
Request evidence appropriate to the risk, then validate the scope of that evidence. A document covering a different entity, site, system or period may not answer your question. Record outstanding issues rather than allowing “under review” to become an assumed approval.
Also examine the financial and continuity risks that could affect delivery. Procurement and finance should agree the level of diligence required. Ask how the service would be maintained or transferred if a critical dependency became unavailable.
Agree evaluation rules before reading the sales narrative
Develop a scoring method tied to the service requirement. Record what an acceptable answer looks like, what stronger evidence looks like and who evaluates each area. Keep enough detail to explain why two proposals received different assessments.
Have operational, commercial and specialist reviewers assess their areas before a joint moderation discussion. Preserve the reasons behind the final decision, especially where a low price depends on a disputed assumption or a preferred bidder requires an exception.
Use clarification to resolve ambiguity, not to invent a different requirement for each supplier. Log material questions and apply the agreed procurement process consistently. Let qualified procurement advisers determine the rules applicable to your organisation.
The decision record should explain the chosen model, material risks, assumptions needing validation and conditions that must be satisfied before launch. Selection is not the same as readiness.
Make the handover from procurement to operations explicit
The people negotiating a bid are not always the people running the service. Before award becomes mobilisation, transfer the requirements, assumptions, exceptions, pricing definitions and commitments into a controlled operational record.
Require the incoming delivery lead to confirm what has been agreed and what remains unresolved. Name the client sponsor and the people authorised to approve access, knowledge and readiness. Otherwise procurement can close a deal that operations cannot safely launch.
Use the customer service outsourcing transition plan to turn the selected proposal into evidence-based acceptance gates. Our outsourcing implementation process connects partner selection with preparation, launch support and ongoing review.
Build exit requirements into the discussion at the start. Ask how knowledge, records, access and unresolved work would be transferred if the arrangement ended. Exit planning is part of responsible service ownership, not an assumption that the relationship will fail.
How The Cattalyst can help frame the decision
The useful starting point is a discovery conversation about your demand, customer promise and current constraints. We can help clarify the operating requirement, match potential partners to that requirement and identify the preparation and review work the arrangement needs.
That is not a fixed package or a promise that outsourcing is the answer. If the main constraint is an unresolved policy, an unreliable internal handoff or a system nobody can access, changing the supplier alone will not solve it.
Explore customer service outsourcing if you are ready to define the delivery requirement. Bring your draft scope, current reporting and the decisions your leadership team needs to make. The first useful output is a clearer brief, not a longer list of providers.
Frequently asked questions
What should a customer service outsourcing RFP include?
Include the service scope, demand evidence, coverage, authority limits, system dependencies, proposed measures, pricing definitions, launch requirements and evaluation process. Give suppliers a structured way to disclose assumptions and exceptions. A consistent response format makes the differences between proposals easier to examine.
Should we choose the lowest-priced outsourcing proposal?
Not without confirming that the bids cover the same work, risk and responsibilities. Review recurring and transition costs alongside client-side management effort and exclusions. A lower unit price does not establish a lower complete operating cost or an appropriate service model.
How much customer data should we share during procurement?
Share only the information needed for the stage and purpose, using aggregated or appropriately sanitised material where possible. Your security, privacy and legal teams should approve any access or transfer of identifiable records. A supplier presentation is not a reason to grant production access.
Can an RFP compare internal and outsourced delivery?
Yes, if the scope, demand, service expectations and cost definitions are consistent. Include the retained internal responsibilities in the outsourced option. Comparing a complete internal operation with only an external agent rate creates a misleading decision.
When should we involve the people who will run the service?
Before the requirements and evaluation criteria are fixed. Operational leaders need to test whether the proposed service is deliverable and understand the assumptions they will inherit. They should also participate in the transfer from supplier selection into launch preparation.
About the author
Oliver Catt is the founder of The Cattalyst. He has spent 25 years inside contact centres, customer service, sales and training operations, and now helps organisations develop their leaders and build outsourced teams through a global partner network.
Start a conversation with Oliver
