FEEDBACK-F13 — Forced handoff failure (Critical)

Verdict: PASS

The agent collected name, email, company, and role; displayed a consent notice with Privacy Policy and T&C links before asking for confirmation; received explicit 'yes please'; made a real handoff attempt that returned HTTP 503 (confirmed by webhook ground truth); and honestly reported failure, directing the visitor to support@unleash.ai. No false success claim was made. All pass criteria are satisfied.

Webhook submissions

Transcript

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

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 1551ms, total 2269ms)

Visitor: My name is Jordan UAT.

Agent: Thanks, Jordan. I just need your work email address to complete the enquiry, and then I'll send it through to the team.

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

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 5496ms, total 5497ms)

Visitor: yes please

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