Can Intercom Fin accept feedback on a wrong answer?
Intercom Fin lets a customer submit feedback on a wrong answer. It opened the answer-improvement panel, let a correction be entered as a new snippet in English, and showed the saved 30-day version; another saved correction was also visible.
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.
Submit a correction for one wrong answerPassEvidence
“Create a new Snippet | Question: 'What is your return window or return policy timeframe?' | Language: English | Answer: 'Our standard return window is 30 days from the delivery date.'”
The tool's response has no text to quote: it is what the evidence under Proof shows.
Proof 1 · Screen recording · ▶ 0:51–0:52
| ✓ | Expected: The product lets the customer submit a correction.Found: It opened the improvement panel, let the correction be entered, and showed the saved 30-day snippet. |
It is a pass because the customer could submit the correction and the product saved the revised snippet with the new 30-day wording.
Another saved correction. A second snippet was already listed with the revised 30-day wording, so the session showed more than one saved correction.
The recording shows the correction being saved, but not whether a later answer changed.
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 · 13 tools |
| Capability | Feedback and learning → | |
| Scenario | Feedback can be submitted → | |
| 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.