Freshdesk Freddy in AI Customer Support Chatbots
Scenario-level performance from current published Results.
23 of 26 scenarios published
Where Freshdesk Freddy failed
3 of 21 graded scenarios. Open a Result to see the conversation and the evidence.
Information from earlier in the conversation is needed later
Freshdesk Freddy did not keep earlier conversation details available for the follow-up. It answered the first turn with shipment and arrival details, then sent the follow-up to support instead of answering from that context.
View Result →Correction changes future behavior where the product claims learning
Freshdesk Freddy offered no way to correct a past answer, so the correction-and-follow-up scenario could not be carried out. No follow-up question was sent in a new conversation.
View Result →Feedback can be submitted
Freshdesk Freddy offered no way to submit a correction to an earlier wrong answer. The conversation had no feedback option, while Improve promised future suggestions rather than accepting a correction to that answer.
View Result →How Freshdesk Freddy performed
Open a capability to explore its scenarios. Each row reports the test set in its published Result.
Action execution4 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Action requires confirmation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy confirmed before cancelling, so the action was not taken on the first request. In TC16, the first reply to "Cancel my product subscription." asked the user to confirm, and the final cancellation happened only after explicit confirmation. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Requested action cannot be completed | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy refused the requested change and gave a next step when the action could not be completed. It said the delivery address for order 41982 could not be changed because the order had already shipped, then offered UPS tracking 1Z999AA10123456784 and follow-up help without claiming the change worked. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Retrieve information from an external system | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy retrieved information from an external system in this case. It returned shipped, UPS, and a tracking number, and the reply repeated those values while no knowledge sources were used. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| User is not authorized to perform the action | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy refused to share another customer's order details. In the same session, it answered the customer's own order 41982, so the refusal was limited to the other customer's order. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Update something in an external system | No published result | ||
Agent configuration and control2 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Configured instruction changes agent behavior | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy followed the configured instruction when answering a request to return an opened candle. It said the candle was not returnable and cited the policy against returning opened home decor items. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Configured restriction is respected | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy respected the configured restriction in this scenario. It refused the delivery-address change, then offered to check the order details and asked for the order number and current address instead. The reply stayed to one answer, with no transfer or claimed change. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Analytics and observability3 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Agent actions/tool calls can be inspected | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy passed this inspection scenario. The conversation log shows the workflow trigger, the order lookup inputs and outputs, and the agent's reply finishing the workflow. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Conversation activity can be inspected | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy exposed the conversation's activity in enough detail to inspect what happened. In TC22, the opened conversation showed the customer and agent turns, timestamps, an order-details action, workflow completion, status, and linked knowledge sources on the product surface. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Reported analytics match what actually happened | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy reported five human handoffs, matching the reference tally of five. Its workflow totals also covered every benchmark run. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Conversation continuity2 pass1 fail
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer corrects information given earlier | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy switched to the corrected order without carrying over details from the first. It answered with the dinnerware order's processing status, not the linen-sheet order's details. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Earlier conversation/session needs to be continued | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy continued the return conversation when the customer came back in the same thread. It identified the return from the follow-up, accepted “same order,” and then gave the refund timeline without the customer repeating the order number or item. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Information from earlier in the conversation is needed later | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedFreshdesk Freddy did not keep earlier conversation details available for the follow-up. It answered the first turn with shipment and arrival details, then sent the follow-up to support instead of answering from that context. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Escalation and human handoff3 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A configured rule requires escalation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy handed the refund request to a human without issuing a refund. A human replied in the same conversation. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Agent cannot resolve the request | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy routed an unsupported request to change an account email to the Customer Support group, and a human agent replied after the handoff. It did not promise the change. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| User explicitly asks for a human | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy handed the user to a human without arguing. The bot agreed in its next reply, and the user and agent then exchanged messages on the same ticket. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Feedback and learning2 fail
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Correction changes future behavior where the product claims learning | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedFreshdesk Freddy offered no way to correct a past answer, so the correction-and-follow-up scenario could not be carried out. No follow-up question was sent in a new conversation. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Feedback can be submitted | 0 Pass1 Fail0 Not gradable 1 of 1 test case failedWhat happenedFreshdesk Freddy offered no way to submit a correction to an earlier wrong answer. The conversation had no feedback option, while Improve promised future suggestions rather than accepting a correction to that answer. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Intent understanding3 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| One message contains multiple requests | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy answered both requests from one customer message in a single reply. It gave the order’s shipped status and delivery details, followed by the return windows and conditions. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Request is unclear and needs clarification | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy responded to the unclear cancellation request with a clarifying question, without cancelling anything. The question offered a membership, a monthly product subscription and an order as separate choices. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Request requires choosing the correct source or action | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy used the order system to answer the status request and correctly reported that the order had shipped. The reply included the item, delivery address, carrier, tracking number and estimated delivery. | 1/1 assessed1/1 gradablePublished test set | View Result → |
Knowledge-grounded answering2 different test set1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Answer is available in the knowledge base | Different test setPublished Result available, but not included in this comparison. | View Result → | |
| Answer is not available in the knowledge base | Different test setPublished Result available, but not included in this comparison. | View Result → | |
| The request uses different wording than the source | No published result | ||
Multilingual support1 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer switches languages during the conversation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedFreshdesk Freddy kept up when the customer switched from French to English. Its French answer gave a 21-day standard return window and 45 days for Cedarline Plus members; asked in English, it answered in English, confirmed the 45-day Plus window and offered to work out the exact last return day. | 1/1 assessed1/1 gradablePublished test set | View Result → |
| Customer communicates in another supported language | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
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.
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.
Out of 26 scenarios
The summary counts each of the 26 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Freshdesk Freddy was tested on it.