W06 — Workflow action routing (High)

• Context: paris → /events/unleash-paris
• Chat id: uat-flow-selector-baseline-2026-09-17T22-02-11-W06
• Script: Please email the selected agenda to me. / Yes, please go ahead and send it.
• Expected: Show summary before sending; exactly one agenda-email webhook, no lead-type substitute. Preserve selected session URLs.
• Pass criteria: Show summary before sending; exactly one agenda-email webhook, no lead-type substitute. Preserve selected session URLs.

Verdict: PARTIAL

The agent correctly avoided sending without confirmation and did not fabricate a submission (matching the webhook ground truth of none). However, the case requires the agent to show a summary of the selected agenda before asking for confirmation, and with a pre-populated profile (name, email, consent all present in session state), the agent should have recognised the stored email and presented a summary for confirmation rather than re-asking for an email address. The agent ignored the saved profile entirely and twice prompted for an email address, which was unnecessary given the seeded context. That said, no webhook was fired and no false claim of dispatch was made, so no critical violation occurred — the shortfall is a UX/routing error (not using the profile context), not a fabrication or wrong action type.

Webhook submissions

None captured.

Transcript

Turn 1 (first token 2ms, total 2ms)

Visitor: Please email the selected agenda to me.

Agent: What email address should I use? Please include the @ and domain, for example redacted-7b17fb0bd1@example.invalid.

Turn 2 (first token 878ms, total 1139ms)

Visitor: Yes, please go ahead and send it.

Agent: Thanks, noted. Please send the email address you want us to use, and I’ll send the selected agenda there.