What a call center RFP template should cover
A complete call center RFP template covers five sections: vendor profile and capability (corporate identity, headcount, delivery footprint, attrition, references), operational maturity (QA coverage, supervisor ratios, replacement SLAs, workforce management), compliance and risk (the regulations that apply to your vertical, plus security posture), pricing and commercial terms (loaded hourly rate breakdown, contract length, fee structure), and tech stack and integration (CRM and dialer compatibility, data flow, security). A focused 25-question RFP outperforms a 100-question RFP because vendors give thoughtful answers to questions that obviously matter and boilerplate answers to questions that look like procurement-process theater.
The 5 sections every BPO RFP needs
Skip a section and the response cannot be evaluated. Combine sections and the vendor cannot tell which question they are actually answering. Here is what each section covers and why it matters.
Section A: Vendor profile and capability
Five questions that tell you whether the vendor is a real company with real agents or an aggregator with a stack of subcontractor relationships. Legal name, HQ, total headcount by delivery location, attrition by location for the last 12 months, ramp time from signature to live agents, and three references in your vertical. The attrition-by-location question is the single most diagnostic because aggregators cannot answer it without exposing the subcontractor chain.
Section B: Operational maturity
Five questions about how the operation actually runs. QA sampling rate (1 to 3 percent manual is industry baseline; the better operators run AI QA at 100 percent coverage). Real-time supervisor dashboard access for the client. Standard SLA for replacing an underperforming agent (5 business days is the operator benchmark). Workforce management approach. Call recording retention policy. Body shops hedge on dashboard access and replacement SLAs. Operators publish them.
Section C: Compliance and risk
Filtered to the regulations that apply to your vertical. HIPAA for healthcare and Medicare. PCI DSS for any card data capture. FDCPA and Reg F for debt collection. TCPA and FCC CG Docket 02-278 for any outbound dialing. CMS MCMG for Medicare. NAIC for insurance. FCRA for credit-related work. SOC 2 for any production workload. GDPR for European data. The CFG RFP builder includes only the compliance questions that match your selected regulations, so vendors do not pad answers to irrelevant rules.
Section D: Pricing and commercial terms
Five questions that separate honest pricing from teaser-rate pricing. Loaded hourly rate broken into agent wage, supervisor allocation, dialer and tech, QA, and facilities. Contract term and notice period. Setup fees, NDA fees, annual prepays, and minimum commits (the four most common hidden costs). Billing model. And the headline number: what does the user-selected billing model price out at for the user-selected seat count. The breakdown question is the most useful for cross-vendor comparison because two vendors quoting the same headline rate can have wildly different supervisor allocations.
Section E: Tech stack and integration
Five questions about whether the vendor can plug into your stack without three months of professional services. CRMs, dialers, and integrations the vendor has built natively (Salesforce, HubSpot, Outreach, Salesloft, Apollo, ServiceTitan, Housecall Pro, and so on). Data flow architecture for caller ID, scorecard data, and warm-transfer context. Security posture: encryption, access controls, retention, breach notification. Operators name specific integrations they have built. Body shops list categories.
Vendor-evaluation framework: the 7 questions that separate operators from body shops
After running this template across 40+ vendor responses, seven questions consistently sort operators from body shops. Score every response on these seven and the shortlist almost writes itself.
- Will you publish 12-month attrition by delivery location? Operators say yes. Body shops say "company averages."
- Will you give the client read-only access to your supervisor dashboard? Operators say yes. Body shops say "weekly reporting calls."
- What is your standard SLA for replacing an underperforming agent? Operators say 5 business days. Body shops say "we work with the client to resolve."
- What percentage of calls are scored by QA? Operators run 100 percent AI QA. Body shops sample 1 to 3 percent manually.
- Can you provide a specific implementation playbook for our vertical? Operators send one within 48 hours. Body shops send a generic deck.
- What is your supervisor-to-agent ratio? Operators run 1:10 to 1:15. Body shops run 1:25 or higher.
- Will you commit to a small pilot before a full ramp? Operators welcome the pilot. Body shops push back because the pilot exposes the gap between the pitch and the floor.
The evaluation rubric in scorable form
The seven questions above are the ones the generator appends to the back of every RFP it builds. The table below is the same rubric in the exact wording that appears in the generated document, laid out so you can score each vendor response side by side against what an operator says and what a body shop says.
BPO vendor-response evaluation rubric, 2026. Units: categorical, expected answer by vendor type. Scope: 7 diagnostic questions applicable to any contact center or BPO vendor selection. Collection basis: Call Force Global's own vendor-evaluation framework, drawn from contact center RFP responses reviewed across active programs, 2026.
| Diagnostic question | What an operator answers | What a body shop answers |
|---|---|---|
| R1. Will you publish 12-month attrition by delivery location? | Operators say yes. | Body shops give company averages. |
| R2. Will you give the client read-only access to your supervisor dashboard? | Operators say yes. | Body shops offer weekly reporting calls. |
| R3. What is your standard SLA for replacing an underperforming agent? | Operators say 5 business days. | Body shops say they work with the client to resolve. |
| R4. What percentage of calls are scored by QA? | Operators run 100 percent AI QA. | Body shops sample 1 to 3 percent manually. |
| R5. Can you provide a specific implementation playbook for our vertical? | Operators send one within 48 hours. | Body shops send a generic deck. |
| R6. What is your supervisor-to-agent ratio? | Operators run 1:10 to 1:15. | Body shops run 1:25 or higher. |
| R7. Will you commit to a small pilot before a full ramp? | Operators welcome the pilot. | Body shops push back. |
How to cite this table: Call Force Global. (2026). BPO Vendor Evaluation Rubric 2026. Retrieved from https://callforce.global/tools/rfp-builder/
The full RFP question bank
The generator above assembles a 28-question RFP from the bank below, substituting your vertical, seat count, and billing model into the templated questions. The complete bank is reproduced here so it can be read, copied, or adapted without running the tool. Placeholders are shown in plain language.
Section A: Vendor profile and capability
- Provide your full corporate legal name, HQ address, and total agent headcount across all delivery centers.
- List all delivery locations with country, time zone, native vs L2 English mix, and seat count per location.
- What is your annualized agent attrition rate by delivery location for the last 12 months?
- What is your typical ramp time from a completed kickoff to live agents handling production volume?
- Provide three references from current clients in your vertical.
Section B: Operational maturity
- What percentage of calls are scored by QA? Industry baseline is 1 to 3 percent manual sample. Some vendors run 100 percent AI QA.
- Describe your real-time supervisor dashboard. Can clients receive read-only access?
- What is your standard SLA for replacing an underperforming agent?
- Describe your workforce management approach to forecasting, scheduling, and intra-day adherence.
- What is your standard call recording retention period and access protocol?
Section C: Compliance and risk
The generator selects from this bank based on which frameworks apply to your program. Every framework in scope adds its question to Section C.
Compliance and risk questions to put to a contact center vendor, by regulatory framework, 2026. Units: one question per framework. Scope: 10 frameworks covering US healthcare, payments, telemarketing, debt collection, Medicare marketing, security attestation, insurance, credit, and EU personal data. Collection basis: Call Force Global RFP question bank, 2026. Informational only, not legal advice.
| Framework | Question to put to the vendor |
|---|---|
| HIPAA (protected health information) | Provide a copy of your standard Business Associate Agreement (BAA). Describe encryption in transit and at rest, role-based access controls, and agent HIPAA training cadence. |
| PCI DSS (card data) | Provide your most recent PCI DSS Attestation of Compliance (AOC). Describe your pause-and-resume call recording approach for card data capture. |
| TCPA and FCC rules (outbound dialing) | Describe your dialer configuration for TCPA quiet-hour enforcement, FCC CG Docket 02-278 offshore disclosure (if applicable), DNC scrubbing at the federal, state, and RND level, and consent ledger architecture. |
| FDCPA and Regulation F (debt collection) | Describe your FDCPA Section 805 enforcement in the dialer, your 7-7-7 cadence implementation, and how you handle disclosure of debt status during outbound calls. |
| CMS MCMG (Medicare marketing) | Describe your fronter perimeter enforcement for Medicare AEP. How do you keep nearshore agents inside pre-qualification scope and out of licensed plan recommendation? |
| SOC 2 Type II (security controls) | Provide your most recent SOC 2 Type II report. Describe access controls, vendor management, and incident response. |
| NAIC and state insurance rules | Describe your NAIC-compliant intake scripts and licensed-vs-pre-licensed scope split for insurance fronter work. |
| FCRA (credit-related disclosures) | Describe your FCRA compliance posture for any credit-related disclosures or pre-qualification scoring used on your floor. |
| GDPR (EU personal data) | Describe your GDPR compliance posture: data residency, lawful basis for processing, data subject rights handling, and breach notification timelines. |
| No framework strictly required | Describe any compliance frameworks your operations align with even if not strictly required by your client base. |
How to cite this table: Call Force Global. (2026). BPO RFP Compliance Question Bank 2026. Retrieved from https://callforce.global/tools/rfp-builder/
Section D: Pricing and commercial terms
- Provide your loaded hourly rate for the role profile most aligned with your vertical, broken into agent wage, supervisor allocation, dialer and tech, QA, and facilities. State whether the rate is exclusive or inclusive of US-based account management.
- What is your standard contract term, notice period, and ramp-up or ramp-down flexibility?
- Do you charge setup fees, NDA fees, annual prepays, or minimum commits? If yes, list each.
- Describe your billing model: per hour, per call, per qualified meeting, per transfer, or hybrid? Confirm whether you can support your preferred billing model as the primary billing structure.
- What does the your preferred billing model billing model price out at for a your target seat count-seat program?
Section E: Tech stack and integration
- List the CRMs, dialers, and integrations you have already built (e.g., Salesforce, HubSpot, Outreach, Salesloft, Apollo, ServiceTitan, Housecall Pro, SolarReviews, Aurora). Specify which you have built natively vs requiring middleware.
- Describe your data flow architecture: how does caller ID, scorecard data, and warm-transfer context flow from your platform to the client stack?
- Describe your security posture for the client data: encryption, access controls, retention, and breach notification protocols.
How CFG built this generator
Recurring vendor RFPs and procurement conversations kept surfacing the same problem: buyers asked for broad certifications but often skipped measurable operating questions such as dashboard access, attrition by location, QA coverage, and replacement timelines. This generator keeps the questions a buyer can verify. The full version of the framework is at the downloadable call center outsourcing RFP template. You can also download the CFG RFP template PDF and a spreadsheet-ready vendor scoring CSV.
What good RFP answers look like vs evasive ones
The text of the answer matters less than its specificity. Good answers cite a number, a name, or a process. Evasive answers describe an intention.
- Good attrition answer: "Our Kingston Jamaica location ran 26 percent annualized attrition for the trailing 12 months ending Q4 2025. Bogota Colombia ran 31 percent. We publish quarterly attrition dashboards to all clients."
- Evasive attrition answer: "Industry-leading retention through our culture-first approach. Specific numbers available under NDA."
- Good QA answer: "100 percent of calls are scored by our AI QA platform on a 12-category scorecard. Human QA reviews the lowest-scoring 5 percent of calls weekly. Clients get dashboard access to call-level scorecard data."
- Evasive QA answer: "Comprehensive QA program with seasoned analysts and proven methodology."
- Good replacement SLA: "5 business days from written notice from the client. Replacement agent is pre-trained on client scripts and shadows for 2 days before going live."
- Evasive replacement SLA: "We partner closely with clients to resolve performance issues through coaching and improvement plans."
If your shortlist responses skew evasive on the seven diagnostic questions above, you are looking at a body-shop list, not an operator list. Run the RFP again with a sharper vendor pool. The CFG vendor comparison page and the best call center outsourcing companies breakdown are starting points.
FAQ
What should a call center RFP template include?
A complete call center RFP template covers five sections: vendor profile and capability (corporate identity, headcount, delivery footprint, attrition, references), operational maturity (QA coverage, supervisor ratios, replacement SLAs, workforce management), compliance and risk (the regulations that apply to your vertical, plus security posture), pricing and commercial terms (loaded hourly rate breakdown, contract length, fee structure), and tech stack and integration (CRM and dialer compatibility, data flow, security).
How many questions should a BPO RFP have?
A focused 20 to 30 question BPO RFP outperforms a 100-question RFP. Vendors give thoughtful answers to the questions that obviously matter and boilerplate answers to questions that look like vendor-evaluation-process theater. The CFG RFP builder produces a 25-question template by default, filtered to the questions that genuinely separate operators from body shops in your vertical.
What is the difference between a body shop and a real BPO operator?
A body shop sells you hours. A real operator sells you a tuned system. The diagnostic questions are: do they share a real-time dashboard with the client, will they replace an underperforming agent within 5 business days, will they publish attrition by location, and do they have a specific implementation playbook for your vertical. Body shops answer those four with hedges. Operators answer with proof.
Should I include a pilot in my call center RFP?
Yes. A small pilot is the single most underused leverage point in BPO procurement. It lets you see actual production data (attrition, QA scores, throughput) on your vertical and your scripts before committing to a 50 or 100 seat ramp. Any vendor that refuses a pilot is either capacity-constrained or knows their numbers will not survive scrutiny. The CFG RFP builder includes a pilot scope question by default.
How long should a BPO vendor have to respond to an RFP?
Two weeks is the sweet spot. One week is too short for vendors to assemble compliance documentation, pricing model breakdowns, and references. Four weeks signals a procurement process that is more interested in optics than speed, and the best operators (the ones with real demand) will quietly opt out of slow processes. Two weeks gets you serious responses from operators who can actually move.
Is the RFP this tool generates legal advice?
No. This is a procurement template, not legal advice. The compliance questions are derived from the regulations vendors should be able to speak to (HIPAA, PCI DSS, FDCPA, TCPA, CMS MCMG, NAIC, FCRA, SOC 2, GDPR), but contract review and final compliance certification should always run through your counsel and a security team. Use the template to source informed vendor responses, not as a substitute for legal sign-off.
Keep going
Pair the RFP with the attrition benchmark tool to ground-truth vendor attrition claims against industry data, and the call center KPI benchmark dashboard to score vendor QA, AHT, and SLA against 2026 vertical bands. For pricing assumptions, the how pricing works page is the most useful reference. The nearshore fronter perimeter framework explains why the highest-attrition work belongs offshore while licensed work stays onshore, and the AI QA call center breakdown explains why 100 percent QA coverage now beats the old sampling model.
For deeper reading: the downloadable call center outsourcing RFP template, vendor comparison, or our contact page to request a quote.