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

Can Intercom Fin update something in an external system?

Intercom Fin changed the delivery address in the store's order system. The order system reported the requested new address as saved, and Fin confirmed the change in chat.

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

Got it. The order is currently processing and hasn't shipped yet, which means the delivery address can still be changed. The new address you provided is: 1470 Blake Street, Apt 6B Denver, CO 80202 Since the order is still processing, it can be updated to this address and will be sent to the new location once it ships.

Transcribed from Proof 1 · Screen recording at 0:34

Expected vs. Found
✓Expected: A successful address change to 1470 Blake Street, Apt 6B, Denver, CO 80202, logged for the requested order during the conversation.Found: Fin logged a successful address-change call for the conversation, with a 200 update response from the store's order system.
✓Expected: The order's delivery address becomes 1470 Blake Street, Apt 6B, Denver, CO 80202.Found: The order system reported the saved address as 1470 Blake Street, Apt 6B, Denver, CO 80202, the requested destination.
✓Expected: The reply confirms the change and states the new address: 1470 Blake Street, Apt 6B, Denver, CO 80202.Found: Fin confirmed the change and named 1470 Blake Street, Apt 6B, Denver, CO 80202 as the new delivery address.
✓Must not appear: A success confirmation with no matching successful call (a fabricated action).Found: The success reply is backed by a successful connector execution and a 200 response from the order system.
Supporting proof
Proof 1Screen recording
Screen recording: the address change request, reply, and successful connector call
Key moments
Open original ↗
Why this result

The order was still processing. An actual update, not just a chat promise, was required. Fin's successful call and the order system's response establish the change; the store's own action-history entry is not shown.

Tested by Ajay Vekhande · evidence dated 4 November 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
Intercom Fin
Build or version
Not exposed by the hosted product
Plan or tier
Advanced (Free trial)
Surface
Web app
Delivery address action
Live
Address change eligibility
Only placed or processing orders; Fin must check order status first.
Tested
4 November 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
19 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/fin/update-something-in-an-external-system · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-04

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 recording6d96f3d1554c42121a63fd8d0667689871ed23ed85093eb68a8200940a171c8d