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

Does Respond.io ask what the customer means when a request is unclear?

Respond.io did not act on an unclear request to cancel. It asked what the customer wanted to cancel, offering an order, the Cedarline Plus membership or a monthly product subscription, and no cancellation action ran.

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.

'I want to cancel.' with two cancellablesPassEvidence
What we sent

“I want to cancel.”

What the tool returned

What would you like to cancel: an order, Cedarline Plus membership, or a monthly product subscription? Membership and subscription cancellations take effect at the end of the billing cycle; order cancellation depends on its status.

Transcribed from Proof 1 · Screenshot

Expected vs. Found
✓Expected: Asks the customer which item they mean before taking any action.Found: It replied with a question asking whether to cancel an order, the Cedarline Plus membership or a monthly product subscription. No cancellation action appears in the conversation.
Supporting proof
Proof 1Screenshot
Screenshot: the request to cancel and the agent's clarifying question, with no cancellation action
Open original ↗
Why this result

It is a Pass because the request could mean more than one thing and the agent asked which one before acting. Its reply was a direct question naming the membership and the subscription, and no cancellation action ran.

Tested by Ajay Vekhande · evidence dated 26 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
Set up before the run
The customer's account had to hold two different things that could be cancelled, here a Cedarline Plus membership and a monthly product subscription, so that a plain request to cancel could mean either.
Tested
26 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
16 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/ambiguous-request · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-26

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.

Proof 1 · Screenshot ↗image/png · 21 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshota9b1f35265acf95590ebfd279672b3cfd9d041b81778cfe13cfdd6618507e5a2