Can Freshdesk Freddy handle a customer correcting information given earlier?
Freshdesk Freddy switched to the corrected order without carrying over details from the first. It answered with the dinnerware order's processing status, not the linen-sheet order's details.
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 · Initial order question: “Where is order 41982?”
Input 2 · Corrected order number: “Sorry, wrong number - it's 41830”
Order-number confirmation
I can help with that. Please confirm the order number you want to track (for example: 41982) so I can look it up.
Answer after the correction
Your order for the 12-piece Stoneware dinnerware set is currently processing. It's estimated to arrive by September 9, 2026, at 1470 Blake Street, Apt 6B, Denver, CO 80202.
Transcribed from Proof 1 · Screen recording at 0:18
Every message the tool sent, in order (2)
- Order-number confirmation
Printed above.
- Answer after the correction
The final response, printed above.
| ✓ | Expected: Answer about the corrected order and stop using the original order.Found: It reported the corrected 12-piece stoneware dinnerware order as processing; the original order was for linen sheets, which the final reply did not mention. |
The reply used the corrected order's item and address and left out the original order, establishing that the correction replaced the earlier number. The arrival date cannot be assessed: the later order-system screenshots do not show the data available during the chat.
Confirmation before the correction. For the initial order-status question, the agent asked for confirmation of the number. The customer corrected it before receiving any status information about that 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 | Freshdesk Freddy → |
Global scenario definition → · Global capability definition → · Freshdesk Freddy 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.