{"id":"808cc83d-46e4-4e87-94fc-1ac129a26465","task":"Implement a deflection and escalation orchestration flow — detect unresolved AI chat intent and create a helpdesk ticket with full conversation context","domain":"general-cx-orchestration","steps":["Receive conversation events from your AI chat platform (Intercom Fin, Zendesk AI agent, or custom LLM) via webhook when a session ends or escalation is explicitly requested by the user","Evaluate escalation criteria in your orchestration layer: check intent confidence score, session turn count, presence of escalation trigger phrases, or explicit 'talk to human' detection","Compile conversation context: extract full transcript, detected intent, customer identifier, and any structured data collected (order number, account ID) from the AI session payload","POST to your helpdesk API (e.g., Zendesk POST /api/v2/tickets, Freshdesk POST /api/v2/tickets) with subject derived from detected intent, a description containing the transcript, requester_id mapped from customer identifier, and tags indicating AI-sourced origin","Set ticket priority and routing group based on the escalation reason — unresolved billing issues route to billing queue; technical issues route to tier-2 team","Notify the customer via the original channel (chat or email) with the ticket ID and expected response time, and close the AI session gracefully"],"gotchas":["Customer identity resolution between the AI chat platform and the helpdesk is the most fragile step — anonymous chat sessions may not have an email or account ID; build a fallback that creates a new contact rather than failing the whole escalation","Transcript encoding varies across platforms: some deliver HTML, some plain text, some markdown; sanitize before inserting into ticket description fields to prevent rendering issues or injection in the helpdesk UI","Escalation loops occur when the helpdesk auto-responder sends an email that the AI platform interprets as a new inbound conversation — use ticket tags or email headers to exclude AI-originated tickets from re-entering deflection flows"],"contributor":"waymark-seed","created":"2026-06-13T03:24:47Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/808cc83d-46e4-4e87-94fc-1ac129a26465"}