Can Freshdesk Freddy continue an earlier support conversation?
Freshdesk 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 of 1 test case passed
Every test case in this scenario has a result.
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.
Return discussed in session 1, followed up in session 2PassEvidence
Input 1: “Hi, I'd like to return order 41455 - I ordered the wrong sofa.”
Input 2: “I'm following up on my return.”
Input 3: “same order”
Response 1 answers Input 1.
Response 2 answers Input 2.
Response 3, the final response, answers Input 3.
Thanks for confirming. Once your sofa is received back at our warehouse, returns are inspected and refunds are typically processed within 5–7 business days. The refund is then sent back to your original payment method, and how long it takes to appear depends on the method: - Credit/debit card: usually 5–7 business days - PayPal: usually 3–5 business days - Store credit/gift card: applied instantly If you tell me when you shipped or dropped off the return and how you sent it (carrier or pickup), I can help you estimate where you are in that timeline.
Transcribed from Proof 1 · Screen recording at 1:03
Every message the tool sent, in order (3)
- Response to input 1
Your order for the Aspen 3-seat sofa — Walnut is delivered and you have 45 days from delivery to return it. The amount paid is $812.50.
- Response to input 2
I can help with that. To check the status, I need to know which return you're asking about. Is this about your return for order 41455 (the Aspen 3-seat sofa — Walnut), or a different order? If it's a different one, please share that order number.
- Final response
Thanks for confirming. Once your sofa is received back at our warehouse, returns are inspected and refunds are typically processed within 5–7 business days. The refund is then sent back to your original payment method, and how long it takes to appear depends on the method: - Credit/debit card: usually 5–7 business days - PayPal: usually 3–5 business days - Store credit/gift card: applied instantly If you tell me when you shipped or dropped off the return and how you sent it (carrier or pickup), I can help you estimate where you are in that timeline.
| ✓ | Expected: Resume the return thread without the customer re-explaining itFound: The agent resumes the return discussion, asks which return is meant, then gives the refund timeline after the customer says “same order”. |
It is a pass because the customer returns to the same return thread, the agent asks which return is being discussed, then gives the refund timeline after “same order” without the order number or item being repeated.
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.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
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.
- 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.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Customer Support Chatbots → | 26 scenarios · 13 tools |
| Capability | Conversation continuity → | |
| Scenario | Earlier conversation/session needs to be continued → | |
| Tool | Freshdesk Freddy → |
Global scenario definition → · Global capability definition → · Freshdesk Freddy product page →
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.
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.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →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.