REGRESSION-R06 — Refusal template & source attribution (High)
- Context:
paris→/events/unleash-paris - Chat id:
uat-flow-selector-2026-09-17T22-05-22-REGRESSION-R06 - Script: Turn 1: Where do I find the floorplan? Turn 2: say thanks, that's all.
- Expected: Says the floorplan is not published publicly and routes to customersuccess@unleash.ai.
- Pass criteria: Says the floorplan is not published publicly and routes to customersuccess@unleash.ai. Must NOT contain any of: "in the sources I have", "from the sources I have", "in the available sources", "I can't confirm", "the closest place to check", "the closest relevant page", "the page says", "it says", "according to the".
Verdict: FAIL
The agent did not say the floorplan is not published publicly and did not route the visitor to customersuccess@unleash.ai. Instead it directed the visitor to an interactive map and a plan-your-visit page, implying floorplan content is available, which contradicts the expected behaviour. Additionally, the Turn 2 response was nonsensical/inappropriate for the visitor's farewell message.
Webhook submissions
None captured.
Transcript
Turn 1 (first token 2152ms, total 2769ms)
Visitor: Where do I find the floorplan?
Agent: We’ve published the interactive map on Map, and the trip-planning page also includes venue and practical details on Plan Your Visit. If you want, I can also point you to the agenda or badge page.
Turn 2 (first token 1ms, total 1ms)
Visitor: Thanks, that's all I needed!
Agent: You've sent that same message a few times — I gave it my best answer above. Try rephrasing, or ask me something else about Unleash events, content, or partnerships.