FEEDBACK-F13 — Forced handoff failure (Critical)

Verdict: PASS

The agent collected name, email, role, company, and quantity; presented a clear consent statement before submission; attempted the handoff (server-side ground truth confirms a lead submission was made and received HTTP 503); honestly reported failure without claiming success; and provided an alternative contact route (customersuccess@unleash.ai). All pass criteria are satisfied.

Webhook submissions

Transcript

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

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: What name should our team use for this enquiry?

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

Visitor: My name is Jordan UAT.

Agent: What work email should our team use to contact you?

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

Visitor: redacted-95526c2592@example.invalid

Agent: Your ticket enquiry for UNLEASH in Paris:

This is an enquiry for the team, not a confirmed booking.

By sharing your details, you agree to UNLEASH contacting you about this enquiry. View our Privacy Policy. Shall I send this request with your consent?

Turn 4 (first token 1319ms, total 1320ms)

Visitor: yes please

Agent: We couldn’t send that request just now. Please email customersuccess@unleash.ai and our team can help.