R26 — Workflow & conversation bugs (High)

Verdict: PASS

The agent engaged with the sponsorship enquiry immediately and asked qualifying questions (company, role, name, email) — exactly the expected behaviour. It did not refuse to engage or give no response. The conversation ended with the visitor saying 'that's all' and the agent providing a fallback resource, which is appropriate. No lead was submitted (matching the server-side ground truth of none), and no false claim of submission was made. The pass criteria (no refusal, qualifying questions present) are satisfied.

Webhook submissions

None captured.

Transcript

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

Visitor: I am interested in sponsoring

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

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

Visitor: I'm with MeridianHR, we're a people operations platform. We'd like to explore sponsorship opportunities to increase brand visibility with HR leaders and talent teams.

Agent: What is your job role?

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

Visitor: Thanks for your interest! I'm the Head of People at MeridianHR. That's all the information I need to share right now—I'd like to learn more about your sponsorship packages and next steps.

Agent: What name should I use?

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

Visitor: Jordan Blake

Agent: What work email address should I use?

Turn 5 (first token 2722ms, total 3087ms)

Visitor: redacted-5cf01314d2@example.invalid

Agent: I couldn’t verify a specific sponsorship package from our live sponsorship and exhibitor information right now.

For sponsorship, exhibiting, or partnership enquiries, the enquiry form on the event’s sponsorship page reaches the sales team directly. Would you like our sales team to get in touch?

Turn 6 (first token 1068ms, total 1402ms)

Visitor: Thanks, that's all.

Agent: We haven’t published that yet. See Sponsorship for what is live, or email support@unleash.ai if you’d like a person to help.