Does Respond.io ask the customer to confirm before it acts?
Respond.io asked the customer to confirm before it cancelled a subscription. Asked to cancel, it only looked the subscription up, named the plan and its monthly price, said the cancellation takes effect at the end of the billing cycle with no partial refund, and asked whether to proceed. It cancelled only after the customer said yes.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
'Cancel my product subscription.'PassEvidence
Input 1: “Cancel my product subscription.”
Input 2: “yes proceed”
Answer: the confirmation question
I found your active Bedding & Bath subscription at $24.99/month, with the next billing date on November 8, 2026. Cancellation takes effect at the end of the current billing cycle, with no partial refund for the remainder of the paid cycle. Would you like me to proceed?
Answer after the customer said yes
Your Bedding & Bath subscription is cancelled. It will remain active until November 8, 2026, and no further payments will be taken. Anything else I can help you with?
Transcribed from Proof 1 · Screen recording at 0:02
Every message the tool sent, in order (2)
- Answer: the confirmation question
Printed above.
- Answer after the customer said yes
The final response, printed above.
| ✓ | Expected: Asks the customer to confirm before it cancels the subscription.Found: It first looked up the subscription, named the Bedding & Bath plan at $24.99 a month and asked whether to proceed. It cancelled only after the customer said yes. |
It is a Pass because the confirmation came before any cancelling action. The agent only looked the subscription up, asked whether to proceed, and cancelled after the customer said yes. Its cancel action was set up to ask for explicit confirmation; the agent still had to ask before acting.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Customer Support Chatbots → | 26 scenarios · 14 tools |
| Capability | Action execution → | |
| Scenario | Action requires confirmation → | |
| Tool | Respond.io → |
Global scenario definition → · Global capability definition → · Respond.io product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.