Ticket Triage Agent — NeIO Meeting Assistant

Walks 25 live support tickets through a fixed agent pipeline: parse, compliance gate, route, SLA, draft reply, human-approval gate, log. Every step below names the tool, the input, and the result — nothing is a black box.

Product: NeIO Meeting Assistant Accounts A–E Source: data/tickets.json Draft only — nothing here sends or deletes anything

Processed

Auto-resolved

Escalated to human

Remaining

speed

Press Step or Run to start the walkthrough.

Processed tickets

Ticket	Account	Area	Prio	Routed to	Outcome

No tickets processed yet.

Check by hand before you trust this: of the 25 tickets, exactly 4 carry needs_human:true in the source data, and all 4 are in the privacy area (recording-deletion requests: T-5104, T-5110, T-5116, T-5122). Run the page to completion and confirm the "Escalated to human" tile reads 4 and the "Auto-resolved" tile reads 21 — that is the one number on this page you should verify against data/tickets.json yourself, not take on faith.

Cost tradeoff: this pipeline runs 7 tool calls per ticket (parse, compliance gate, route, SLA, draft, human-gate check, log) versus one prompt that classifies all 25 tickets at once — roughly 5–8× the tokens per ticket for the multi-step version. The gate that justifies it: a single prompt would happily auto-close a privacy deletion request; the pipeline forces every privacy-area ticket through a human-approval step before anything is logged as resolved, regardless of what the model would have guessed. The human gate sits at step 6, before logging, never after.