Respond.io in AI Customer Support Chatbots
Scenario-level performance from current published Results.
19 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.
Action execution3 pass1 different test set1 no Result yet
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Action requires confirmation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Retrieve information from an external system | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Update something in an external system | Different 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 passedWhat happenedRespond.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 set | View Result → |
| Requested action cannot be completed | No published result | ||
Agent configuration and control2 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Configured instruction changes agent behavior | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Configured restriction is respected | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View 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 handoff3 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| A configured rule requires escalation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View 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 → |
Intent understanding3 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| One message contains multiple requests | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Request is unclear and needs clarification | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View 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 → |
Knowledge-grounded answering1 pass2 different test set
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Answer is available in the knowledge base | Different test setPublished Result available, but not included in this comparison. | View Result → | |
| Answer is not available in the knowledge base | Different 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 passedWhat happenedRespond.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 set | View Result → |
Multilingual support2 pass
Capability in this benchmark →
| Scenario | Published outcomes | Test coverage | Result |
|---|---|---|---|
| Customer communicates in another supported language | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View Result → |
| Customer switches languages during the conversation | 1 Pass0 Fail0 Not gradable 1 of 1 test case passedWhat happenedRespond.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 set | View 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 | ||
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.