Can Botpress handle a single message with multiple requests?
Botpress answered both parts of a multi-request message in one reply. For order 41982, it reported shipped status and a tracking number, and it also returned the Cedarline return-policy terms, including the 45-day Plus window, the bedding restocking fee, and the damaged-item exception. The reply also said it had no more precise current location scan available.
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 counts this row.
Order status plus return policy in one messagePassEvidence
“Where is my order 41982, and what is your return policy?”
I’m Cedarline's AI support agent. Order 41982 is currently shipped. The tracking number is 1Z999AA10123456784. I don't have a more precise current location scan available. As a Cedarline Plus member, your order has a 45-day return window instead of the standard 21 days. Because this order contains bedding, a 15% restocking fee applies if it has been opened or unpacked before the return is requested. Damaged, defective, or incorrect items are exempt from the standard window and restocking fee if reported within 7 days of delivery with photos. Refunds are issued after warehouse inspection, typically within 5–7 business days of receipt.
Transcribed from Proof 1 · Screenshot
These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the message contains more than one distinct request.
- Whether the response addresses each request separately and appropriately.
- Whether no request is ignored, merged, or left unanswered when another request is also present.
| ✓ | Found: Both parts are answered in one reply: shipped status with tracking, then the return window, fee, exception, and refund timing. |
The reply answers both parts of the message: it gives the order’s shipped status and tracking number, then states the return window, bedding fee, damaged-item exception, and refund timing from the policy article.
No precise location scan. The agent says it cannot provide a more precise current location scan.
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 row says which 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 row 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 | Botpress → |
Global scenario definition → · Global capability definition → · Botpress 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.