Tool in benchmark · Version 1

Respond.io in AI Customer Support Chatbots

Scenario-level performance from current published Results.

16Passed
0Failed
3Different test set
7No published Result yet

19 of 26 scenarios published

CapabilityScenariosResult
Action execution3 pass · 0 fail · 4 of 5 published
Agent configuration and control2 pass · 0 fail · 2 of 2 published
Conversation continuity2 pass · 0 fail · 2 of 3 published
Escalation and human handoff3 pass · 0 fail · 3 of 3 published
Intent understanding3 pass · 0 fail · 3 of 3 published
Knowledge-grounded answering1 pass · 0 fail · 3 of 3 published
Multilingual support2 pass · 0 fail · 2 of 2 published
Feedback and learning0 of 2 published
PassedFailedPublished, different test setNo published Result yet

Respond.io passed every graded scenario it has a published Result for.

How Respond.io performed

Open a capability to explore its scenarios. Each row reports the test set in its published Result.

Action execution3 pass1 different test set1 no Result yet
ScenarioPublished outcomesTest coverageResult
Action requires confirmation
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io asked the customer to confirm before it cancelled a subscription. Asked to cancel, it only looked the subscription up, named the plan and its monthly price, said the cancellation takes effect at the end of the billing cycle with no partial refund, and asked whether to proceed. It cancelled only after the customer said yes.

1/1 assessed1/1 gradablePublished test setView Result →
Retrieve information from an external system
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io retrieved the order’s status and correctly reported that it had shipped. The order-status action ran, and the connected order system also listed shipped.

1/1 assessed1/1 gradablePublished test setView Result →
Update something in an external systemDifferent test setPublished Result available, but not included in this comparison.View Result →
User is not authorized to perform the action
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io declined to look up another customer's order and revealed none of its details. The agent invoked its order-status action before giving the refusal.

1/1 assessed1/1 gradablePublished test setView Result →
Requested action cannot be completedNo published result
Agent configuration and control2 pass
ScenarioPublished outcomesTest coverageResult
Configured instruction changes agent behavior
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io followed the requested behavior by offering store credit before any cash refund. It asked when the cushions were delivered and whether the customer wanted store credit.

1/1 assessed1/1 gradablePublished test setView Result →
Configured restriction is respected
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io respected the restriction on subscription cancellation. It declined to act in chat and directed the customer to the account dashboard or support.

1/1 assessed1/1 gradablePublished test setView Result →
Conversation continuity2 pass1 no Result yet
ScenarioPublished outcomesTest coverageResult
Customer corrects information given earlier
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io handled the correction and kept the answer on the updated order. After the customer changed the number, the reply covered only 41830: it said the order was processing, gave an arrival date of November 2, 2026, and said there was no tracking number yet.

1/1 assessed1/1 gradablePublished test setView Result →
Information from earlier in the conversation is needed later
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io passed this conversation-continuity scenario. The second customer message was answered with the earlier order number, and the reply gave a delivery date, carrier, and tracking number without asking for the number again.

1/1 assessed1/1 gradablePublished test setView Result →
Earlier conversation/session needs to be continuedNo published result
Escalation and human handoff3 pass
ScenarioPublished outcomesTest coverageResult
A configured rule requires escalation
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io routed the refund request to a human and issued no refund. A human agent then replied in the same conversation.

1/1 assessed1/1 gradablePublished test setView Result →
Agent cannot resolve the request
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io passed this scenario: when the agent could not handle the account-name change, it handed the customer to a human. The capture shows the bot’s inability statement, the handover note, the reassignment, and the human reply in the same conversation.

1/1 assessed1/1 gradablePublished test setView Result →
User explicitly asks for a human
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io handed the chat to a human when the customer explicitly asked. The agent agreed without asking for a reason or trying to answer instead.

1/1 assessed1/1 gradablePublished test setView Result →
Intent understanding3 pass
ScenarioPublished outcomesTest coverageResult
One message contains multiple requests
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io answered both requests in the one message. It looked up the order and gave its live status, shipped with UPS and arriving October 27, 2026, then in the same reply stated the return policy: 45 days from delivery for Cedarline Plus members, items in resalable condition, and a 15% restocking fee on opened bedding.

1/1 assessed1/1 gradablePublished test setView Result →
Request is unclear and needs clarification
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

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/1 assessed1/1 gradablePublished test setView Result →
Request requires choosing the correct source or action
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io chose the order system rather than the knowledge base for an order-status request. Its answer included shipment status, tracking details and an estimated delivery date.

1/1 assessed1/1 gradablePublished test setView Result →
Knowledge-grounded answering1 pass2 different test set
ScenarioPublished outcomesTest coverageResult
Answer is available in the knowledge baseDifferent test setPublished Result available, but not included in this comparison.View Result →
Answer is not available in the knowledge baseDifferent test setPublished Result available, but not included in this comparison.View Result →
The request uses different wording than the source
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io answered the reworded return question with the required 15% refund deduction, ruling out a full refund. The customer asked about an opened rug without using the knowledge base’s term “restocking fee”.

1/1 assessed1/1 gradablePublished test setView Result →
Multilingual support2 pass
ScenarioPublished outcomesTest coverageResult
Customer communicates in another supported language
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io handled the French question in French and returned the return-policy details from the knowledge base. The reply matched the expected article facts and added nothing extra.

1/1 assessed1/1 gradablePublished test setView Result →
Customer switches languages during the conversation
1 Pass0 Fail0 Not gradable
1 of 1 test case passed
What happened

Respond.io continued in English without losing the return-policy context after the customer changed languages. It kept the 45-day Plus return window from delivery and explained that orders placed during active membership still qualify if they arrive after cancellation.

1/1 assessed1/1 gradablePublished test setView Result →
Analytics and observability3 no Result yet
ScenarioPublished outcomesTest coverageResult
Agent actions/tool calls can be inspectedNo published result
Conversation activity can be inspectedNo published result
Reported analytics match what actually happenedNo published result
Feedback and learning2 no Result yet
ScenarioPublished outcomesTest coverageResult
Correction changes future behavior where the product claims learningNo published result
Feedback can be submittedNo published result

Reading these Results

Published evidence and test coverage answer different questions.

Publication availability

Which scenarios have a Result?

A published Result is public evidence for this tool on one scenario. “No published result” does not say whether testing has taken place.

Test coverage

What does each Result cover?

Assessed includes Pass, Fail and Not gradable. Gradable includes Pass and Fail. Both use the pinned test count in that published Result.

Scenario scope

Out of 26 scenarios

The summary counts each of the 26 scenarios once. A scenario fails when any of its published test cases failed. “No published Result yet” means nothing is public for that scenario; it does not say whether Respond.io was tested on it.

Respond.io in AI Customer Support Chatbots | AI Demos