Can Botpress handle a customer correcting information given earlier?
Botpress handled a customer correcting information given earlier in the visible chat. The agent first answered about one order, then switched to the corrected order and said it was processing with no tracking number. The first order's shipped status and tracking number did not carry over.
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 counts this row.
Wrong order number corrected at t2PassEvidence
Input 1: “Where is order 41982?”
Input 2: “Sorry, wrong number - it's 41830”
Response to input 1 Order 41982 is shipped. Your tracking number is 1Z999AA10123456784. Response to input 2 I'll check order 41830 now. Response to input 2 Order 41830 is currently processing. No tracking number is available yet.
Transcribed from Proof 1 · Screenshot
Transcribed from Proof 1 · Screenshot
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: Answers about the corrected order and drops the firstFound: It answered only about the corrected order as processing with no tracking number; the first order's shipped status and tracking number did not carry over. |
The chat was checked for whether the agent kept using the corrected order after the customer changed the number. It switched to the new order and replied only about that order as processing with no tracking number.
Status from reply. The order status appears in the agent's reply; the underlying order system is not shown separately.
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 row says which 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 row 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 | Conversation continuity → | |
| Scenario | Customer corrects information given earlier → | |
| 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.