Respond.io in AI Customer Support Chatbots
Scenario-level performance from current published Results.
6 of 26 scenarios published
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.
Conversation continuity2 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer corrects information given earlier | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Information from earlier in the conversation is needed later | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Earlier conversation/session needs to be continued | No published result | ||
Escalation and human handoff2 pass1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Agent cannot resolve the request | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| User explicitly asks for a human | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| A configured rule requires escalation | No published result | ||
Intent understanding1 pass2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Request requires choosing the correct source or action | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| One message contains multiple requests | No published result | ||
| Request is unclear and needs clarification | No published result | ||
Knowledge-grounded answering1 different test set2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Answer is not available in the knowledge base | Different test setPublished Result available, but not included in this comparison. | View Result → | |
| Answer is available in the knowledge base | No published result | ||
| The request uses different wording than the source | No published result | ||
Action execution5 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Action requires confirmation | No published result | ||
| Requested action cannot be completed | No published result | ||
| Retrieve information from an external system | No published result | ||
| Update something in an external system | No published result | ||
| User is not authorized to perform the action | No published result | ||
Agent configuration and control2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Configured instruction changes agent behavior | No published result | ||
| Configured restriction is respected | No published result | ||
Analytics and observability3 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Agent actions/tool calls can be inspected | No published result | ||
| Conversation activity can be inspected | No published result | ||
| Reported analytics match what actually happened | No published result | ||
Feedback and learning2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Correction changes future behavior where the product claims learning | No published result | ||
| Feedback can be submitted | No published result | ||
Multilingual support2 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer communicates in another supported language | No published result | ||
| Customer switches languages during the conversation | No published result | ||
Reading these Results
Published evidence and test coverage answer different questions.
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.
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.
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.