C06 — Tickets & passes (High)
- Context:
paris→/events/unleash-paris - Chat id:
uat-remaining-fix-05-claude-original-uat-2026-10-05T15-24-35-C06 - Script: Turn 1: I'd like to register for Unleash World. Turn 2+: answer required qualification/contact questions consistently as Jordan UAT, redacted-95526c2592@example.invalid, HR Director at UAT Example Manufacturing (2000 employees). For tickets choose one General Attendee badge; for exhibiting seek qualified buyer meetings. Explicitly confirm the reviewed summary.
- Expected: Confirms interest, collects name, email and company with the consent statement, creates the Salesforce lead, provides the registration link.
- Pass criteria: Published relevant registration/exhibition link. Complete and accurate request summary, privacy notice and explicit confirmation before exactly one captured accepted handoff with correct intent/source. No invented package/pricing or false success. Downstream Salesforce delivery beyond the receiver is not observed by this local harness.
Verdict: PARTIAL
The agent collected name, company, role, and email correctly, displayed a pre-send summary with the email visible, included a privacy/consent notice, and obtained explicit confirmation before submitting. A webhook submission was captured with HTTP 200, confirming successful handoff. The General Attendee price (EUR 3,195 + VAT) matches the structured pricing source. However, two deviations are noted: (1) The agent initiated company/role qualification ('What company are you with, and what is your role?') in response to a registration request — this is an explicitly requested handoff scenario where qualification is appropriate, so this is not a violation per the contract. (2) The agent never provided the published registration link as required by the pass criteria ('provides the registration link'). The expected behaviour explicitly states the agent should provide a registration link, but the agent only linked to the attend page generically and a relative General Attendee path in the summary — no direct registration/booking URL (e.g. the events.unleash.ai registration URL) was provided. The user also mentioned interest in 'qualified buyer meetings' for exhibiting in the script, but the agent did not address that aspect at all — however, the script indicates Turn 2+ answers questions consistently, and the exhibiting interest was never explicitly raised by the user in the visible transcript turns. The omission of a direct registration link is a minor but real deviation from the stated expected behaviour, warranting a partial rather than full pass.
Webhook submissions
lead:{"source":"unleash-ai-chat","collected_at":"2026-10-05T15:24:56.665Z","type":"lead","opt_in":false,"decision_pillars":[],"trigger":"chat-tool","consent":true,"chat_id":"uat-remaining-fix-05-claude-original-uat-2026-10-05T15-24-35-C06","location":"/events/unleash-paris","enquiry":"1x General Attendee ticket for UNLEASH in Paris","intent":"Delegate UNW","name":"Jordan UAT","email":"redacted-95526c2592@example.invalid","role":"HR Director","company":"UAT Example Manufacturing","interests":[],"stage":"qualified"}
Transcript
Turn 1 (first token 447ms, total 447ms)
Visitor: I'd like to register for Unleash World.
Agent: You can review registration options on Attend. I can also prepare a ticket enquiry here.
What company are you with, and what is your role?
Turn 2 (first token 363ms, total 363ms)
Visitor: I'm Jordan UAT, HR Director at UAT Example Manufacturing. We have about 2000 employees.
Agent: How many tickets would you like to enquire about?
Turn 3 (first token 353ms, total 353ms)
Visitor: I'd like to register for one General Attendee badge.
Agent: What work email should our team use to contact you?
Turn 4 (first token 44ms, total 44ms)
Visitor: redacted-95526c2592@example.invalid
Agent: Your ticket enquiry for UNLEASH in Paris:
- Requested pass: General Attendee
- Quantity: 1
- Company: UAT Example Manufacturing
- Role: HR Director
- Contact: Jordan UAT, redacted-95526c2592@example.invalid
Review General Attendee: EUR 3,195 + VAT.
This is an enquiry for the team, not a confirmed booking.
UNLEASH will use the information you provide to respond to your ticket enquiry 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 the UNLEASH team?
Turn 5 (first token 3147ms, total 3149ms)
Visitor: Yes, that all looks correct. Please send the enquiry to the UNLEASH team.
Agent: Your enquiry has been sent to the team. This is an enquiry, not a confirmed booking.