Support tickets
A queue and a reply surface. The two screens a support agent lives in, ready for the system that holds the tickets.
⚠️ Pro edition
These screens are in the Pro download. The free edition ships the design system and the demo, not the application screens.
The screens
2 screens, at these routes in your download. Open them beside this page.
| Route | Screen | What it is for |
|---|---|---|
| /support-tickets | Tickets | The queue: subject, requester, priority, status, age and assignee. |
| /support-ticket-reply | Ticket | One ticket's conversation, its metadata sidebar, and the reply composer. |
What you get
- Priority and status as theme tokens, so an urgent row looks urgent in your palette rather than ours.
- A conversation view that distinguishes the customer, the agent and an internal note.
- The metadata beside the thread rather than above it, so an agent can read and act without scrolling.
What you connect
These are interfaces, not an application.They render, they hold their own state, and they talk to nothing. Everything below is your application's, and none of it is supplied.
- Your ticket store. Everything here is demo data.
- Email and channel ingestion. Nothing creates a ticket from anything.
- SLA. Age is displayed. No timer, breach or escalation is calculated.
- Assignment and routing. Picking an assignee sets a field.
Built from
Nothing here is a one-off. Each screen composes the same families documented in the reference, so changing a token moves them with the rest of the product.
data-table, badge, avatar, textarea, card.
Next
A customer screen, end to end builds one of these from an empty route, and Theming is how you make them look like yours.