AISSIST is named the Most Innovative CX Technology of 2026 by CX Today.
All tools

Tool · RFP question bank

AI Customer Service RFP Questions: 55 Questions to Evaluate a Vendor, and the Answer That Should End the Call

These AI customer service RFP questions are written for the buyer, not the bidder: 55 numbered questions in 11 groups, each with what a good answer looks like and what a red flag looks like — including the questions Aissist answers badly.

Last reviewed 2 Nov 2026 · First published 26 Oct 2026

TL;DR

Ask every vendor for a written resolution definition and a list of what its agent writes in your systems; Forrester expects two-thirds of providers to lose deals because buyers cannot verify their claims, and those two answers are the verifiable ones.

Methodology & sources
AI customer service RFP scoring grid: eleven question groups and their weights, summing to 100, with resolution definition and accuracy weighted highest
Eleven groups, weights summing to 100. Any knockout “no” removes the bid before scoring.

How to use it

How should you use these AI customer service RFP questions?

Send all 55 questions in writing, apply the six knockouts first, then score what survives on the weighted grid. The knockouts exist because some missing answers can’t be scored around: a vendor that can’t define a resolution in writing has quoted you a price for an undefined unit.

Two things separate this bank from the templates ranking today. The first is the red-flag column. Vendor templates describe the good answer; the bad answer is usually confident, fluent and specific about the wrong thing, so it is worth writing down in advance. The second is two groups that other templates fold into pricing and integrations: how a resolution is defined and measured (group 1), and what the agent actually writes into your helpdesk and CRM (group 3). Those two decide what every price in group 5 is worth. A third, new in this revision, asks what the vendor learns from your conversations and what it changes as a result (group 11).

“These tools rapidly synthesize provider claims and check facts.”

— Karen Tran, Principal Analyst, and Anthony McPartlin, VP, Principal Analyst, Forrester

Knockout table — any “no” ends the evaluation.

RequirementYes / NoIf no, stop here
A one-sentence resolution definition we can put in the contract (Q1) The per-resolution price has no unit
A pilot on our own helpdesk, with tickets staying there (Q32) You are evaluating a sandbox
Escalated conversations are not billed as resolutions (Q23) You pay for the agent's failures
A named subprocessor list, including every LLM provider (Q37) Security review cannot finish
Approved wording disclosing that customers are talking to an AI (Q40) EU Article 50(1) exposure since 2 Aug 2026
Full transcript export, message content included (Q46) Leaving costs your history

Group 1 of 11

1. How is a resolution defined and measured? (6 questions)

Make every vendor define "resolved" in one contract-ready sentence, then make it say what that sentence excludes. Aissist’s deflection vs resolution guide explains why: resolution is a subset of deflection, handover sits outside both, and the gap between them is where headline rates get made.

#QuestionA good answer looks likeA red flag looks like
1Define a resolved conversation in one sentence we can put in the contract.The test, the time window and the exclusions, in one sentenceA definition that exists only on a sales call
2Does a conversation that ends in customer silence count as resolved?No, or yes but reported as its own lineSilence counts after a timer you can't see
3Is the rate measured against all inbound conversations, or only those the AI attempted?All inbound, with excluded classes listed"Conversations where the AI engaged"
4What share of "resolved" customers come back on the same issue within seven days?A monthly number, and the charge reverses on a repeat"We don't track repeat contacts"
5Who grades a resolution, and can we see the grade and its reason for one conversation?Grade, reason and transcript linked; the rubric is oursThe vendor's model grades, with no appeal
6Do you report deflection, handover and resolution separately?Three lines that are never summedOne "automation rate"

Silence is where most definitions quietly loosen.

“If a frustrated customer stops responding, does that count as 'resolved'?”

— Bihan Jiang, Director of Product, Decagon

Red flagA resolution rate without a denominator is a marketing number.

Group 2 of 11

2. How accurate and safe is the agent on your tickets? (5 questions)

Test accuracy on tickets you choose, and judge it by one real decision rather than an aggregate dashboard. These five come from the buyer tests in AI washing in customer service, where the failing answers sounded just as fluent as the passing ones.

#QuestionA good answer looks likeA red flag looks like
7Run the agent on 50 historical tickets we choose, blind-graded against our agents.Our tickets, every output sharedA demo on the vendor's sample data
8What resolution rate do you expect on our tickets, and how will you measure it?A range, given after reading our sample, with the methodA guaranteed figure before seeing our data
9What is your error rate, and how do you grade error severity?A severity scale with a rate per level example →"99% accurate," undefined
10Which models does it run on, and what happens when a provider ships a regression?Named models, routing rule, fallback, regression gate"We always use the best model"
11Open one real conversation from last week and show why the AI answered as it did.Source retrieved, policy check run, escalation rule appliedA dashboard of aggregate accuracy

Macha’s template states question 8’s failure mode as cleanly as anyone has:

“A guaranteed percentage before seeing data is a red flag.”

— Abbas, Customer Support & AI, Macha

Red flagIf they can't show one decision, the dashboard is decoration.

Group 3 of 11

3. What does the agent write in your helpdesk and CRM? (6 questions)

Ask what the agent changes in your systems of record — object, field, trigger — because an agent that only replies has resolved a conversation, not a case. Templates usually ask whether the agent can write; fewer ask what it leaves on the ticket or what happens when a write fails. That difference decides whether “resolved” means the refund was issued or merely promised.

#QuestionA good answer looks likeA red flag looks like
12For each system we name, which actions can the agent take, and which are read-only?A list per system: object, field, action"Integrates with Shopify"
13For one ticket type, name the record it writes, the field it sets and the API it calls."Writes the RMA number to the order and sets refund_status""It surfaces the right answer"
14What does the agent write back to the helpdesk ticket: tags, fields, notes, status?Named fields in our taxonomy, set on every conversationReplies only; the ticket record stays empty
15Does our helpdesk stay the system of record, or do tickets move to your platform?Tickets, history and reporting stay where they areA migration before the agent can run
16What limits apply per action, and who sets them?Amount, frequency and approval thresholds, set by usOne global on/off switch
17If a write fails halfway, what happens to the customer and the record?Retry or rollback, logged, handed over with a noteCustomer told it's done; record half-written

Question 15 also sets the size of your security review and your exit: when the helpdesk stays the system of record, removing the agent costs you tuning, not a migration. The lock-in analysis scores seven vendors on it.

Red flagAn agent that only replies is a chatbot with better grammar.

Group 4 of 11

4. What happens when the agent hands over to a human? (4 questions)

Check that escalation is proactive, carries context, and is never suppressed to protect the automation rate.

#QuestionA good answer looks likeA red flag looks like
18When does the agent escalate on its own, without being asked?Documented, context-based triggers we can configureOnly when the customer types "human"
19What reaches the human agent on handover?Summary, steps taken and data collected, in the ticketThe human starts from the first message
20Does the agent ever make reaching a person harder?No; a person is always reachableEscalation hidden behind loops
21Show 20 escalated tickets from a live customer, redacted.Shared, handover notes visible"Escalations are rare"

Red flagHiding the human raises the rate and loses the customer.

Group 5 of 11

5. What exactly are you billed for? (6 questions)

Get the billable unit, the escalation rule and the clawback in writing before comparing a single price. Aissist’s AI agent pricing benchmark normalizes 18 vendors to cost per resolved conversation and records who controls the meter, which matters more than the headline rate.

#QuestionA good answer looks likeA red flag looks like
22What is your billable unit, defined in writing?One sentence that settles the edge casesThe invoice and the website disagree
23Are escalated or handed-over conversations billed, and at what rate?Not billed, or a stated lower rateBilled in full as an "outcome"
24Does the charge reverse if the customer returns on the same issue?Yes, within a stated windowNo clawback
25What is the year-one total at our volume and at double, all fees included?One total: seats, platform, usage, onboardingA per-resolution price quoted alone
26Can your software raise the billable count without us acting?A price cap per resolution, or a spend capCredits burned per action the agent chooses
27What happens when we hit the allowance?A pause or a known price; our choiceAutomatic overage by default

Definitions now differ inside a single vendor’s history. Since 18 May 2026, Zendesk bills only “verified” resolutions, where an LLM reads the ended conversation and confirms the request was resolved; assisted escalations and contained resolutions don’t count against the allowance. An email conversation ends 72 hours after the first email, and messaging defaults to 2 hours (Zendesk). That is a genuine improvement, and the vendor’s own model is still the judge — which is question 5.

Red flagA per-resolution price means nothing until the resolution is defined.

Group 6 of 11

6. How does implementation and the pilot work? (5 questions)

Pilot on your own helpdesk and your own tickets, draft-only first, with the success bar written down before day one.

#QuestionA good answer looks likeA red flag looks like
28What are the phases, in days, from kickoff to the first live category?Named phases with dates and our dependencies"It depends"
29Can we launch draft-only, per category, before customers see replies?Yes, with a written bar for going publicLive to customers on day one
30Who builds connections you don't have, and is that in the price?A named owner and "included" or a priceDiscovered after signature
31What do you need from our team, in hours per week?A number and a role"Minimal effort"
32Can the pilot run on our own helpdesk, with tickets staying there?YesA vendor sandbox only

Red flagA pilot in the vendor's sandbox tests the vendor's sandbox.

Group 7 of 11

7. Who checks quality after launch? (4 questions)

Require scoring of every conversation against your rubric, with a reason attached to each score.

#QuestionA good answer looks likeA red flag looks like
33What share of conversations do you score, and against whose standard?All of them, against our rubric, per roleA small sample against theirs
34Can we see every scored conversation with the reason for its score?Yes, linked to the transcriptScores without reasons
35Do you report CSAT for AI conversations separately, with the response rate?Separate, response rate shownBlended with human CSAT
36How fast do you surface contact reasons the agent can't handle, and who fixes them?A weekly gap report with an ownerA quarterly business review

Red flagA vendor that grades itself is writing its own report card.

Group 8 of 11

8. What happens to your data, and are you compliant? (5 questions)

Get the subprocessor list, the training answer and the retention period as numbers and names, not assurances. The full security block is in the AI agent security review; these five belong in the commercial RFP because legal needs them to sign.

#QuestionA good answer looks likeA red flag looks like
37Name every subprocessor that sees our data, including each LLM provider and region.A named list, with change notice"Our providers are confidential"
38Do you or your model providers train on our conversations?A contractual no covering providers tooA no that covers only the vendor
39How long is each data class retained, and how is it deleted?Days per class and a deletion record"As long as needed"
40How does the agent tell customers they are talking to an AI?Shown wording we approve"It's obvious"
41Which certifications do you hold, and which are only "aligned"?Certificate and scope"Aligned" presented as certified

Question 40 has been a legal duty in the EU since 2 August 2026, when Article 50 began to apply: providers must design systems so people know they are interacting with an AI unless it is obvious (Article 50). Article 50(2), machine-readable marking of generated content, has a grace period to 2 December 2026 for generative systems already on the market before 2 August, under the Digital Omnibus agreement of 7 May 2026 (Cloud Security Alliance). Ask whether it applies to the vendor’s outputs and what ships by that date.

Red flag"Aligned" is not a certificate.

Group 9 of 11

9. What does the contract lock you into? (4 questions)

Put the notice period, the renewal cap and the outcome SLA in the order form, not the linked terms.

#QuestionA good answer looks likeA red flag looks like
42What are the term, auto-renewal and notice period?Days, written in the order formBuried in linked terms
43Can the price rise at renewal, and by how much?A cap in writing"Then-current rates"
44Can committed volume decrease mid-term?Yes, or flexible tiersNon-reducible quantities
45Who is accountable when resolution falls below the contracted rate?A named owner and remedy in the SLANo SLA on outcomes

Red flagThe renewal clause costs more than the pilot ever will.

Group 10 of 11

10. Can you leave, and what do you take with you? (5 questions)

See the export work during the pilot; a documented endpoint you've run beats a promised one. Aissist’s lock-in analysis found three of seven vendors, Aissist included, publish no readable data-export path.

#QuestionA good answer looks likeA red flag looks like
46Can we export full transcripts, message content included, in JSON at any time?A documented endpoint, no lookback floorCSV without message content
47Can we export the agent's instructions, knowledge and workflow logic?An open-format exportImport-only configuration
48How many days after termination can we retrieve our data?A number in the order form"A reasonable period"
49If you are acquired, what changes for our contract and integrations?Terms survive; integrations committed for the termA press release instead of a clause
50Who owns the configuration and tuning built for us?We do, documentedThe vendor; leaving means rebuilding

Question 49 is not hypothetical. Salesforce completed its acquisition of Fin on 10 September 2026; the release says Fin works with the helpdesks companies already use, but puts no time horizon on it (Salesforce). The protection is a clause, not a release.

Red flagIf you can't see the export before signing, you've seen the exit.

Group 11 of 11

11. What insights does the agent generate, and how do they improve operations? (5 questions)

Ask what the vendor learns from your conversations that you could not see before, then make it show one operational change an insight produced. Resolving a ticket saves its handling cost once; finding out why a thousand of them arrived — a confusing policy, a broken checkout step, a missing help article — removes them for good. This group separates a vendor that reports on itself from one that improves your operation.

#QuestionA good answer looks likeA red flag looks like
51What insights do you generate from our conversations, beyond the agent's own performance?Contact reasons, product gaps, policy friction and sentiment shifts, by topicOnly resolution and deflection charts
52Can we ask a new question of our conversation data and get an answer the same day?Ad hoc questions answered across all conversations, with examples linkedFixed reports; new cuts need a services ticket
53Show one insight from a live customer and the operational change it led to.The insight, the owner, the change and a before-and-after metricA chart with no action attached
54Do insights cover human agents' conversations too, not only the AI's?AI and human conversations, judged on the same standardAn AI-only view, blind to where people struggle
55How do insights flow back into the agent, the knowledge base and the team?Gaps become knowledge or workflow updates, tracked to closureInsights end in a quarterly PDF

Question 53 is the one to press. Every vendor can draw a contact-reason chart; the useful answer names who acted on it, what changed, and which number moved. Pair it with question 36: the gap report says what the agent can’t handle, and group 11 says what the business should fix so the contact never happens.

Red flagAn insight nobody acts on is a report, not an improvement.

Scoring

How do you score the answers?

Score each question 0–3, average each group, divide by 3 and multiply by the group’s weight; the maximum is 100. 0 is no answer or a dodge, 1 is vague, 2 is specific, 3 is specific and written into the contract. Score each proposal alone before discussing it. The spreadsheet does the arithmetic.

GroupQuestionsWeight
1. Resolution definition and measurement1–615
2. Accuracy and safety7–1115
3. Helpdesk and CRM write-back12–1712
4. Escalation and handoff18–216
5. Pricing and billing units22–2712
6. Implementation and pilot28–326
7. Post-launch quality33–368
8. Security, data and compliance37–418
9. Contract terms42–454
10. Exit and portability46–508
11. Insights and operational impact51–556
Total55100

Groups 1 and 2 carry 30 points because every other number on the sheet depends on them. Move weight to group 8 if you are a regulated EU buyer, to group 3 if most of your volume needs an action rather than an answer, or to group 11 if the business case rests on fixing why customers contact you, not just answering them. Keep the total at 100.

Four dated anchors for an AI customer service RFP in 2026: Zendesk verified resolution tiers on 18 May, EU AI Act Article 50 on 2 August, Salesforce completing the Fin acquisition on 10 September, and the Article 50(2) marking grace period ending 2 December
Put dates in the RFP, not performance claims: each one changes a question you must ask.

Self-audit

How does Aissist answer its own question bank?

Aissist answers the write-back, system-of-record and billing questions well, and the denominator, silence, subprocessor, retention and export questions badly. We checked only what a buyer can find on Aissist’s public pages on 2 Nov 2026. Aissist reports an 83% average resolution rate and 4.8/5.0 CSAT, and publishes no denominator for the 83% — which is precisely what question 3 catches.

QuestionAissist’s public answer (2 Nov 2026)Verdict
1 · Resolution definitionResolved without escalation, after at least one genuine inquiry (pricing)Strong
2 · SilenceNot addressedGap
3 · Denominator83% published with no denominatorGap
13 · Named write actionsFive named Zendesk write actions (AI washing)Strong
15 · System of recordRuns on the existing helpdesk, which stays the recordStrong
23 · Escalation billingCases handed to a human are not chargedStrong
26 · Meter control$0.09 per interaction, capped at $0.25 (email) or $0.60 (chat) per resolutionStrong
37 · SubprocessorsAWS and Azure named; no LLM provider listGap
39 · RetentionNo retention period publishedGap
41 · CertificationsISO 27001 certified; SOC 2 aligned, not certifiedPartial
46–48 · Export and exitNo transcript export documented; configuration import-only; no post-termination windowGap

Six gaps out of eleven. A question bank no vendor fails is a brochure, so this one includes the questions that fail us.

Verdict

Ask for the definition before the number

A resolution rate is a claim; a written definition, a list of writes and an export you have run are commitments. The templates ranking today tell you what a good answer sounds like. This bank adds what a bad one sounds like, so you can stop an evaluation in the first call rather than the first renewal. Send all 55 questions, apply the six knockouts, score the survivors, and write answers 1, 23, 37, 46 and 48 into the order form. Then run groups 7 and 11 monthly, on whoever wins — including us.

FAQ

Frequently asked questions

What questions should be in an AI customer service RFP?

A contract-ready resolution definition, what the agent writes in your systems, escalation and billing rules, year-one total cost, subprocessors and retention, AI disclosure wording, renewal terms and transcript export rights. This bank groups 55 such questions into eleven areas.

How do you evaluate an AI customer service vendor?

Send written questions, apply pass/fail knockouts, score surviving answers on a weighted grid, then pilot on your own helpdesk and tickets. Judge accuracy on tickets you choose, not on the vendor's demo data.

What is a red flag in an AI vendor's RFP answer?

A confident answer that is specific about the wrong thing: a resolution rate with no denominator, "integrates with" with no list of writes, a guaranteed rate before seeing your tickets, or "aligned" presented as certified.

Should escalated conversations be billed?

Not as resolutions. Under per-resolution pricing, a case handed to a human should be free or carry a stated lower rate. Ask in writing, then reconcile invoices against helpdesk handovers.

Does silence count as a resolved conversation?

At some vendors, yes, after a timer. Ask whether silent endings count, how long the window is, and whether they are reported separately; a customer who gave up looks identical to one who was helped.

How many questions should an AI vendor RFP have?

Enough to cover resolution, accuracy, write-back, escalation, pricing, implementation, quality, data, contract, exit and insights. This bank uses 55; a small team can send groups 1, 3 and 5, seventeen questions, and learn most of what matters.

Does the EU AI Act affect AI customer service RFPs?

Yes. Since 2 August 2026, Article 50 requires that customers be told they are talking to an AI unless it is obvious. Ask each vendor to show the disclosure wording.

Is there a free AI customer service RFP template?

Yes. This bank is a free spreadsheet with 55 questions, a good-answer and red-flag column for each, a scoring grid and blank columns for each vendor's answer, evidence and score.

Changelog — 26 Oct 2026: first published as a 24-question bank in four phases. 2 Nov 2026: expanded to 55 questions in eleven groups; added red-flag column, knockout table, weighted scoring grid, write-back, resolution-definition and insights groups, dated regulatory and billing anchors, and an updated self-audit.

Put us through the same 55 questions.

Bring the spreadsheet to a working session and we will answer every line in writing — gaps included.