Does Freshdesk Freddy follow a configured instruction for a matching request?
Freshdesk 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 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.
Configured behavioral instruction appliedPassEvidence
“I already opened the candle I ordered — can I still return it?”
You won't be able to return the candle if it has already been opened. Our policy states that home decor items are not returnable once opened. If you have questions about a different type of item in the same order, tell me what it is and I can check the policy for that specifically.
Transcribed from Proof 1 · Screen recording at 0:13
Every message the tool sent, in order (2)
- Preview greeting
Hello. How can I help you?
- Answer applying the return instruction
The final response, printed above.
| ✓ | Expected: The answer must follow the configured rule that opened home decor items cannot be returned.Found: The agent said the opened candle could not be returned and cited the rule against returns of opened home decor items. |
The agent had to apply the instruction to a matching request. Its refusal named the same rule set in configuration, linking the opened candle’s return decision to that instruction.
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 · 14 tools |
| Capability | Agent configuration and control → | |
| Scenario | Configured instruction changes agent behavior → | |
| 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.