Does Intercom Fin answer multiple requests in one message?
Intercom Fin answered both requests in one message. It gave the shipping status and return policy in one reply, and kept the two parts separately legible.
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?”
The tool's reply is shown in the evidence under Proof.
Your order #41982 has already shipped. Carrier: UPS. Tracking number: 1Z999AA10123456784. Shipped: Oct 4. Estimated delivery: Oct 7. Delivery address: 1470 Blake Street, Apt 6B, Denver, CO 80202. You can follow the shipment using the UPS tracking number above. Return policy: Standard return window: 21 days from delivery. Plus members: 45 days from delivery. Items must be in resalable condition with original packaging if possible. Opened bedding or rugs may have a 15% restocking fee deducted from the refund.
Transcribed from Proof 1 · Screenshot
| ✓ | Expected: Answers both requests: the live status and the stated policyFound: Fin answered both in one reply: the shipment status and the return policy were both present, with neither request dropped or deferred. |
The customer sent one message with two requests, and Fin answered both without dropping either. It gave the shipping status and the policy in separate parts, which matches the required behavior.
Two requests kept apart. The reply handled the two requests in separate parts, so the order status and policy stayed easy to tell apart.
The order number, tracking number, and address shown are test-store data.
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 | Intent understanding → | |
| Scenario | One message contains multiple requests → | |
| Tool | Intercom Fin → |
Global scenario definition → · Global capability definition → · Intercom Fin 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.