Tickets: opening them, working them, and closing them out.
The one page that reads every open alert across every client and every monitored domain, shown on an instance with no open alerts on any domain, any status, or any time frame yet.
Create a multi-step project by hand or from a saved workflow, then read the Schedule page's day timeline and mark a tech out of office.
Close a resolved ticket with a plain-language reply, then review, edit, and publish the knowledge base article Elise drafts from it.
How to log a client's problem in ezCyber, step by step, and every other way a ticket can be created.
Read the plain-sentence reason behind a ticket's assignment, see the order dispatch tries before it gives up, give one client a dedicated tech, and see what changes when a person reassigns a ticket by hand instead.
How the Service Desk list works: the My Tickets tab, board tabs, the Needs Attention queue, filtering, and saving a view so you or your team can reuse it.
Answer a client on a ticket and move its status forward in the same action, then see the reply, the time it logged, and the status change on the record.
Attach a documented procedure to a ticket as a checklist, tick off steps as the work gets done, and know exactly what removing it does.
A response target is a promise the shop made to a client, and working out what it is was never the technician's job. What a technician needs is narrower: which of the conversations in front of me has a clock running, how much of it is gone, what stops it, and what to type next. This walk stays in that seat on one instance. It covers every state a ticket's SLA control can be in, the exact words on screen for each, and what to do about it.
Read the SLA chip and time entries, set the billing status, ask Elise about the ticket, and know why a delete can be blocked.