Keeps the refund answer concise and easy to read, presenting the information in a single support-friendly paragraph.
What was measured
conversational quality
Responds in a clear, natural, and support-appropriate way.
transformation
What was given, what came back
Test input: Refund policy, application, and processing-time question · text · group: stylenova-customer-support
Input — what we sent
The exact prompt
What's your refund policy? And if I'm eligible, how do I actually apply for one? Also, how long does it usually take to process?
A multi-part customer-support query asking for the refund policy, how to apply for a refund, and how long processing usually takes. It tests grounded FAQ answering and multi-step policy completeness.
Why this input is hard
- · knowledge-base grounding
- · multi-part query handling
- · policy accuracy
- · response completeness
- · hallucination resistance
Output — unretouched
No output artifact
The verdict rests on the tester's written observation alone — no file was captured for this cell.
Also checked on this input — same tool, 3 other criteria
multi-part query handling✓ WorkedHandles a three-part support question in one coherent reply, covering the refund policy, how to start a return, and the usual processing time in a single response.policy accuracy✓ WorkedStates the core refund policy accurately: returns within 30 days of delivery, items must be unused/unwashed/in original packaging, and refunds are processed 5–7 business days after the returned item is received.response completeness◐ MixedPartially answers a multi-part refund request: it gives the policy and timing, but the application procedure stays vague and the reply omits Elite free returns and the $4.99 non-Elite return-shipping rule that the report says were in the knowledge base.
Provenance
- Observation
- d99fa613-15e5-4ef8-a31b-7d04ea68817d
- Evidence run
- cf8842ae-b5a5-4bf3-a6d9-d61ebe406097
- Study
- Automate customer support using an AI chatbot
- Research task
- 86b9jm3ev
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- observed
- Proof shown
- input only
- 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: "kommunicate",
scenario: "stylenova-customer-support"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 4 other tools
measured on conversational quality
Freshdesk◐ MixedKeeps the answer clearly structured and support-appropriate, but the researcher notes it is somewhat long and text-heavy.JotForm◐ MixedThe response was concise and support-appropriate, but the report notes it stayed as one unformatted paragraph with no headers or bullets, which made it harder to scan.Tidio✓ WorkedResponds in a clear, support-appropriate format with bold section headers and bullet points that are easy to scan.Wonderchat◐ MixedThe response was clearly structured and support-appropriate, but the report says it was slightly over-explained for a simple policy check and could overwhelm a customer who wanted a quick answer.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com