The ticket opens with the client, the device and the contract on it.
The service desk is the ticketing module of Service in The One Stack, the platform MSPs run their whole business on. It takes requests from email, phone, the portal and device alerts into one set of queues for your technicians and service managers. Each ticket carries the client, the contract and the response clock.
Service desk is part of Service, one of the six systems of The One Stack.
What it does.
One set of queues for every channel
Email, portal forms, phone calls and device alerts all open tickets in the same queues. A reply threads onto the ticket it belongs to.
The whole client in the sidebar
The ticket sidebar shows the device’s health, its security alerts, its backup status and the client’s billing history. A technician does not leave the ticket to find them.
SLA timers from the contract
Response and resolution targets come from the client’s contract. A ticket that breaches its target is flagged, and a high-priority one escalates to on-call.
Routing, macros and recurring tickets
Routing rules send a new ticket to the right queue. A macro applies a set of changes and a canned reply in one step, and recurring templates open scheduled tickets for you.
Approvals and satisfaction scores
A ticket can wait for a named client contact to approve it, by emailed link or in the portal. After a ticket is resolved a survey goes out, and the score is kept on the ticket.
Inside service desk.
More of the product, screen by screen.
The queue
Quick views sort the queue by whose it is and how close it is to its SLA. A ticket THEO resolved sits in the same list as one a technician is working, with the same record behind it.
How it connects.
Service desk reads and writes the same record as the rest of the platform.
An alert opens the ticket
A critical alert from monitoring opens a ticket with the device attached. A repeat of the same alert joins the open ticket.
A missed call opens the ticket
A missed call or a voicemail opens a ticket matched to the caller, with the call summary added as a note.
A detection opens the ticket
A detection from Defend arrives as a ticket with its recorded details, and response actions wait for a technician to approve them.
The clock starts on the ticket
A technician starts a timer or enters time from the ticket, and the entry carries the ticket’s contract.
The client moves it from the portal
From your portal a client asks for a call or an update, flags the ticket as urgent or confirms the fix. The request lands on the ticket, so nobody phones to ask where it stands.
A serious incident gets a room
A declared incident is run in a war room, with its timeline, playbook, client updates and evidence in one place.
What THEO does here.
THEO triages new tickets, summarizes long threads and drafts replies for a technician to send. When a request matches a runbook you have switched on for that client, THEO runs the fix through Tier Zero before a technician picks the ticket up. Anything outside the runbooks goes to a technician with the context on the ticket.
Questions
Questions about service desk
Does the service desk replace my PSA ticketing?
Yes. The service desk covers tickets, queues, SLA timers, macros, approvals and satisfaction surveys, on the record that also holds devices, contracts and invoices. Ticket history imports through Integrate.
Can clients open tickets themselves?
Yes. Clients open and follow tickets in your portal, by email, or through a form you publish. Every one lands in your queues with the client and the contract on it.
What does THEO do in the queue without asking?
THEO runs the runbooks you have switched on, at the level you set, for the clients you have opted in. Outside those runbooks it asks or hands the ticket to a technician. Isolating a device and changing a user’s account always wait for a person.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.