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

Does Zendesk AI's analytics match what actually happened?

Zendesk AI's reporting overview for 23 September to 15 October 2026 showed 50 conversations and 11 assisted escalations, and all 25 of our earlier test conversations, including the three escalation tests, appear in its conversation logs. Its totals contain our runs; the extra conversations are other traffic on the same agent.

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.

Product's counts vs our recordsPassEvidence
What we sent

No message was sent: the counts were read from Zendesk's reporting overview and conversation logs.

What the tool returned

The tool's response has no text to quote: it is what the evidence under Proof shows.

Proof 1 · Screen recording · ▶ 3:56–3:59

Expected vs. Found
✓Expected: The product's conversation and escalation numbers agree with our own record of the test runs.Found: The dashboard reported 50 conversations and 11 assisted escalations for the period; our record holds 25 conversations, 3 of them escalations, and each appears in the conversation logs.
Supporting proof
Proof 1Screen recording
Screen recording: our query list matched to the conversation logs, then the reporting overview
Key moments
Open original ↗
Why this result

The case asks whether the product's counts agree with our record of the runs. Every one of our 25 conversations and 3 escalations is inside its totals and none of its counts is below ours, so it passes. The agreement is containment: the dashboard counts all traffic on the agent, not just our tests.

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
We kept our own list of the 25 earlier support test conversations, three of them escalations. The task was to read Zendesk's conversation and escalation counts for the test period and compare them with that list. Nothing was sent to the AI agent.
Reporting time frame
23/09/2026 - 15/10/2026
Conversation source
AI agent
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
16 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/analytics-accuracy · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-16

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.

Proof 1 · Screen recording43f78556bc2aad0ae67583c687ff908836de44e4fcf15d810080b24253e64812