W03 — Workflow action routing (High)

• Context: paris → /events/unleash-paris
• Chat id: uat-flow-selector-baseline-2026-09-17T22-02-11-W03
• Script: please do / Yes, I consent. Please send the enquiry.
• Expected: Summary then exactly one Spex UNW lead; no repeating contact offer or consent loop.
• Pass criteria: Summary then exactly one Spex UNW lead; no repeating contact offer or consent loop.

Verdict: PARTIAL

The webhook submission is present and correct (exactly one Spex UNW lead, correct event scoping, consent=true, no duplicate submission). However, the pass criteria require a summary of the enquiry before dispatch. In Turn 1 the agent redirected to the sponsorship page rather than preparing a summary of the pending enquiry, and in Turn 2 it confirmed dispatch without showing a summary of what was being sent (contact details, event, enquiry type). The consent was already on file and need not be re-collected, but a summary before confirmation is explicitly required by the pass criteria. The core routing and submission behaviour is correct; only the pre-dispatch summary step is absent.

Webhook submissions

• lead: {"source":"unleash-ai-chat","collected_at":"2026-09-17T22:02:48.817Z","type":"lead","trigger":"chat-tool","consent":true,"chat_id":"uat-flow-selector-baseline-2026-09-17T22-02-11-W03","location":"/events/unleash-paris","enquiry":"sponsorship enquiry for UNLEASH in Paris","intent":"Spex UNW","name":"Jordan UAT","email":"redacted-95526c2592@example.invalid","role":"HR Director","company":"UAT Example","interests":[],"stage":"qualified"}

Transcript

Turn 1 (first token 4680ms, total 5121ms)

Visitor: please do

Agent: For sponsorship, the right page is Sponsor UNLEASH Paris 2026. That page is where the sponsorship enquiry form lives and is the direct route to our sales team.

Would you like our sales team to get in touch?

Turn 2 (first token 8619ms, total 9396ms)

Visitor: Yes, I consent. Please send the enquiry.

Agent: Your enquiry has been sent to the team.