Tool · RFP question bank
AI Agent Evaluation: An RFP Question Bank Written for the Buyer
AI agent evaluation usually runs on checklists written by the vendors being evaluated. This question bank is the buyer’s version: 24 literal RFP lines, grouped into four phases, each paired with a way to check the answer after the contract is signed.
9 min read · Last reviewed 26 Oct 2026
Forrester predicts two-thirds of providers will lose deals because buyers cannot verify their claims — so ask only questions that have a checkable answer, and write down how you will check it before you sign.
- Competing checklists read 26 Oct 2026: Fini, Parloa, Fin and Ada, scored on five buyer-side questions.
- Analyst sources: Forrester’s 2027 B2B predictions (21 Oct 2026) and Gartner’s agentic AI forecast (25 Jun 2025).
- Aissist’s self-audit uses only its own public pages as of 26 Oct 2026. Aissist figures: 83% average resolution, 4.8/5.0 CSAT (vendor-claimed).
- Disclosure: this is Aissist’s site, and Aissist sells AI agents. It appears in its own audit, weak answers included.

The problem
Why do vendor-written AI agent evaluation checklists fail buyers?
Vendor-written checklists ask about features the vendor has, not commitments the buyer can enforce. Of the four checklists ranking for this query, none asks how escalations are billed or for a subprocessor list. Fini’s guide evaluates nine platforms and ranks Fini first. Parloa, Fin and Ada publish neutral-sounding frameworks that close on a demo of their own product.
That gap now has a price. Forrester’s 2027 predictions say AI agents will influence 75% of B2B purchase decisions, and that two-thirds of providers will lose deals because buyers cannot verify their claims. The buyer’s own AI is now the fact-checker.
“These tools rapidly synthesize provider claims and check facts.”
Credit where due: Ada’s guide does tell buyers to get the resolution definition in writing. It just doesn’t ask what happens to the bill, the data or the knowledge base afterwards. Most vendors in this category call their AI agentic. Gartner estimates only about 130 of thousands of agentic AI vendors are real, so the RFP has to do the sorting.
The question bank
What questions should you ask an AI customer service vendor?
Ask 24 questions across four phases — pre-RFP screening, evaluation, contract, and the first 90 days — and require a written answer to each. Questions 6–13 are the core block to send every vendor. The right-hand column is the part no vendor checklist includes: how you check the answer once the vendor no longer needs to impress you.
| # | Question to put in the RFP | How to verify it after signing |
|---|---|---|
| Phase 1 — Pre-RFP screening | ||
| 1 | Does deploying your agent require replacing our helpdesk? | Pilot on your own helpdesk; tickets must stay there. |
| 2 | Which actions can the agent take in our systems, and which are read-only? | Trigger each listed action in the pilot. |
| 3 | Provide your current subprocessor list, including every LLM provider. | Match it to the DPA annex; require notice of changes. |
| 4 | Do you train shared models on our conversations? | Get a “no” as a contract clause. |
| 5 | Which security certifications do you hold, and which are only “aligned”? | Request the certificate and its scope. |
| Phase 2 — Evaluation: ask every vendor | ||
| 6 | Define a “resolved” conversation in one sentence we can put in the contract. | Apply it yourself to 200 random conversations. |
| 7 | Does a conversation that ends in customer silence count as resolved? | Split silent endings from confirmed ones. |
| 8 | Are conversations escalated to a human billed, and at what rate? | Reconcile invoice lines with helpdesk handovers. |
| 9 | Is your resolution rate measured against all inbound conversations, or only those the AI attempted? | Recompute it from a raw export. |
| 10 | Who audits the resolution rate, and can we see the audit sample? | Monthly sample, with a reason per score. |
| 11 | What is your error rate, and how do you grade error severity? severity scale → | Count errors by severity in a QA sample. |
| 12 | Run the agent on 50 historical tickets we choose. | Blind-grade against human answers. |
| 13 | What is the total cost at our volume, including platform fees, seats and minimums? | Compare the first three invoices to the quote. |
| Phase 3 — Contract and deployment | ||
| 14 | Can we export full transcripts, message content included, in JSON at any time? | Run an export during the pilot. |
| 15 | Can we export the agent’s instructions, knowledge and workflow logic? | Export the configuration before go-live. |
| 16 | How many days after termination can we retrieve our data? | Write the number of days into the order form. |
| 17 | What are the renewal term and notice period, and can volume commitments decrease? | Check the order form, not the MSA summary. |
| 18 | What context reaches the human agent on escalation? | Inspect 20 escalated tickets. |
| Phase 4 — First 90 days | ||
| 19 | What share of conversations do you score, and against whose standard? | Confirm coverage; the rubric is your QA guideline. |
| 20 | Can we see every scored conversation with the reason for its score? | Spot-check 20 scores a week. |
| 21 | What share of “resolved” customers contact us again within seven days? | Query the helpdesk for same customer, same issue. |
| 22 | Do you report CSAT for AI conversations separately from human ones? | Check the response rate behind the score. |
| 23 | Who is accountable when resolution falls below the contracted rate? | Named owner and remedy in the SLA. |
| 24 | How fast do you surface contact reasons the agent cannot handle? | Compare the gap report with escalations. |
The downloadable version adds a “what a good answer looks like” column and blank cells for each vendor’s answer, evidence link and score.
After signing
How do you verify an AI vendor's resolution rate after signing?
Pull 200 random AI-handled conversations each month and re-score them yourself against the contract’s definition of “resolved.” Aissist’s deflection vs resolution guide describes four checks: count same-issue repeat contacts within seven days, separate confirmed endings from silent ones, report handovers as their own line, and confirm the denominator. The guide cites Aissist’s AI Customer Service Benchmark 2026 for a 20–40 point gap between deflection and resolution on the same deployment.
Silence is the expensive one, and vendors know it.
“If a frustrated customer stops responding, does that count as 'resolved'?”
Sampling 200 conversations is a floor, not a QA program. Aissist’s Agent Insight page, citing Solidroad, puts typical manual QA coverage at 1–2% of conversations; Agent Insight itself scores 100%. Whichever tool you use, the test is the same: every score links to the conversation and states its reason, and the rubric is yours. If the vendor scores itself, the scorecard is marketing.

The checks also catch scope inflation. Gartner’s warning applies after the demo as much as before it.
“Many use cases positioned as agentic today don't require agentic implementations.”
Self-audit
How does Aissist answer its own question bank?
Aissist answers the billing and helpdesk questions well, and the data-exit and subprocessor questions badly. We ran the bank against Aissist’s own public pages on 26 Oct 2026, accepting only what a buyer could find in writing. Aissist reports 83% average resolution and 4.8/5.0 CSAT on its evaluable AI page — vendor-claimed figures, which is precisely why questions 6–10 exist.
| Question | Aissist’s public answer (26 Oct 2026) | Verdict |
|---|---|---|
| 1 · Replace the helpdesk? | No — runs on top; the helpdesk stays the system of record (lock-in analysis) | Strong |
| 3 · Subprocessor list | Not published; the security page names AWS and Azure, no LLM provider (security) | Gap |
| 5 · Certifications | ISO 27001 certified; SOC 2 aligned, not certified | Partial |
| 6 · Resolution definition | Counted when the AI fully resolves the request without escalation (pricing) | Strong |
| 7 · Silence | Not addressed | Gap |
| 8 · Escalation billing | Cases handed over to a human are not charged (pricing) | Strong |
| 14–15 · Export | No transcript export documented; configuration is import-only | Gap |
| 16 · Post-termination window | Not published | Gap |
Four gaps out of eight is not a flattering scorecard. It is the honest one, and a buyer would find it in an afternoon. Our pricing models comparison covers how other vendors answer question 8.
Verdict
Ask for the measurement, not the number
A resolution rate is a claim; a written definition plus a monthly audit sample is a commitment. The vendor checklists ranking today help you compare features. This bank helps you hold a vendor to what it said, using the export, the invoice and the helpdesk you already own. If a vendor will not answer question 6 in writing, treat its per-resolution price as a per-conversation price. Send questions 6–13 to every shortlisted vendor, put the answers to 6, 8, 14 and 16 into the order form, and check where your current numbers sit with the industry benchmark tool. Then run Phase 4 every month, including on us.
FAQ
Frequently asked questions
What should a conversational AI RFP include?
A conversational AI RFP should include a contract-ready definition of "resolved," escalation billing terms, the subprocessor list, transcript and configuration export rights, a post-termination data window, and a method for verifying each answer after signing.
What questions should I ask an AI customer service vendor first?
Start with the definition of a resolved conversation, whether silent endings count, whether escalations are billed, and whether the resolution rate's denominator is all inbound conversations or only those the AI attempted. These four determine what the headline number means.
How do I verify an AI agent's resolution rate?
Re-score a random sample of about 200 AI-handled conversations each month against the contracted definition. Check seven-day repeat contacts, separate silent endings from confirmed ones, and recompute the rate from a raw export rather than the vendor dashboard.
Should escalated conversations be billed?
Under per-resolution pricing, conversations handed to a human should not be billed as resolutions. Ask the vendor to state this in writing, then reconcile each invoice against the handover count in your helpdesk.
What is agent washing?
Agent washing is Gartner's term for rebranding chatbots, assistants or automation tools as AI agents without substantial agentic capabilities. Gartner estimates only about 130 of thousands of agentic AI vendors are real.
How long should an AI agent pilot run before signing?
Long enough to run every verification step once: an export, an invoice reconciliation, 20 escalated tickets and one 200-conversation audit. For most teams that means at least one full billing cycle.
Can I keep my helpdesk when I deploy an AI agent?
Yes, if the agent is helpdesk-agnostic and runs on top of your existing helpdesk. Ask question 1 in writing: if deployment requires migrating tickets, removing the AI later also means a helpdesk migration.
Is there a free AI agent RFP template?
Yes. Aissist publishes this 24-question bank as a free spreadsheet with a verification method for every question, plus blank columns for each vendor's answer, evidence link and score. It includes the questions Aissist itself answers badly.
Put us through the same 24 questions.
Bring the spreadsheet to a working session and we will answer every line in writing — gaps included.