OLYMP LogoOLYMP
Contact
Template

Customer support outsourcing RFP template

A request for proposal only works if every provider answers the same scope in the same format. Copy the eight sections below, add your own numbers, and score the answers with the weighted matrix. It is written for teams of 5 to 50 agents, where a 60-page enterprise tender would cost more time than it saves.

Send us your RFPSee the sections
How to choose a partnerSLA guidePricing modelsSupport KPIs

What should a customer support outsourcing RFP include?

A customer support outsourcing RFP should describe your goals, scope of work, contact volumes and hours, systems and data, and the service levels you expect, then tell providers exactly what to submit, which commercial model to price, the timeline and how answers will be scored. Real volumes and one pricing model make the proposals comparable.

Sections
Eight: four about your operation, four about the response
Providers to invite
Three to five
Typical timeline
Four to six weeks to a decision, then a pilot
Scoring
Weighted matrix, weights published in the RFP

The eight sections of the RFP

Sections 1 to 4 describe your operation, so every provider prices the same work. Sections 5 to 8 tell providers what to send back and how you will decide.

  1. Company and goals

    Section 1

    Who you are, what you sell, who your customers are and why you are outsourcing now: cost, coverage hours, languages, growth or quality. Name the two or three outcomes that would make the project a success after six months.

  2. Scope of work

    Section 2

    Channels (phone, email, chat, social, tickets), contact types with examples, languages, and what stays in-house. Say whether you need technical support, and at which tier, or back-office tasks such as refunds and order changes.

  3. Volumes and hours

    Section 3

    Contacts per month by channel for the last twelve months, the busiest hours and days, seasonal peaks, average handling time if you track it, and the hours and time zones you need covered. Real numbers here are what make quotes comparable.

  4. Systems and data

    Section 4

    Helpdesk, telephony, CRM and knowledge base, who provides the licences, and what personal data agents will see. State where your customers are, because that decides which data protection rules apply to the transfer.

  5. Service levels and quality

    Section 5

    Your current KPIs and the targets you expect, how quality is scored today, and how you want results reported. Ask providers to propose targets they would commit to, rather than accepting yours without question.

  6. Commercial model

    Section 6

    Ask for a price in one stated model (per agent-hour, per dedicated agent per month, or per contact) with everything that is included and excluded, setup costs, minimum commitment, notice periods and how prices change over the contract.

  7. What to submit

    Section 7

    A proposal of a fixed maximum length, a staffing plan with roles and ratios, a week-by-week launch plan, two or three references from similar clients, the standard contract and data processing agreement, and the security documents you require.

  8. Timeline and evaluation

    Section 8

    The deadline for questions, the submission date, when you will shortlist, the date of provider presentations and the decision date. Publish the scoring weights so providers know what matters to you.

21 questions to ask every provider

Put these in section 7 and ask for a direct answer to each. Vague answers are information too.

  • People and hiring

    Do you employ the agents directly? How do you recruit and test them, including language level? Who will lead our account and how many agents will each team lead manage? What was your agent attrition over the last twelve months, and how do you calculate it?

  • Training and launch

    How long is initial training for work like ours, and who delivers it? How do you keep knowledge current when our product changes? What does the first month look like week by week, and when do agents take live contacts?

  • Quality and reporting

    How many conversations per agent do you review each week? Can we score alongside your QA team and calibrate together? Which reports do we get daily, weekly and monthly, and are they built from our systems or yours?

  • Security and data

    Where will our data be accessed from, and by whom? How are accounts, devices and access logs managed? Will you sign our data processing agreement, and what transfer mechanism do you use? Which certifications do you hold, with scope and expiry date?

  • Pricing and commitment

    What exactly does the quoted rate include: management, QA, workstations, software, holidays and sick cover? Are there setup or recruitment fees? What is the minimum team and term? How much notice do you need to add or remove agents?

  • Continuity and exit

    What happens when an agent leaves or is ill? What is your backup for power and internet? How do you hand over knowledge, macros and data if we end the contract, and how long does that take?

A weighted scoring matrix

Score each provider from 1 to 5 on every criterion, multiply by the weight and add up. The weights are a starting point for a 5 to 50 agent support team; change them before you send the RFP, not after.

  • Fit with scope, hours and languages

    Example weight
    15%
    A score of 5 looks like
    Has run similar work in your languages and hours, with named examples
    A score of 1 looks like
    Generic answer that repeats your scope back

  • People: hiring, testing and retention

    Example weight
    20%
    A score of 5 looks like
    Describes its tests and shares its attrition figure and method
    A score of 1 looks like
    No attrition figure, or only a claim such as low turnover

  • Quality and reporting

    Example weight
    15%
    A score of 5 looks like
    Sample scorecard and report attached; offers joint calibration
    A score of 1 looks like
    Promises quality without saying how it is measured

  • Security and data protection

    Example weight
    15%
    A score of 5 looks like
    Clear access controls, signs your DPA, certificates with scope
    A score of 1 looks like
    Lists certifications without scope, dates or the entity that holds them

  • Launch plan

    Example weight
    10%
    A score of 5 looks like
    Week-by-week plan with owners and a go-live check
    A score of 1 looks like
    A single date with no plan behind it

  • Price and commercial terms

    Example weight
    15%
    A score of 5 looks like
    All-inclusive rate, clear inclusions, short notice periods
    A score of 1 looks like
    Low headline rate with fees and minimums in the small print

  • References

    Example weight
    10%
    A score of 5 looks like
    Clients of similar size and work, available to talk
    A score of 1 looks like
    Only logos, or references from much larger accounts

The weights add up to 100%. A provider that scores 1 on security or people should usually be removed, whatever its total.

Running the RFP without wasting anyone's time

Most RFPs fail for the same few reasons: missing volume data, no common price model and scoring rules invented after the answers arrive. These points avoid them.

Which data should you collect before writing the RFP?

  • Twelve months of contact volumes per channel, ideally per hour of the day
  • The share of contacts by reason, from your helpdesk tags or a manual sample of 200 tickets
  • Current KPIs: response time, resolution rate, customer satisfaction and quality scores
  • The languages and hours you need now and in a year
  • Your helpdesk, telephony and CRM, and who will pay for the licences

How do you make prices comparable?

Choose one pricing model and ask everyone to quote in it: per agent-hour, per dedicated agent per month, or per contact. Ask for a list of what is included and what is billed separately, such as setup, recruitment, training time, software, overtime and public holidays.

Then build the same worked example for each provider, for instance ten agents for twelve months, so that minimums, fees and notice periods show up in the total rather than in the small print.

Which answers deserve the most attention?

Look hardest at the answers about people: whether the provider employs its agents, how it tests them, how many agents each team lead manages and what its attrition was over the last year, with the method used to calculate it. These decide quality more than any technology slide.

Treat a missing number as an answer. A provider that cannot say what its attrition was, or which entity holds its certificates, is telling you how it will report to you later.

Continue reading

What are the red flags in an outsourcing proposal?

  • A headline rate with no list of inclusions
  • Certifications named without scope, holder or expiry date
  • No attrition figure, or only a word such as low
  • References only from clients many times your size
  • A launch date with no plan behind it
  • Long minimum terms combined with long notice periods

What should happen after the RFP?

Shortlist two providers, meet the people who would run your account, call their references and then start a pilot with a small team, agreed KPIs and weekly reviews. Sign for the full scope only when the pilot has met its targets for several consecutive weeks.

Last reviewed: . Written and reviewed by the OLYMP BPO team in Prishtina, Kosovo. About the company

RFPs for customer support: common questions

What is an RFP in customer support outsourcing?

A request for proposal is a document you send to several outsourcing providers describing the support work you need, the information you want back and how you will choose. It makes proposals comparable, because every provider prices the same scope.

What should a customer service RFP include?

Your company and goals, the scope of work, volumes and hours, systems and data, expected service levels and quality measures, the commercial model you want priced, what providers must submit, and the timeline and scoring method.

How many providers should receive the RFP?

Three to five is usually enough. More than that creates work for your team without improving the decision, and providers put less effort into tenders where their chance of winning is small.

How long should a customer support RFP process take?

For a team of 5 to 50 agents, four to six weeks from sending the RFP to a decision is realistic: two weeks for answers, one to two weeks for presentations and references, and time for contract review. A pilot then follows before scaling.

Should the RFP ask for a fixed price?

Ask for a price in one model you choose, such as per agent-hour or per dedicated agent per month, with every inclusion and exclusion listed. Without a common model, a low headline rate can hide fees, minimums or overtime charges.

Is an RFP needed for a small team?

A short, structured RFP helps even for five agents, because it forces you to write down volumes, hours and quality expectations. Keep it to a few pages and use the scoring matrix to stay objective.

Already have an RFP?

Send it to us. We answer every question directly, including price, inclusions and notice periods, so you can score us against the others.

Send your RFPPricing