Creytix Desk
SLA clocks that stop when your office is closed.
A ticket engine with business-hours SLA timers, first-response tracking, per-agent workload, and a queue ordered by how close each ticket is to breaching.
A ticket raised Friday at 6pm is not late on Monday morning.
What it does for you
Business minutes, not wall-clock minutes
SLA elapsed time counts only the hours you are open. Every help desk that measures wall-clock time reports weekend breaches that never happened, and the metric quietly stops meaning anything.
The queue is sorted by risk
Tickets order by time remaining against their SLA, so the one about to breach is at the top — not the newest, and not the loudest.
Waiting on the customer is not your delay
Time in a pending state is tracked separately, so a ticket held up by an unanswered question does not read as a team failure.
Capabilities
- Business-hours SLA clocks
- First-response and resolution targets
- Risk-ordered queue
- Per-agent workload
- Unassigned-ticket report
Proof, not adjectives
- Engine ships and is tested
- src/lib/helpdesk/tickets.ts — business-minute arithmetic, first-response detection, SLA state, agent load and the risk-ordered queue, with its own suite.
- The test was wrong before the code was
- A queue test called a ticket fresh while dating it four days back. The engine was right; the fixture was fixed. Worth saying, because a test written to match the code proves nothing.
Related tools
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.