ⓘ Demo mode: read-only demonstration. Changes are disabled — request full access.
DEMO MODE
Changes are disabled in the demo.
You are viewing a read-only demonstration. Browse everything freely — adding, editing and deleting are switched off so the demo stays tidy for everyone.
For each screen we answer the same questions — what it is, why it exists, how to use it, who it is for, and what business problem it solves.
Tickets & the ticket screen
Where the actual work happens: the conversation, the notes, the attachments and every action available on a case.
What is it?
The full ticket workspace — customer details and history in the sidebar, the complete message thread in the centre, and the actions available: reply, internal note, assign, change status or priority, add labels, attach files, merge, escalate, close.
Why does it exist?
Everything an agent needs must be on one screen. The moment they have to open another system to understand the customer, quality and speed both drop.
How does it work?
1Read the thread from the top — previous replies may already contain the answer.
2Check the customer sidebar for past tickets and internal notes before replying.
3Reply to the customer, or add an internal note for colleagues only.
4Update status honestly — "pending" means waiting on the customer, not waiting on you.
5Reassign or escalate rather than letting a ticket sit in the wrong place.
WHO USES IT
Support staff
WHAT MANAGEMENT ACHIEVES
Any agent can take over any case competently, because the whole history is in front of them.
In practice
A customer replies to a two-week-old thread. A different agent opens it, reads eight previous messages and the engineer’s internal note, and answers correctly on the first attempt.