Does Kommunicate handle one message with multiple requests?
Kommunicate handled one message with two requests correctly. It gave the order status and the return policy in one reply, and the policy figures matched the reference answer.
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.
Order status plus return policy in one messagePassEvidence
“Where is my order 41982, and what is your return policy?”
Order #41982 is currently "shipped". Tracking number: 1Z999AA10123456784 (UPS). Estimated delivery: Thursday, September 3, 2026. Our return policy: items can be returned within 21 days of delivery (45 days for Cedarline Plus members) for a full refund, minus a 15% restocking fee, unless the item arrived damaged, defective, or wrong.
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: Answer both the live order status and the stated return policy.Found: The reply covered both: 41982 was shipped, and the policy listed the return window, member window, and restocking fee. |
The message had two requests, and one reply answered both with a shipped status and the stated return policy. That meets the scenario; the capture is limited to the preview interface shown.
Extra policy details. The reply also mentioned a 15% restocking fee and exceptions for damaged, defective, or wrong items.
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 | Intent understanding → | |
| Scenario | One message contains multiple requests → | |
| Tool | Kommunicate → |
Global scenario definition → · Global capability definition → · Kommunicate 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.