W03 — Workflow action routing (High)

• Context: paris → /events/unleash-paris
• Chat id: uat-comparison-openai-flow-selector-2026-10-05T11-45-28-W03
• Script: please do / Yes, I consent. Please send the enquiry.
• Expected: Summary then exactly one Spex UNW lead; no repeating contact offer or consent loop.
• Pass criteria: Summary then exactly one Spex UNW lead; no repeating contact offer or consent loop.

Verdict: BLOCKED

The agent correctly prepared a summary with contact details and a consent notice, then attempted to submit after explicit confirmation — the correct workflow. However, the webhook submission failed server-side (no lead submitted), and the agent reported the failure rather than falsely claiming success. This is a missing capability (reliable webhook dispatch) rather than agent misbehaviour. No fabrication, no consent loop, no cross-event contamination occurred.

Missing capabilities:

• Reliable Spex UNW lead webhook submission — the handoff failed server-side despite correct agent behaviour

Webhook submissions

None captured.

Transcript

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

Visitor: please do

Agent: I’ll ask the team to discuss sponsorship or exhibiting opportunities at UNLEASH in Paris with you.

Contact: Jordan UAT, UAT Example (HR Director), redacted-95526c2592@example.invalid.

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 2 (first token 3048ms, total 3429ms)

Visitor: Yes, I consent. Please send the enquiry.

Agent: We haven’t been able to complete that handoff right now. Please email customersuccess@unleash.ai and the team will help route your sponsorship enquiry.