One screen from alert to closed.
The One Stack is the platform MSPs run their whole business on, and for a service team it is one screen from alert to closed. The ticket carries the device, the person, the contract, the history and the documentation, and the remote session, the script and the time entry start from it. THEO handles the requests its runbooks cover and hands over the rest with the context on the ticket.
The ticket with everything on it
An alert, a call or an email opens the ticket with the record already attached. Nobody types a company name.
The device
The device record from the agent is on the ticket, with the alert that raised it.
The person
The caller or sender is matched to a contact and a client before the ticket opens.
The contract
The ticket shows the contract that covers the client and runs the response clock that contract sets.
The history
Earlier tickets for the same client and the same device sit beside the open one.
The documentation
Configurations, runbooks and procedures for that client open from the ticket. Credentials come from the vault by checkout, with an audit trail.
Fix from where you are
The tools start from the ticket, so the work and the record stay in one place.
Remote session
Start an attended or unattended session from the ticket or the device. On an attended device the person approves first.
Script
Run a script from the library against the device on the ticket, or let remediation run on a schedule or an alert.
Onsite, on mobile
The mobile app carries your schedule and the ticket to the site, with check-in on arrival.
THEO as the first line
THEO takes requests by phone, email, form and the portal. What happens next depends on whether a runbook covers the request.
THEO runs the fix
- A request that matches a runbook you have switched on for that client, such as a full disk or a stuck print queue.
- On autopilot THEO runs the fix and reports what it did. On assist it runs the fix when it is confident and asks when it is not.
- Every run is recorded step by step, so you can read what it did.
A technician gets it
- Anything outside the runbooks, with the caller, the device, the contract and the details already on the ticket.
- Isolating a device and changing a user’s account. These always wait for a person.
- Runbooks set to watch or suggest. THEO records or proposes the fix, and a technician decides.
For the service manager
Queues, service levels, on-call and workload read from the same tickets your team is working.
Queues
Every channel lands in the same queues, with macros and satisfaction scores on the same tickets.
Service levels
Response and resolution timers come from each contract and run on every ticket it covers.
Workload
The dispatch board shows who is scheduled, who is available and what is unassigned. You reassign from the board.
Reporting
Service levels and technician performance read from the same tickets and time entries in analytics.
Questions
Questions MSPs ask
Does the ticket open with the device already on it?
Yes. An alert from the agent opens the ticket with the device attached. A call or an email is matched to the person and the client before the ticket opens.
Can I start a remote session from the ticket?
Yes. Attended and unattended sessions start from the ticket or the device. On an attended device the person at the keyboard approves the session first.
What does THEO do without asking?
THEO runs the runbooks you have switched on, at the level you set for each client. Outside its runbooks it asks or hands the request to a technician, and isolating a device or changing a user’s account always waits for a person.
Can I see what THEO did?
Yes. Every runbook run is recorded step by step. On autopilot THEO also reports what it did when the run ends.
Is there a mobile app for technicians?
Yes. The mobile app for iOS and Android carries the schedule and the ticket for onsite work, with check-in on arrival.
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.