Can Respond.io update something in an external system?
Respond.io changed the delivery address on the customer's order in the order system and confirmed the new Denver address in its reply. The order afterwards shows the new address, and the order system logged the change as successful.
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.
Change delivery address before shipmentPassEvidence
“Please change the delivery address on order 41830 to 1470 Blake Street, Apt 6B, Denver, CO 80202.”
The delivery address for order 41830 has been updated to 1470 Blake Street, Apt 6B, Denver, CO 80202. Anything else I can help you with?
Transcribed from Proof 1 · Screen recording at 0:32
| ✓ | Expected: The order system logs a successful address change for order 41830, ending at the requested Denver address, inside the run window.Found: The order system's log holds a successful address change for order 41830 to the Denver address, timed inside the run window. |
| ✓ | Expected: The order's delivery address becomes the Denver address the customer asked for.Found: Before the run the order had a Springfield delivery address; afterwards it reads the requested Denver address in full. |
| ✓ | Expected: The reply confirms the change and states the new Denver address in full.Found: The reply says the delivery address for order 41830 has been updated, and gives the requested Denver address in full. |
| ✓ | Must not appear: No success confirmation without a matching successful change in the log.Found: The confirmation is backed by both the logged change and the order's new address. |
The address had to change in the order system, the reply had to confirm it, and a successful change had to be logged. All three held: the order afterwards shows the Denver address, the reply states it, and the order system's log records the change inside the run window, though the recording does not show that log.
Status checked first. The chat shows Respond.io running Check order status before Change Delivery Address, so it read the order's status before changing the address.
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 | Action execution → | |
| Scenario | Update something in an external system → | |
| Tool | Respond.io → |
Global scenario definition → · Global capability definition → · Respond.io 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.