Partially 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.

◐ Mixedinput onlyTest date not recordedKommunicate
What was measured
response completeness

Addresses all parts of the user’s support request instead of leaving key questions unanswered.

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.
Provenance
Observation
0f349e03-d0ec-4fe2-8046-1e56b05b32fa
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 — 6 other tools
measured on response completeness
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com