Buyer's guide · Checklist
Contact Center RFP Checklist
96 questions to put to every contact center vendor you shortlist, grouped into fourteen areas. Vendor-neutral, printable, and written to be copied straight into your RFP.
Quick answer
What should a contact center RFP include? A contact center RFP should ask every vendor the same questions about fourteen areas: telephony and BYOC, inbound routing, outbound dialing modes and answering machine detection, omnichannel messaging, AI voice agents, agent assist and QA, reporting, compliance-supporting controls such as DNC, consent, calling hours and recording retention, security and data residency, multi-tenancy and white-label, integrations and API, migration, the pricing model, and support and SLA. Ask for evidence with each answer, such as a live demo screen or a contract clause, and treat planned features as unavailable until dated in writing.
How do you use this checklist?
An RFP is only useful if the answers can be compared. That means the same questions, in the same words, to every vendor, and a rule for what counts as a good answer. Three rules keep this checklist honest:
- Cut before you send. Delete the sections that do not apply to you. A shorter questionnaire gets more careful answers, and vendors notice when a buyer knows what they need.
- Ask for evidence, not adjectives. Beside each question, ask the vendor to name where the answer can be seen: a screen in the demo, a page in the documentation, or a clause in the contract. "Yes" with no evidence scores lower than "partly" with a screenshot.
- Separate today from later. Ask vendors to mark every answer as available now, planned with a date, or not planned. A roadmap item is a reason to talk, not a reason to buy.
If you have not yet decided which calls should be automated, read AI or Human? Which Calls to Automate first. To compare AI voice agents hands-on, use the AI Voice Agent Evaluation Matrix.
Telephony, BYOC and SIP
The voice path decides call quality, cost and who you depend on when calls fail. Settle it before anything else.
- Can we bring our own carrier (BYOC) or SIP trunk, and is any feature unavailable when we do?
- Can the platform sit on top of our existing PBX or SBC, or must voice move to your infrastructure?
- Which SIP signalling and codecs do you support, and how do you handle registration versus IP authentication?
- Do you charge a per-minute platform fee on calls that travel over our own trunk?
- Where are your media servers, and what happens to calls in progress if one fails?
- Who signs outbound calls for STIR/SHAKEN where it applies: the carrier, the platform, or nobody?
- How is caller ID chosen per campaign, and can a number be deactivated without a support ticket?
- Do agents need an installed softphone, or does the browser work, and which browsers are supported?
Inbound routing
If you take calls as well as make them, routing is where callers feel the platform.
- How are DIDs mapped to queues, IVR flows or AI agents, and who can change that mapping?
- What queue strategies exist (longest idle, ring all, round robin), and is skills-based routing live today or on the roadmap?
- Can callers request a callback and keep their place in the queue?
- What does a caller hear when nobody answers, and is anyone alerted about the missed call?
- Can business hours, holidays and overflow rules be set per queue without a developer?
- Can an agent take inbound and outbound calls on the same seat, and how is that billed?
Outbound dialing modes and AMD
Dialing mode and answering machine detection drive both productivity and complaints. Ask how each is controlled, not just whether it exists.
- Which dialing modes are included in each plan: preview, power, progressive, predictive?
- How does predictive pacing decide how many lines to dial, and how is the abandon rate held under the limit we set?
- How does answering machine detection work: beep detection, greeting analysis, or transcript classification?
- In which languages has AMD been tested, and can you share the method and the conditions of the test?
- Can AMD sensitivity be set per campaign, and what happens to a call the AMD is unsure about?
- What is the false-positive handling path: how is a live person wrongly classified as a machine detected and corrected?
- How are retry rules, attempt limits and callback scheduling configured per campaign?
- Can a supervisor pause, edit or stop a running campaign instantly?
Omnichannel
Customers reply on the channel they prefer. The question is whether the thread and the opt-outs stay joined up.
- Which channels are native (voice, WhatsApp, SMS, email), and which depend on a third-party connector?
- Do all channels for one customer appear in one conversation history?
- Does an opt-out on one channel apply to the others automatically?
- Are WhatsApp templates, buttons and media supported, and who handles template approval?
- Is message delivery reported per message, and can a send in progress be paused or cancelled?
AI voice agents
Ask to hear real calls, not a scripted demo. The evaluation matrix in this guide goes deeper.
- Can the AI voice agent answer inbound calls and run outbound campaigns on the same telephony as human agents?
- Can callers interrupt the agent mid-sentence (barge-in), and does it stop and listen?
- How do you measure response latency, and will you share median and p95 figures from our pilot calls?
- How is the agent kept to facts: knowledge base, approved price list, guardrails before speech?
- When the agent takes an action (booking, payment promise, cancellation), how does it confirm the action succeeded before telling the caller?
- How does handoff to a human work, and does the human see the transcript and context?
- Which languages and Arabic dialects are supported in production, not just in a demo?
- Who can switch the AI off, at what scope, and how fast?
- How is AI usage billed, and can we use our own model provider keys?
Agent assist and QA
Assist tools help on the live call; QA tools help afterwards. Both depend on transcription quality in your languages.
- Is live transcription available in our languages, and with what delay?
- What does agent assist show during the call: summary, sentiment, suggested responses, knowledge articles?
- Can supervisors listen, whisper and barge in, and is that logged?
- Can we build our own QA scorecards, and can AI pre-score calls for a human to review?
- Are AI summaries written into the CRM, and can an agent edit them first?
Reporting
You will be asked to prove results. Make sure the numbers you need exist before you sign.
- Which reports exist out of the box, and can we see them populated with demo data?
- Is there a real-time wallboard, and how often does it refresh?
- Can reports be exported (CSV, Excel, PDF) and scheduled by email?
- Can we access raw call records through an API or data export for our own BI tools?
- How are metrics such as connect rate, abandon rate and handle time defined, and are the definitions documented?
Compliance-supporting controls
No platform can meet your obligations for you. What you are buying is controls that help you meet your obligations and records that prove what happened.
- Is the DNC list checked on every call attempt, or only when a list is uploaded?
- Can we import national and internal DNC lists, and record why a number was added?
- How are consent records stored (source, timestamp, proof), and is consent checked before dialing?
- Are calling hours enforced in the destination's local time, per country, with day-of-week rules?
- Can we set attempt limits per contact per period?
- Can recording be switched on or off per campaign or jurisdiction, and can it pause during payment details?
- How are recording and data retention periods set, and is deletion at the end of the period automatic?
- Is every blocked call logged with the reason, and can those decisions be exported for an audit?
- Which regulations do your default rule packs reference, and who keeps them current?
Security and data
Ask for status, not adjectives. A planned certification is not a held one, and both are fine as long as the vendor says which.
- How is data encrypted in transit and at rest?
- How is one customer's data isolated from another's at the database level?
- Is there role-based access control, and can roles be scoped to a campaign, team or client?
- Is single sign-on (SAML or OIDC) available today, or only on the roadmap? Is multi-factor login enforced?
- Are audit records append-only, and who, if anyone, can edit or delete them?
- In which countries is our data stored and processed, including recordings, transcripts and AI processing?
- Which subprocessors handle our data, and is the list published?
- Which security certifications do you hold today, and which are planned, with target dates?
- Has an independent penetration test been performed? When, by whom, and will you share a summary under NDA?
- Is a data processing agreement available, and is customer data used to train shared AI models?
- How are backups taken and restore-tested, and what are your recovery objectives?
Multi-tenancy and white-label (BPOs and resellers)
If you serve several clients, or resell the platform, isolation and branding are the product.
- Can each client be a separate tenant with its own users, numbers, lists and recordings?
- Can a supervisor be scoped to see only one client's agents and calls?
- Can each tenant have its own carrier, caller IDs and compliance settings?
- Can we brand the platform with our own name, logo and domain?
- Is there a partner console for creating tenants and seeing usage across them?
- How is billing split: can we invoice our clients ourselves?
Integrations and API
An integration that writes data back is worth more than one that only displays it.
- Which CRMs have native integrations, and do they write call outcomes and recordings back?
- Is there a documented REST API, and can we read the documentation before signing?
- Are webhooks signed, and are failed deliveries retried?
- Is there a sandbox or test tenant for developers?
- Are there rate limits, and are they published?
- Do you integrate with workforce management (WFM) tools today, or is that on the roadmap?
Migration
The cheapest platform becomes expensive if the move stalls for three months.
- What does a typical migration plan look like, step by step, and who does each step?
- Can we pilot one campaign on one trunk before moving everything?
- Can we import contacts, DNC lists, dispositions and historical call records?
- Can we port our existing numbers, and who manages the port?
- Is training included, or is it a professional-services line item?
- If we leave, how do we export our data and recordings, and in what format?
Pricing model
Compare total cost at your volumes, not list price per seat. The gap between a pilot quote and a real invoice is where surprises live.
- Is pricing per seat, per minute, or both? What exactly does a seat include?
- Are carrier and telephony charges included, marked up, or billed by our own carrier?
- How is AI usage billed: per minute, per conversation, per token? Is there a monthly cap we can set?
- Which features are reserved for higher tiers (dialing modes, AMD, white-label, API)?
- Are there setup fees, minimum seat counts, or minimum commitments?
- What is the price difference between monthly and annual billing?
- Is there a free trial, and is it on the real product with our own calls?
Support and SLA
Read the SLA document itself. A marketing page saying 'high availability' is not an SLA.
- Which plans include an uptime SLA, what is the figure, and what credit applies if it is missed?
- What are support hours and response times, and in which languages and time zones?
- Do we get a named contact or customer success manager?
- How are incidents communicated, and is there a status page?
- Is user documentation available for each role (agent, supervisor, admin)?
How should you score the answers?
Keep scoring simple enough that two people on your team would give the same answer the same score. A four-point scale works well:
| Score | Meaning |
|---|---|
| 3 | Available today, and shown to us in a demo, document or contract clause. |
| 2 | Available today according to the vendor, but not yet shown. |
| 1 | Planned, with a date in writing, or available only through a workaround. |
| 0 | Not available, not planned, or no clear answer. |
Weight the sections before you read any answers, not after. A BPO will weight multi-tenancy heavily; a single-site collections team may not need it at all. Deciding weights first stops a polished demo from rewriting your priorities. Mark a handful of questions as must-haves: a zero on any of them removes the vendor, whatever the total.
For pricing, do not score the list price. Ask every vendor to price the same scenario (your seat count, your monthly minutes, your carrier arrangement and your expected AI usage) and compare the totals. The ROI calculator and the guide to per-agent versus per-minute pricing help structure that comparison.
How does DialerBee answer some of these?
We would rather you ask us the same questions as everyone else. A few answers, with where to check them:
- BYOC and per-minute fees. DialerBee connects three ways: we supply trunks and numbers, you keep your own PBX or SBC, or you bring a SIP trunk from your own carrier. When you bring your own PBX or carrier there is no per-minute platform fee, because we do not carry the voice. See deployment options.
- Pricing model. Per agent: Starter $69, Professional $129 per agent per month, Enterprise custom. Carrier minutes are billed by your carrier. The AI voice agent is a usage-billed add-on metered by minutes, on managed keys or your own model keys. There is a 14-day free trial. See pricing.
- Dialing modes. Preview, power, progressive and predictive. Starter includes preview and power; Professional includes all four.
- Security status. TLS in transit and AES-256 at rest, row-level tenant isolation in PostgreSQL, role-based access and append-only audit logs are implemented. Single sign-on (OIDC, SAML and SCIM provisioning) and multi-factor login are available. SOC 2 Type II is planned, not held, and an independent penetration test is planned. See the Trust Center for the full status list.
- Compliance-supporting controls. DNC checks, calling-window enforcement, consent tracking, retry limits, CLI ownership verification and append-only audit logging are configurable controls. See compliance controls.
- Integrations. A REST API with signed webhooks, plus CRM, calendar and messaging connections. See integrations.
DialerBee does not provide legal advice or guarantee regulatory compliance. The compliance questions in this checklist concern product controls; confirm your own obligations with your regulator or counsel.
Questions
RFP checklist FAQ
How many questions should a contact center RFP include?
How do I compare vendor answers fairly?
Should an RFP ask about compliance?
What is the most common pricing surprise?
Can I use this checklist for AI voice agent vendors?
Is this checklist legal advice?
Put DialerBee through the checklist
Send us your RFP or bring it to a live walkthrough, and we will answer each question on screen. Or start a 14-day free trial and check the answers yourself.
More from the buyer's guide