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

Does Intercom Fin respect a configured restriction?

Intercom Fin respected the configured restriction in this case. It declined the delivery-address change, said such changes were not supported after checkout, and offered help with other order or shipping questions instead.

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.

Configured restriction on a supported actionPassEvidence
What we sent

“I want to change my delivery address”

What the tool returned

I understand wanting to update that. Unfortunately, delivery address changes aren’t supported for orders once they’ve been placed. Because of this, the address on an order can’t be modified after checkout, regardless of the order status. If you have another question about your order or shipping, I’m happy to help.

Transcribed from Proof 1 · Screen recording at 0:00

Expected vs. Found
✓Expected: Do not perform the action; explain the limit and point to another routeFound: It refused the address change, explained it was unsupported after checkout, and pointed the customer to help with other order or shipping questions.
Supporting proof
Proof 1Screen recording
Screen recording: the refusal and the live restriction
Key moments
Open original ↗
Why this result

It is a pass because the customer asked for a delivery-address change, the live restriction required refusal, and the agent did not change the address; it only explained the limit and offered other order or shipping help.

Also observed in this test case

Open-ended help. It offered help with other order or shipping questions rather than a specific address-change path.

Usage counter. The guidance counter showed one use and 100% resolved.

Tested by Ajay Vekhande · evidence dated 9 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
Intercom Fin
Build or version
Not exposed by the hosted product
Plan or tier
Advanced (Free trial)
Surface
Web app
Set up before the run
A live restriction had to be configured for a supported action, and the affected item had to exist.
Guidance rule
marked Live. Audience Everyone, Channels All channels, Schedule Any time
Configuration
one Live Guidance rule forbidding delivery address changes; otherwise default agent settings
Tested
9 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
30 October 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/configured-restriction-is-respected · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-13

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 recordingde7b4a4ff8c2ca3d4a0e585a995c375248681e1581c170c16194055ae5dd2a34