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

Does Zendesk AI choose the right source or action for a customer's request?

Zendesk AI passed this order-status case. The conversation shows one custom action between the customer’s question and the reply, and the reply matches the order system’s shipped status, UPS carrier, tracking number, and estimated delivery date.

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 status must come from the order systemPassEvidence
What we sent

Input 1: “Hello”

Input 2: “Where is order 41982?”

What the tool returned

Greeting response

How may I assist you today?

Order-status answer

Your order 41982 has shipped with UPS. The tracking number is 1Z999AA10123456784, and the estimated delivery date is 2026-09-22.

Transcribed from Proof 1 · Screen recording at 0:00

Every message the tool sent, in order (4)
  1. Opening greeting

    Hey there, how can I help you today?

  2. Greeting response

    Printed above.

  3. Order-status answer

    The final response, printed above.

  4. Satisfaction prompt

    How would you rate your experience?

Expected vs. Found
✓Expected: Uses the order system, not the KB, and answers with the real status.Found: The reply follows a custom action and matches the order system’s shipped status, UPS carrier, tracking number, and estimated delivery date.
Supporting proof
Proof 1Screen recording
Conversation log with the order question, custom action, and reply
Key moments
Open original ↗
Proof 2Screenshot
Order system response body with the shipped order details
Open original ↗
Proof 3Screenshot
Chat widget showing the order reply
Open original ↗
Why this result

The customer asked for order status, the agent used a custom action before replying, and the reply matches the order system’s shipped status, UPS carrier, tracking number, and estimated delivery date; the knowledge base had no per-order data.

Also observed in this test case

Extra turns. The agent also sent an opening greeting before the customer’s question and a satisfaction prompt after the answer.

Tested by Ajay Vekhande · evidence dated 23 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
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
The order system already contained the shipped order, and the knowledge base had no per-order data.
Tested
23 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/zendesk/source-action-disambiguation · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-03

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 · 199 KB
Proof 3 · Screenshot ↗image/png · 19 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screen recording1fa9e72837c0ee11b7856662c529fbc3f217687db616b4555bbbc891ab6c8365
Proof 2 · Screenshotb8f85664f184cba69857f7f9a33f6a9135e5f89f693b3489806ec767b2d2cde2
Proof 3 · Screenshota67b170c09f2aec54c3cc3fc036888bf9392621c0f94769652e0253702021cb2