Multi-tenant support desk
Customers, recruiters, and field agents open a ticket when they need help. Your team picks it up, replies, and sees it through to resolution. Every step is recorded in an audit trail that cannot be edited, and access is checked by role at every boundary.
Capabilities
Each team runs in a fully sealed environment. Tickets, users, and categories never cross a team boundary, so a single instance can serve many organisations without one ever seeing another's data.
Five roles, each with a precise boundary. Requesters see only their own tickets, Support works the queue, Managers control escalations, and Admins manage access. The rules are enforced on the server, never assumed in the UI.
A finite state machine defines every valid status change. Invalid moves are refused on the server, so no ticket can slip past the defined process, however the request is made.
Agents filter by Unassigned, Mine, Open, and Escalated. Priority and status changes apply at once and roll back on their own if the server declines, so the queue stays fast without ever showing a state the server rejected.
Every status change is written atomically alongside the ticket update. Who acted, when, and why are preserved for good; the history cannot be rewritten or deleted.
Requesters attach images and PDFs to a ticket directly. Agents search across subject and body as they type. Every result stays scoped to the active team.
How it works
Customers, recruiters, and field agents open a ticket from their portal. Each one is categorised, timestamped, and visible in the support queue the moment it arrives.
Support agents claim and prioritise each ticket, post a reply or an internal-only note, and move it through the defined status stages, one deliberate step at a time.
Managers escalate, close, or reopen. Every actor and every status change is kept in an audit trail that cannot be edited or deleted.
Sign in as a support agent, manager, or requester with the demo accounts. Nothing to install, and no sign-up required.
Open the demo →