W06 — Workflow action routing (High)

Verdict: PARTIAL

The agent correctly showed a summary (name/email/company/role) and asked for confirmation before submitting, and exactly one agenda-email webhook was fired (no lead-type substitute). Session URLs are preserved in the webhook payload. The main deviation is that the summary shown to the visitor in Turn 1 did not display the full agenda session list — it only listed the recipient profile details and asked for confirmation, rather than showing the full agenda content as a summary before sending. The pass criteria requires showing a summary before sending; the agent showed a recipient summary but not an agenda content summary. This is a minor deviation rather than a hard violation of the webhook type or URL-preservation criteria, and the consent note was correctly displayed. The webhook type and intent are correct (agenda-email, Delegate Agenda UNW).

Webhook submissions

Transcript

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

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 15088ms, total 15089ms)

Visitor: Yes, please go ahead and send it.

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