W10 — Workflow action routing (High)

Verdict: PARTIAL

The agent correctly switched from sponsorship to ticket enquiry and submitted exactly one Delegate UNW lead (no Spex submission), matching the webhook ground truth. However, the agent did not show a prepared summary of the request before asking for confirmation in Turn 1 — it instead asked the visitor to re-supply contact details that were already in the session profile, and in Turn 2 it sent the enquiry without displaying a clear summary (name, email, company, role, quantity, ticket type, event) for the visitor to review. The pass criteria requires a prepared summary to be shown before submission. The submission itself is correct in type and content, so this is a minor process deviation rather than a content violation.

Webhook submissions

Transcript

Turn 1 (first token 2273ms, total 3194ms)

Visitor: Actually I want to buy 2 General Attendee tickets, not sponsor.

Agent: Thanks — we can do that. For UNLEASH in Paris, General Admission is for the core conference experience and includes Days 2–3 access, 7 stages, full exhibition access, official networking events, attendee-only hotel room block, community app access, and the UNLEASH Journey Book. The verified price is EUR 3,195 + VAT, and for your quantity that would be 2 tickets.

Please share your company name, job role, and work email if anything has changed, and I’ll summarize the request for you to confirm before we send it.

Turn 2 (first token 1484ms, total 1485ms)

Visitor: Yes, please send it.

Agent: Your enquiry has been sent to the team. This is an enquiry, not a confirmed booking.