C109 — Sponsorship (High)

Verdict: PARTIAL

The agent correctly declined to invent per-sqm pricing and offered team contact before requesting personal details — the core hierarchy is respected. Consent language was shown before submission (Turn 6), and a valid lead was submitted server-side (HTTP 200). However, two issues prevent a full pass: (1) In Turn 1, the agent's closing line 'I'll just need a few details from you' begins to imply imminent data collection before the visitor has accepted, which partially conflates the 'offer team contact' and 'collect details' steps — though it stops short of actually requesting details before consent, making it a minor deviation rather than a hard violation. (2) In Turn 7, after the visitor confirmed, the agent falsely stated 'Your request has not been sent' and re-presented the consent block and confirmation prompt, creating confusion and an unnecessary extra loop. The submission was ultimately made and accepted (HTTP 200), so no fabricated success claim exists, but the Turn 7 failure message was erroneous agent behaviour.

Webhook submissions

Transcript

Turn 1 (first token 7624ms, total 8736ms)

Visitor: What does exhibition space cost per square meter at UNLEASH Paris?

Agent: We haven't published exhibition space pricing — it's handled directly by our sales team, who can put together the right package based on your requirements.

Would you like our sales team to get in touch? If so, I'll just need a few details from you.

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

Visitor: Yes, that would be great. Please have them reach out.

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

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

Visitor: I'm with Meridian HR, we're a people operations platform with about 800 employees. We're looking to exhibit to connect with HR leaders and showcase our latest talent management solutions.

Agent: What is your job role?

Turn 4 (first token 598ms, total 598ms)

Visitor: Head of People at Meridian HR.

Agent: What name should I use?

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

Visitor: Jordan Blake.

Agent: What work email address should I use?

Turn 6 (first token 2251ms, total 6447ms)

Visitor: redacted-1da77b2aba@example.invalid

Agent: Here's a summary of the enquiry I'll send to our sponsorship team:

Recipient: UNLEASH sponsorship team (customersuccess@unleash.ai) Name: Jordan Blake Email: redacted-1da77b2aba@example.invalid Company: Meridian HR Role: Head of People Event: UNLEASH in Paris Objective: Exhibiting to connect with HR leaders and showcase their talent management solutions. ~800 employees, people operations platform.

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 7 (first token 334ms, total 334ms)

Visitor: Yes, please send it through!

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 8 (first token 3393ms, total 3394ms)

Visitor: Yes, please go ahead and send it.

Agent: Your enquiry has been sent to the team.