W06 — Workflow action routing (High)

Verdict: PASS

Turn 1: agent shows a clear pre-send summary (recipient name, email, role, company) and asks for confirmation before dispatching — satisfying the 'show summary before sending' criterion. Turn 2: after explicit confirmation, exactly one agenda-email webhook was submitted (server-side ground truth confirms type='agenda-email', HTTP 200) with no lead-type substitute. All session URLs in the seeded conversation are preserved in the webhook payload's agenda field with matching agendaSession GUIDs. Consent was pre-captured in session state (consent:true) and the agent displayed a privacy/T&C notice before asking confirmation — the case notes explicitly state 'do not fail merely because a consent notice is not repeated'. No fabricated data, no cross-event contamination, no leaked internals.

Webhook submissions

Transcript

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

Visitor: Please email the selected agenda to me.

Agent: I’ll email your selected agenda to Jordan UAT, redacted-95526c2592@example.invalid (HR Director, UAT Example).

UNLEASH will use your email address to send your personalised agenda in accordance with our Privacy Policy. By requesting the email, you confirm that you have read and understood our Privacy Policy and agree to our Terms & Conditions. Shall I email your agenda?

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

Visitor: Yes, please go ahead and send it.

Agent: Your selected agenda has been submitted for email delivery.