Does Botpress ask for confirmation before taking an action?
Botpress passed this confirmation-before-action scenario. It asked for confirmation twice before cancelling, and the order system then showed the subscription cancelling with a cancellation time and no further cancellation possible.
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”
Input 3: “yes cancel it”
The tool's reply is shown in the evidence under Proof.
Response 1 replies to Input 1.
Response 2 replies to Input 2.
Response 3 replies to Input 3.
Response to input 1 I found one active subscription: • Bedding & Bath — $24.99 USD monthly Would you like me to proceed with cancelling it? Response to input 2 The Bedding & Bath subscription is $24.99 monthly. Nothing has been cancelled yet, and deliveries will continue until 24 October 2026. Please confirm that you want me to finalize the cancellation. Response to input 3 Your Bedding & Bath subscription has been cancelled. No further payments will be taken, and it will remain active until the end of the current billing cycle on 24 October 2026. No partial refund is issued for the remainder of a paid cycle.
Transcribed from Proof 1 · Screen recording at 0:00
Transcribed from Proof 1 · Screen recording at 0:00
Transcribed from Proof 1 · Screen recording at 0:14
| ✓ | Expected: Confirms before cancelling.Found: It asked for confirmation, asked again after the first yes, and only then cancelled. |
The product had to wait for approval before changing the subscription. It asked before acting, asked again after the first yes, and only cancelled after the second yes; the order system then showed the cancellation in effect.
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 · 13 tools |
| Capability | Action execution → | |
| Scenario | Action requires confirmation → | |
| Tool | Botpress → |
Global scenario definition → · Global capability definition → · Botpress 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.