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

Can Tidio Lyro handle multiple requests in one message?

Tidio Lyro handled the one tested multi-request message successfully. It answered the order status and return policy in one reply, and the order details matched the live order data while the policy block covered the requested rules.

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.

Order status plus return policy in one messagePassEvidence
What we sent

Input 1: “Where is my order 41982, and what is your return policy?”

Input 2 · Confirmation: “yes”

What the tool returned

Confirmation question

Okay, just to confirm the details you've provided: * Order number: 41982 Shall I proceed?

Reply, first part: order status

Here's the info for your order (ORD-2026-0287):

  • Status: Shipped
  • Carrier: UPS
  • Tracking Number: 1Z999AA10123456784
  • Estimated Delivery: October 22, 2026
  • Delivery Address: 1470 Blake Street, Apt 6B, Denver, CO 80202
  • Items: Linen sheet set, queen - Fog Grey
  • Total: $164.00
Show the reply as returned (Markdown)
Here's the info for your order (ORD-2026-0287):
* Status: Shipped
* Carrier: UPS
* Tracking Number: 1Z999AA10123456784
* Estimated Delivery: October 22, 2026
* Delivery Address: 1470 Blake Street, Apt 6B, Denver, CO 80202
* Items: Linen sheet set, queen - Fog Grey
* Total: $164.00

Same reply, continued: return policy

Return Policy:

  • Standard return window: 21 days from delivery date
  • Cedarline Plus members: Extended 45-day return window
  • Items must be returned in resalable condition with original packaging where possible
  • A 15% restocking fee applies to opened bedding and rugs
  • Non-returnable items: Custom/made-to-order furniture, "Final Sale" items, and gift cards
  • For damaged, defective, or wrong items, report within 7 days of delivery with photos - no restocking fee applies
Show the reply as returned (Markdown)
Return Policy:
* Standard return window: 21 days from delivery date
* Cedarline Plus members: Extended 45-day return window
* Items must be returned in resalable condition with original packaging where possible
* A 15% restocking fee applies to opened bedding and rugs
* Non-returnable items: Custom/made-to-order furniture, "Final Sale" items, and gift cards
* For damaged, defective, or wrong items, report within 7 days of delivery with photos - no restocking fee applies

Transcribed from Proof 1 · Screen recording at 0:09

Transcribed from Proof 1 · Screen recording at 0:15

Every message the tool sent, in order (3)
  1. Confirmation question

    Printed above.

  2. Reply, first part: order status

    The final response, printed above.

  3. Same reply, continued: return policy

    The final response, printed above.

Expected vs. Found
✓Expected: Answers both: the live order status and the stated return policyFound: One reply gave the shipped order status and the return-policy details; neither request was omitted.
Supporting proof
Proof 1Screen recording
Screen recording: two-request reply and order check
Key moments
Open original ↗
Why this result

The customer’s one message asked for order status and return policy. The reply answered both, and the order part matched the live order data while the policy part covered the requested rules; the extra confirmation did not drop either request.

Tested by Ajay Vekhande · evidence dated 22 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
Tidio Lyro
Build or version
Not exposed by the hosted product
Plan or tier
Free Plan
Surface
Web app
Set up before the run
A shipped order record and a return-policy help article had to be available.
Tested
22 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/tidio/one-message-contains-multiple-requests · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-22

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 recordingbfa9b09bd83aecce584f48ffcf8bf7387ddc01313fd35f14c90d8ee13828e826