Does Kommunicate update its answers when a customer corrects earlier information?
Kommunicate passed this conversation-continuity case: after the customer corrected the order number, it answered only about the new order and dropped the first one. The final reply names 41830 and leaves out 41982.
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 · Original order number: “Where is order 41982?”
Input 2 · Corrected order number: “Sorry, wrong number - it's 41830”
Response 1 answers Input 1.
Response 2, the final response, answers Input 2.
Order #41830 is currently "processing". Estimated delivery: Wednesday, September 9, 2026.
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (2)
- Answer for order 41982
Order #41982 is currently "shipped". Tracking number: 1Z999AA10123456784 (UPS). Estimated delivery: Thursday, September 3, 2026.
- Answer for order 41830
The final response, printed above.
| ✓ | Expected: Answer about the corrected order and drop the first orderFound: The second reply is only about 41830 and leaves out 41982, including its shipped status, tracking number, and September 3 date. |
It answered the corrected order and left out the first one, so the later correction controlled the reply. The final answer is only about 41830 and gives none of 41982's details.
Canned opener. The opening bot message and quick-reply chips appeared before the customer's first message; they were the bot's canned opener, not a reply to the test.
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 | Kommunicate → |
Global scenario definition → · Global capability definition → · Kommunicate 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.