Ticket routerPro
Sorts support requests into teams: mail, chat widget, Slack and GitHub issues arrive one by one, a model tags what they want, how they feel and how sure it is, and each lands in a lane; unsure ones wait for a person.
oxyn add ticket-routerSupport inbox router
Classified by Claude Haiku 4.5 · review below 70%
The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.
Rendered from Rust at build time · goes live when visible
When to use
- Watch support messages from Gmail, Intercom, Slack and GitHub get labelled with intent, sentiment and confidence and move into team lanes; low confidence goes to review.
When not to use
- Replays a multi-agent run on one clock: use Agent timeline instead.
- One model at a glance: use Model card instead.
- A small automation on a single rail: use AI workflow instead.
Installation
Ticket router is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.
oxyn add ticket-routerUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Routing
Tickets routed live.
Support inbox router
Classified by Claude Haiku 4.5 · review below 70%
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Strict
A stricter threshold sends more to review (Oxyn extra).
Support inbox router
Classified by Claude Haiku 4.5 · review below 90%
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Paused
Paused before the first ticket.
Support inbox router
Classified by Claude Haiku 4.5 · review below 70%
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
TicketRouter
| Prop | Type | Default | Description |
|---|---|---|---|
nowrequired | ClockMs | — | Host clock. |
paused | bool | Default::default() | Start paused. |
threshold | u32 | 70 | Review below this confidence, %. |
tuning | bool | true | Show the threshold control (Oxyn extra). |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | Pause, restart, speed, review buttons, the threshold |
| EnterorSpace | Pause or resume, move a ticket out of review |
| ←or→ | On the threshold slider |
Accessibility
- Labels are words (intent, sentiment, confidence), never colour alone; low confidence is also amber.
- Lanes show a count and the latest tickets; review buttons are named with the ticket and lane.
- Pause, resume, reviews and threshold changes are announced.
From the spec
Lanes are lists with counts in their headings; each routed ticket is announced. Every action returns the line the polite live region announces. The focus outline shows only for keyboard focus.
Motion & interaction
The incoming ticket shows its label chips, then slides into its lane; lane counts tick up.
Timing
Everything on screen is derived from the host clock now (no timers in the component), so playback, tests and the GPUI view agree.
| Transition | Duration | Easing |
|---|---|---|
| Per ticket | 2000 ms (TICKET_MS) | ease-out slide |
Reduced motion: streamed text and moves appear at their end state; progress still advances, without travel animation.
Responsive behaviour
- Four lanes in a row; under 600 px two by two.
- Ticket subjects ellipse; counts use tabular numerals.
Edge cases (spec)
Lanes scroll horizontally under 768 px; long subjects truncate. Checked at 1440, 768 and 390 px in light and dark with no text overlap. Chrome is monochrome grey; colour is semantic only (success, warning, danger, info) plus the providers' coloured brand marks.
Notes for AI
- Import
TicketRouterfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
AiKitViewinoxyn_gpui. - Props to set first:
now. - It reads a clock (
now) for live timers; pass one clock for the whole page rather than one per component. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.