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.
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.”
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: 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. |
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.
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 | Intercom Fin → |
Global scenario definition → · Global capability definition → · Intercom Fin 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.