Skip to content

If the fix is in a runbook, THEO runs it.

Tier Zero is the first-line automation engine in The One Stack, the platform MSPs run their whole business on. It takes requests from phone, email, forms and the client portal, and THEO fixes the ones a runbook covers without a technician in the middle. Everything else reaches a technician with the context assembled.

Illustration, sample data. A runbook run on a ticket: which runbook matched, each step with its result, and the check after.

Intake on every channel

One engine sits behind every way a request arrives. The same runbooks, the same settings and the same record apply to each.

Phone

THEO answers the call, matches the caller and takes the request in conversation.

AI receptionist

Email

An email is read the same way, and lands on the same client record.

Service desk

Forms and the portal

A client’s staff fill in a form or ask THEO in your portal. The request arrives with the person and their company on it.

THEO for your clients

Signals from the platform

A missed backup or a suspicious sign-in can start a runbook too, under the same settings and the same approvals.

Monitoring and reporting

A request, start to finish

The same line, whichever channel the request came in on.

  1. 01

    The request arrives

    A person calls, emails, fills in a form or asks in the portal. The request lands on the client’s record.

  2. 02

    THEO works out what is being asked

    THEO reads the request and matches it to a runbook. If a detail is missing, it asks the person for it.

  3. 03

    THEO checks who is asking

    Before a runbook changes anything, THEO verifies the person to the level that runbook requires. A phone number on its own is not proof.

  4. 04

    THEO checks your settings

    Your policies, the client’s opt-in and the runbook’s level on the ladder decide what happens next: record it, propose it or run it.

  5. 05

    THEO runs the runbook

    On autopilot, or on assist when THEO is confident, the steps run on the device or in the platform. Each step is recorded as it happens.

  6. 06

    THEO tells the person it is done

    The person hears back on the channel they used, and the ticket carries what was run. If the runbook cannot finish, the request goes to a technician.

The ladder

Every runbook sits on one of four levels, and a runbook can also be switched off. Each runbook moves up when you move it, per client. Nothing moves up by itself.

LevelWhat THEO doesWhat your team does
WatchRuns nothing. Records what it would have done.Reads the record to check THEO’s judgment.
SuggestProposes the fix and queues it.A technician approves or declines each one.
AssistRuns the fix when it is confident. Asks when it is not.Decides the ones THEO asks about.
AutopilotRuns the fix and reports what it did.Reads the report. Nobody has to approve.

The runbook library

The library comes with pre-built runbooks for first-line work, by category. Each one is yours to edit, and you can write your own. Every save keeps the earlier version.

CategoryExamples
Devices and hardwareA slow device, a full disk, a service that needs a restart, a driver update.
PrintingInstalling a printer, clearing a stuck print queue.
NetworkReconnecting a VPN, Wi-Fi and DNS troubleshooting, mapping a network drive.
Email and collaborationA full mailbox, an out-of-office reply, recovering deleted mail, a broken meeting.
Software and licensingInstalling from your catalog, diagnosing an app that crashes, a license request.
Identity and accessLocked accounts, password and multi-factor requests. Changes to an account wait for a person.
SecurityA phishing report, a suspicious sign-in. Isolation waits for a person.
Backup and recoveryA missed backup, restoring a file.
PhoneNo dial tone, voicemail setup.
Staff changesNew-hire onboarding and offboarding. Account changes in them wait for a person.
Illustration, sample data. The runbook library: each runbook with its mode on the ladder and the guardrails that hold it.

When it asks or hands off

Anything outside the runbooks goes to a technician with the context assembled: the person, the device, the ticket and what THEO already tried.

THEO asks or hands over when

  • No runbook covers the request.
  • THEO is not confident it has matched the right runbook.
  • It cannot verify who is asking.
  • A policy you set, or the client’s opt-in, says no.
  • The runbook stops partway.

Always waits for a person

  • Isolating a device, or releasing one from isolation.
  • Changing a user’s account.
  • Disabling or suspending a user.
Illustration, sample data. Requests THEO handed to a technician, each with the reason and the context it had gathered.

Questions

Questions MSPs ask

What is Tier Zero?

Tier Zero is the part of The One Stack where THEO takes first-line requests and fixes them with runbooks. It works behind phone, email, forms and the client portal.

Does THEO need approval to run a runbook?

Not when you have set that runbook to autopilot for that client. On assist THEO runs the fix when it is confident and asks when it is not, on suggest a technician approves each one, and on watch nothing runs.

Can I edit the runbooks?

Yes. Every pre-built runbook is editable, you can write your own, and each save keeps the earlier version.

Can I set THEO differently for each client?

Yes. Each client is opted in by you at a level of its own, and a client can be excluded entirely. A contact can be set narrower than their company, never wider.

What happens when THEO cannot fix a request?

The request goes to a technician with the context assembled. The ticket carries the person, the device and what THEO already tried.

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.