Tool in benchmark · Version 1

Zendesk AI in AI Customer Support Chatbots

Scenario-level performance from current published Results.

6 scenarios with published Results · 26 scenarios in the benchmark

How Zendesk AI performed

Open a capability to explore its scenarios. Each row reports the test set in its published Result; counts are not combined into an overall score.

Action execution5 scenarios · 2 with published Results
ScenarioPublished outcomesTest coverageResult
Retrieve information from an external system
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Zendesk AI retrieved information from an external system and reported the returned order status. For order 41982, the conversation log shows the Check Order Status action firing successfully and returning shipped, UPS, tracking number 1Z999AA10123456784, and estimated delivery 2026-09-22; the customer reply repeats those same fields. The recording shows the action firing and returned fields, but not the HTTP request line or endpoint.

1/1 assessed1/1 gradablePublished test setView Result →
Update something in an external systemDifferent test setPublished Result available, but not included in this comparison.View Result →
Action requires confirmationNo published result
Requested action cannot be completedNo published result
User is not authorized to perform the actionNo published result
Conversation continuity3 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
Customer corrects information given earlier
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Zendesk AI handled a customer correcting information given earlier by answering about the corrected order and leaving the first order out. The visible exchange shows the customer changing 41982 to 41830, then the bot replying only about 41830 with a processing status and a 2026-09-28 delivery estimate. The screenshot does not show a lookup result for 41982.

1/1 assessed1/1 gradablePublished test setView Result →
Earlier conversation/session needs to be continuedNo published result
Information from earlier in the conversation is needed laterNo published result
Escalation and human handoff3 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
User explicitly asks for a human
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Zendesk AI hands off a user who explicitly asks for a human without arguing. It replies, “No problem, please leave your details and someone will get back to you soon,” and the visible thread then shows a human agent replying in the same conversation. The recording ends before the final seconds, and the console does not show the ticket’s full audit trail, so the exact creation route is not shown.

1/1 assessed1/1 gradablePublished test setView Result →
A configured rule requires escalationNo published result
Agent cannot resolve the requestNo published result
Feedback and learning2 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
Feedback can be submitted
0 Pass1 Fail0 Not gradable
1 of 1 test case failed
What happened

Zendesk AI did not provide a way to submit feedback in the tested conversation surface. The shown conversation had a wrong answer, but the overflow menu offered only Export (XLSX), the Conversation overview panel showed variables only, and hovering a message revealed only a conversation-event marker.

1/1 assessed1/1 gradablePublished test setView Result →
Correction changes future behavior where the product claims learningNo published result
Intent understanding3 scenarios · 1 with published Results
ScenarioPublished outcomesTest coverageResult
One message contains multiple requests
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Zendesk AI answered both requests in one reply to a message that asked for order status and return policy. It said order 41982 had shipped with UPS, and it gave the 21-day standard return window, the 45-day Cedarline Plus window, and the resalable-condition/original-packaging guidance.

1/1 assessed1/1 gradablePublished test setView Result →
Request is unclear and needs clarificationNo published result
Request requires choosing the correct source or actionNo published result
Agent configuration and control2 scenarios · 0 with published Results
ScenarioPublished outcomesTest coverageResult
Configured instruction changes agent behaviorNo published result
Configured restriction is respectedNo published result
Analytics and observability3 scenarios · 0 with published Results
ScenarioPublished outcomesTest coverageResult
Agent actions/tool calls can be inspectedNo published result
Conversation activity can be inspectedNo published result
Reported analytics match what actually happenedNo published result
Knowledge-grounded answering3 scenarios · 0 with published Results
ScenarioPublished outcomesTest coverageResult
Answer is available in the knowledge baseNo published result
Answer is not available in the knowledge baseNo published result
The request uses different wording than the sourceNo published result
Multilingual support2 scenarios · 0 with published Results
ScenarioPublished outcomesTest coverageResult
Customer communicates in another supported languageNo published result
Customer switches languages during the conversationNo published result

Reading these Results

Published evidence and test coverage answer different questions.

Publication availability

Which scenarios have a Result?

A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.

Test coverage

What does each Result cover?

Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.

Scenario scope

Inventory is not testing progress

The 26 scenarios describe this benchmark’s scope. They are not an assumed applicability or test-coverage denominator for Zendesk AI.

Zendesk AI in AI Customer Support Chatbots | AI Demos