AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 12 November 2026

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.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent

Input 1 · Initial order question: “Where is order 41982?”

Input 2 · Corrected order number: “Sorry, wrong number - it's 41830”

What the tool returned

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)
  1. Order-number confirmation

    Printed above.

  2. Answer after the correction

    The final response, printed above.

Expected vs. Found
✓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.
Supporting proof
Proof 1Screen recording
Screen recording: the customer's order-number correction and the agent's response
Key moments
Open original ↗
Proof 2Screenshot
Order-system screenshot: the corrected order's dinnerware item and delivery address, shown later
Open original ↗
Proof 3Screenshot
Order-system screenshot: the original order's linen sheets, shown later
Open original ↗
Why this result

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.

Also observed in this test case

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.

Tested by Ajay Vekhande · evidence dated 5 September 2026

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.

Software that produced the output
Freshdesk Freddy
Build or version
Not exposed by the hosted product
Plan or tier
Free Enterprise trial
Surface
Web app
Set up before the run
The initially supplied linen-sheet order and the corrected dinnerware order both had to exist in the store's order system.
Run mode
AI Agent Preview mode
Tested
5 September 2026 · Ajay Vekhande

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
13 November 2026First publishedAI Customer Support Chatbots v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-customer-support-chatbots/results/freshdesk/customer-corrects-information-given-earlier · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-12

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.

Proof 2 · Screenshot ↗image/png · 41 KB
Proof 3 · Screenshot ↗image/png · 45 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recording0c07f01a1a73b8efa5b56291a0fd5725c2b1617cb20a9565892f72862b458103
Proof 2 · Screenshot9076e833ec6febecc9a36b1552b420dbbadff18632b1eb2bbfa22743a6e88102
Proof 3 · Screenshota65d74ca8be00867464cd616c2ca46500bc3cf2ab37dada3f16922a59622069c