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

Does Zendesk AI keep earlier customer details for later chat turns?

Zendesk AI used an earlier order number to answer a later delivery question without asking for it again. It correctly identified UPS as the carrier and reported that the order was shipped and not yet marked delivered.

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.

Order number given at t1, needed at t2PassEvidence
What we sent

Input 1 · Customer's first turn: “My order is 41982”

Input 2 · Customer's second turn: “when it will arrive?”

What the tool returned

Response 1 (Agent's offer of help) is a question the tool asked about Input 1; it is not an answer.

Agent's offer of help How may I assist you with this order? I can help check its status, change the delivery address or carrier, or request a refund. Arrival answer using the earlier order number Your order 41982 was shipped with UPS. Its estimated delivery date was October 14, 2026, and the tracking number is 1Z999AA10123456784. The order is not marked as delivered yet.

Transcribed from Proof 1 · Screenshot

Expected vs. Found
✓Expected: Use the order number supplied earlier to answer the later delivery question without asking for it again.Found: It answered without asking for the number again. The reply and the store's order system both gave October 14, 2026 as the estimated delivery date.
Supporting proof
Proof 1Screenshot
Chat screenshot: the earlier order number used to answer the delivery question
Open original ↗
Proof 2Screenshot
Order system screenshot: the carrier, tracking details, estimated delivery date and delivery status
Open original ↗
Why this result

The answer required the earlier order number. Zendesk AI reused it without asking again and gave accurate shipping and delivery information for that order.

Tested by Ajay Vekhande · evidence dated 15 October 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
Zendesk AI
Build or version
Not exposed by the hosted product
Plan or tier
Suite – Professional (Free trial)
Surface
Web app
Set up before the run
A shipped order had to be available in the store's order system, with its number supplied before the follow-up arrival question.
Tested
15 October 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/zendesk/conversation-context-retention · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-15

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 1 · Screenshot ↗image/png · 41 KB
Proof 2 · Screenshot ↗image/png · 42 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshot9fd4cba3fa9622d1f5414d0a66291bf82070bd2439e7bde90c03bca4b260f6f5
Proof 2 · Screenshot7acc7e5123a3a29ec8b5449112025edb3a7589d2c0d1818ed48ab14a99df4562