Understands and answers a Hindi escalation request in Hindi, asking for the user's email and issue details so the request can be routed onward.
What was measured
Multilingual Understanding
Correctly understands support requests written in more than one language.
decisive for this rankingtransformation
If the bot cannot understand customer requests in the languages it is expected to serve, it cannot automate support well. (3 of 3 judges)
What was given, what came back
Test input: Customer-support handoff request · text
Input — what we sent
The exact prompt
I received the wrong item in my order. I've already checked the order details and this is clearly a mistake on your end. I don't want any more back and forth — can you please connect me to a customer support agent or raise a ticket for this?
A frustrated support-escalation request after receiving the wrong item, asking to be connected to a support agent or have a ticket raised.
Why this input is hard
- · Human handoff reliability
- · Ticket creation workflow
- · Escalation contextual awareness
- · Professional tone under frustration
Output — unretouched
Also checked on this input — same tool, 3 other criteria
Conversational Quality✓ WorkedHandles a human-handoff request in a clear, support-appropriate way by acknowledging the user and starting ticket intake with an email address and issue description.Conversational Safety Behavior✓ WorkedResponds safely to a fraud claim by de-escalating, apologizing, and collecting the minimum details needed for support ticket creation instead of trying to resolve the charge on the spot.Response Completeness✓ WorkedCompletes a 'no bot' escalation by routing the user to support and requesting the email address and brief issue description needed to proceed.
Provenance
- Observation
- b447c90a-9341-4072-ac5d-04ec43d088d5
- Evidence run
- 2645dc92-49df-478a-b809-21dfd09f06a7
- Study
- Automate customer support using an AI chatbot
- Research task
- 86b9jm3ev
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "fs-agent"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 4 other tools
measured on Multilingual Understanding
Fin✓ WorkedThe bot responds in Hindi and offers either a human-agent connection or continued help, showing it can understand a non-English support request.Freshdesk✓ WorkedThe bot recognizes a Spanish request for customer service, states that it is trained for English, French, and Urdu, and still assigns the chat to support.JotForm✓ WorkedIt correctly understood 2 escalation requests written in Hindi and Spanish, responded in the same language, and asked for an email address for follow-up.Wonderchat✓ WorkedIt understands the Hindi support request and answers fully in Hindi, preserving the support-channel options and response-time details.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com