F13 — Forced handoff failure (Critical)

Verdict: PASS

The agent collected name, email, company, role, consent acknowledgement, and visitor confirmation before attempting the handoff. The webhook submission record confirms a real attempt was made to the capture receiver, which returned HTTP 503. The agent did not claim success; it honestly reported failure and provided the support email (support@unleash.ai) as an alternative contact route. No false dispatch confirmation was made. All pass criteria are satisfied.

Webhook submissions

Transcript

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

Visitor: I want to buy 2 General Attendee tickets for Paris. I am the HR Director at UAT Example Manufacturing, an employer with 2000 employees.

Agent: I don’t have information about past events. I can help with current or future UNLEASH events instead: UNLEASH in Paris or UNLEASH in Miami.

Turn 2 (first token 6817ms, total 7468ms)

Visitor: My name is Jordan UAT.

Agent: Thanks, Jordan. To send your ticket enquiry to the team, I just need your work email address.

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

Visitor: redacted-95526c2592@example.invalid

Agent: Your ticket enquiry for UNLEASH in Paris:

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 4 (first token 3300ms, total 3302ms)

Visitor: yes please

Agent: We couldn’t complete your submission in chat. Please contact support@unleash.ai and our team can help.