Can Respond.io keep a conversation on track after a customer corrects information?
Respond.io handled the correction and kept the answer on the updated order. After the customer changed the number, the reply covered only 41830: it said the order was processing, gave an arrival date of November 2, 2026, and said there was no tracking number yet.
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.
Wrong order number corrected at t2PassEvidence
Input 1: “Where is order 41982?”
Input 2: “Sorry, wrong number - it's 41830”
Response 1 answers Input 1.
Response 2, the final response, answers Input 2.
Thanks for the correction! Order 41830 is processing and is estimated to arrive November 2, 2026. There isn't a tracking number yet; tracking is generated once the order ships.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (2)
- Response to input 1
Order 41982 has shipped via UPS. You can track it with number 1Z999AA10123456784; the estimated delivery date is October 27, 2026. I don't have a live location update.
- Final response
The final response, printed above.
| ✓ | Expected: Answers about the corrected order and leaves out the first oneFound: After the correction, the reply is entirely about 41830: it says the order is processing, gives November 2, 2026, and says there is no tracking number yet. |
The conversation had to stay with the corrected order instead of blending both orders. After the number was fixed, the reply was entirely about the new order and did not return to the first one.
Extra status note. The first reply also says there is no live location update for the shipped order.
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 | Conversation continuity → | |
| Scenario | Customer corrects information given earlier → | |
| 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.