Can Botpress use earlier conversation context later?
Botpress kept earlier conversation context across the two turns. The second reply used the first turn's order number to give the delivery date and tracking number, and it did not ask for the number again.
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 number given at t1, needed at t2PassEvidence
Input 1: “My order number is 41982”
Input 2: “When will it arrive?”
Response 1 answers Input 1.
Response 2, the final response, answers Input 2.
Response 3, the final response, answers Input 2.
The estimated delivery date was September 3, 2026, so your order is now delayed. Its current status is shipped, with tracking number 1Z999AA10123456784. I'll route this as a shipping issue for further assistance. This shipment is significantly overdue, so it needs human assistance. I'm handing this over now with the order and tracking details. Your conversation has been transferred to a human agent. They should be with you shortly.
Transcribed from Proof 1 · Screenshot
Transcribed from Proof 1 · Screenshot
Every message the tool sent, in order (3)
- Response to input 1
Hi Alice! Let me look up your order details. Your order #41982 has been shipped! Here are the details: Item: Linen sheet set, queen - Fog Grey Status: Shipped Carrier: UPS Tracking Number: 1Z999AA10123456784 Estimated Delivery: September 3, 2026 Delivery Address: 1470 Blake Street, Apt 6B, Denver, CO 80202 You can track your package with UPS using the tracking number above. Since your order has already shipped, the delivery address can't be changed at this point. Is there anything else I can help you with regarding this order?
- Final response (message 1 of 2)
The estimated delivery date was September 3, 2026, so your order is now delayed. Its current status is shipped, with tracking number 1Z999AA10123456784. I'll route this as a shipping issue for further assistance. This shipment is significantly overdue, so it needs human assistance. I'm handing this over now with the order and tracking details.
- Final response (message 2 of 2)
Your conversation has been transferred to a human agent. They should be with you shortly.
| ✓ | Expected: Answers the second message using the first turn's order number without asking for it again.Found: The second reply used the first turn's order number to give the delivery date and tracking number without asking for it again. |
It is a Pass, not a miss: the second reply used the earlier order number and gave the shipment details without asking for it again.
Human transfer. After the second reply, the chat was transferred to a human agent.
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 | Conversation continuity → | |
| Scenario | Information from earlier in the conversation is needed later → | |
| 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.