Does Basedash offer follow-up questions after an answer?
Basedash did not offer a follow-up question after answering in web chat. It answered the revenue question but left the space below the answer empty, even after eight minutes.
1 of 1 test case failed
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.
Suggested next questions after an answerFailEvidence
“As of September 2, 2026, what was our total revenue last month?”
Your total order revenue for August 2026 was $8,847.45 USD, as of September 2, 2026. This sums the recorded order totals for 22 non-cancelled orders placed August 1–31, excluding $4,436.62 in cancelled orders. No completed refunds were recorded for the included orders by that date. Dates use your Asia/Calcutta timezone. This is order revenue; it does not include membership or subscription billing.
Transcribed from Proof 1 · Screen recording at 0:08
| ✗ | Expected: At least one suggested question that follows from the analysis and can be answered from the database.Found: Basedash gave August 2026 revenue as $8,847.45 but offered no follow-up questions. The chat still had no suggestions eight minutes later. |
Basedash answered the database question correctly, so there was an opportunity to suggest what to ask next. It offered no question after the answer, rather than a relevant question answerable from the database. This is a product failure in web chat, not an interrupted test.
Revenue answer's qualifications. The August revenue answer defined revenue using non-cancelled orders, identified excluded cancelled orders and the timezone, and distinguished order revenue from subscription billing.
New-chat starters. The empty new-chat screen offered four fixed starters, covering support contacts, restocking, return trends and connecting Slack.
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 Database Agents → | 28 scenarios · 11 tools |
| Capability | Conversational Interaction → | |
| Scenario | The agent offers what to ask next → | |
| Tool | Basedash → |
Global scenario definition → · Global capability definition → · Basedash 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.