S.02TICKET ROUTER
ticket router.
Read the ticket. Classify the intent. Draft a reply a human can sign off on — or escalate the ones that are about to churn.
pick a fixture_
or
turnstile · invisible
waiting for verification token...
~/demo/ticket-router.log
idle · waiting for input
model_ —
pick a fixture on the left, then press [ run demo ].
~/outbound/draft-reply.eml
draft reply · awaiting approval
no draft yet
proposed · no side effects in demo mode
── log ──
no log entries yet
01— ingest
zendesk, helpscout, shared mailbox, or a webhook — wherever tickets land today.
02— reason
classify intent and severity, draft a reply, detect churn signals before they snowball.
03— act
route to the right team with an approval-gated draft. nothing auto-sends without a human.
This demo runs on free-tier AI against fake data. In production, the same workflow writes to your real tools, logs every run, and is reversible — the reasoning step is the smallest part of the stack.
[ deploy one like this → ]