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

Does Zendesk AI let an operator submit a correction to one of its answers?

Zendesk AI offered no way to submit a correction to one of its earlier answers on the conversation screen where those answers are read. That screen's only menu held an export option, the conversation overview offered only a field for adding labels, and no rating, flag or correction option appeared on the agent's replies.

1 of 1 test case failed

Every test case in this scenario has a result.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Submit a correction for one wrong answerFailEvidence
What we sent

We opened the agent's earlier conversations in the product to submit a correction against one of its answers; the screen offered no way to submit one, so nothing was sent.

What the tool returned

Nothing came back from the product for this request, so there is no reply to show.

Expected vs. Found
✗Expected: Zendesk AI accepts feedback or a correction submitted against one of its earlier answers.Found: Nothing to submit a correction with: the only menu held 'Export (XLSX)', the conversation overview offered only a labels field, and the agent's replies showed no rating, flag or correct option.
Supporting proof
Proof 1Screen recording
Screen recording: the conversation screen's menu, overview panel and replies, with no correction option
Key moments
Open original ↗
Why this result

It is a Fail, not Not gradable: the test needed a correction submitted against one of the agent's earlier answers, and the conversation screen where those answers are read offers no way to submit one, so the step could not be performed.

Tested by Ajay Vekhande · evidence dated 3 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
An earlier conversation in which the AI agent gave a wrong answer had to exist, and a correction to that answer had to be submitted through the product.
Tested
3 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.

LevelNameScope
BenchmarkAI Customer Support Chatbots →26 scenarios · 14 tools
CapabilityFeedback and learning →
ScenarioFeedback can be submitted →
ToolZendesk AI →

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
8 October 2026First publishedAI Customer Support Chatbots v1
17 November 2026Updated — retested
The result is unchanged: 0 pass · 1 fail. The earlier result stays readable. Read the earlier result →

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/feedback-can-be-submitted · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-17

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 recordingffd275d3bdb5d8d1aa01c5bea974ee0ab0d6989857701e80c3bf815ae7eeb22f