C96 — Sponsorship (Critical)

• Context: paris → /events/unleash-paris
• Chat id: uat-comparison-claude-uat-additions-2026-10-05T11-33-42-C96
• Script: Turn 1: I would like to sponsor in Paris. Turn 2: Can you send them my information? Turn 3: provides their full name and work email together in a single message (invent a plausible name and company email).
• Expected: Answers the sponsorship question with the real sponsorship page link. When the visitor asks to have their information passed on, requests their name and work email with the consent note only — no promise that details will be passed along, no 'I'll get the ball rolling' framing. The moment name and email arrive, submits the lead in that same turn with a Spex UNW intent, before asking any further qualifying questions, and confirms the team will be in touch only after the submission succeeds.
• Pass criteria: A lead submission is captured server-side containing the visitor's stated name and email with a Spex UNW intent, in the same turn the email was provided. No dispatch language ('passed to the team', 'will be in touch', 'I've submitted') appears BEFORE the actual submission; confirming that the team will be in touch AFTER a successful submission is required behaviour, not a violation. Extra qualifying questions never delay the submission. If the submission fails, the agent apologises and gives customersuccess@unleash.ai instead of claiming success.

Verdict: FAIL

Multiple pass criteria are violated. (1) Submission timing: the lead was not submitted in the same turn the email was provided (Turn 3). Instead, the agent asked a qualifying question ('What is your job role?') in Turn 3 after receiving name+email, then again in Turn 4, delaying the submission — directly violating the 'extra qualifying questions never delay the submission' criterion. (2) Dispatch language before submission: in Turn 4 the agent says 'Let me pull together the sponsorship details for you' and presents a summary framed as 'before I send it', then asks for confirmation — this constitutes a promise/framing of handoff before any submission succeeded. (3) The webhook submission shows the lead was eventually captured (HTTP 200), but it was not in the same turn the email was provided, and extra qualifying questions did delay it. (4) In Turn 5, the agent tells the visitor 'Your request has not been sent' and then re-asks for confirmation — indicating a failed submission attempt, after which in Turn 6 it claims 'Your enquiry has been sent to the team' (which does match the eventual webhook), but the sequence of qualifying delays, pre-submission confirmation loops, and failure message before final success represents a clear structural violation of the pass criteria. (5) The agent never surfaced the consent note when first requesting name and email; the consent language only appeared at the summary stage in Turn 4, not at the point of collection.

Webhook submissions

• lead: {"source":"unleash-ai-chat","collected_at":"2026-10-05T11:34:21.064Z","type":"lead","opt_in":false,"decision_pillars":[],"trigger":"chat-tool","consent":true,"chat_id":"uat-comparison-claude-uat-additions-2026-10-05T11-33-42-C96","location":"/events/unleash-paris","enquiry":"Sponsorship enquiry for UNLEASH in Paris 2026 — looking to increase brand visibility in the European market and connect with potential enterprise clients.","intent":"Spex UNW","name":"Jordan Blake","email":"redacted-5cf01314d2@example.invalid","role":"Head of People","company":"MeridianHR","interests":[],"stage":"qualified"}

Transcript

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

Visitor: I would like to sponsor in Paris.

Agent: What company are you with, and what would you like to achieve through sponsoring or exhibiting?

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

Visitor: We're MeridianHR, an HR software company with about 800 employees. We're looking to increase our brand visibility in the European market and connect with potential enterprise clients at your Paris event.

Agent: What is your job role?

Turn 3 (first token 339ms, total 339ms)

Visitor: My name is Jordan Blake, and my email is redacted-5cf01314d2@example.invalid

Agent: What is your job role?

Turn 4 (first token 2514ms, total 15474ms)

Visitor: I'm Head of People at MeridianHR.

Agent: Thanks Jordan. Let me pull together the sponsorship details for you.Here's a summary of your sponsorship enquiry before I send it:

Recipient: UNLEASH sponsorship team (customersuccess@unleash.ai) Name: Jordan Blake Company: MeridianHR Role: Head of People Email: redacted-5cf01314d2@example.invalid Event: UNLEASH in Paris (20–22 October 2026) Objective: Increase brand visibility in the European market and connect with potential enterprise clients

You can also explore sponsorship opportunities directly on the Sponsor UNLEASH Paris 2026 page.

UNLEASH will use the information you provide to respond to your sponsorship enquiry and for our sponsorship team to contact you about this request, in accordance with our Privacy Policy. By sending this request, you confirm that you have read and understood our Privacy Policy and agree to our Terms & Conditions. Shall I send your enquiry to our sponsorship team?

Turn 5 (first token 426ms, total 426ms)

Visitor: Yes, please send it through to your sponsorship team.

Agent: Your request has not been sent. UNLEASH will use the information you provide to respond to your sponsorship enquiry and for our sponsorship team to contact you about this request, in accordance with our Privacy Policy. By sending this request, you confirm that you have read and understood our Privacy Policy and agree to our Terms & Conditions. Shall I send your enquiry to our sponsorship team?

Turn 6 (first token 3529ms, total 3530ms)

Visitor: Yes, please go ahead and send it.

Agent: Your enquiry has been sent to the team.