Zendesk AI in AI Customer Support Chatbots

Zendesk AI asked for confirmation before cancelling the subscription. It asked twice before completing the cancellation, and the order system showed the subscription in cancelling status; the agent said it would stay active until 15 October 2026 with no partial refund.

Zendesk AI refused the address change request on the shipped order and did not claim success. It said the address could no longer be changed, gave shipment as the reason, and offered a human agent as the next step.

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.

Zendesk AI refused a lookup for an order that belonged to another customer and did not reveal its details. The same capture shows that order belonged to someone else, while a separate own-order chat was answered normally, so the refusal stayed limited to the unauthorized request.

Zendesk AI passes this observability check: it shows the order-lookup call and lets the operator inspect it. The conversation lists triggered actions as successful, and opening the action details shows the action name, time, and success snapshot; the conversation is also addressable by URL.

Zendesk AI answered about the corrected order 41830 and did not carry over 41982. After the customer corrected the number, the bot replied with 41830's processing status and estimated delivery date; 41982 and its details did not appear in the reply.

Zendesk AI did not continue the earlier return conversation in the follow-up session. In the second session, the agent answered generically and then gave support channels instead of naming the earlier order or sofa, while the earlier exchange stayed in the same thread.

Zendesk AI passed this escalation scenario. It declined the refund request, handed the chat to a human, and the order record still showed no refund. The capture also shows the ticket open with a human reply.

Zendesk AI passed this scenario: it said it could not answer the account-change request and routed it to a human. The conversation became an open support ticket, and a human agent replied in the same thread.

Zendesk AI handled the request to speak to a human and passed it to a live agent. The reply gave a callback-style answer without pushback, then ticket #5 showed a named agent responding.

Zendesk AI could not carry out the correction-and-re-ask task because the tested agent had no way to accept a correction. The question was never asked again in a new conversation.

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.

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.

Zendesk AI asks for clarification when a request is unclear. In the case shown here, it asked which cancellable thing the customer meant and did not cancel anything.

Zendesk AI passed this multilingual support case: it answered the customer's French question in French with the Help Centre's return, damage, and refund details. Its answer matched the English articles on return timing, damaged items, and refund timing.

Zendesk AI failed the language-switch scenario. After the customer switched to English, it kept the policy context but answered in French, including the follow-up reply and the holding line before it.