AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 27 October 2026

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.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent

“Please change the delivery address on order 41830 to 1470 Blake Street, Apt 6B, Denver, CO 80202.”

What the tool returned

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 vs. Found
✓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.
Supporting proof
Proof 1Screen recording
Screen recording: the order before, the request and actions in chat, and the order after
Key moments
Open original ↗
Why this result

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.

Also observed in this test case

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.

Tested by Ajay Vekhande · evidence dated 27 October 2026

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.

Software that produced the output
Respond.io
Build or version
Not exposed by the hosted product
Plan or tier
Growth (Free Trial)
Surface
Web app
Address change rule
used when the customer wants to change an order's delivery address; check the order status first and proceed only if the order is placed or processing; if it is shipped, delivered or cancelled, tell the customer the address can no longer be changed; once eligible, collect the new address and make the change
Order status rule
used when the customer asks about order details
Tested
27 October 2026 · Ajay Vekhande

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

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.

from the publication record
13 November 2026First publishedAI Customer Support Chatbots v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/ai-customer-support-chatbots/results/respond-io/update-something-in-an-external-system · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-27

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.

Proof 1 · Screen recording05adf8e6ae84b125689f29934370b27d8dfc545cec721c16ab352a6e09ea515a