Skip to content

Your clients get help without the wait.

THEO for your clients is the client-facing side of THEO in The One Stack, the platform MSPs run their whole business on. A client’s staff ask THEO in your portal or on your phone line, and THEO fixes routine requests a runbook covers after it checks who is asking. Every answer is kept to that person’s own company.

Illustration, sample data. A client asks THEO in the MSP’s portal, and a request it cannot finish becomes a ticket with the whole chat.

What a client can do

A client’s staff ask in plain words, in the portal that carries your name.

Ask how to do something

THEO answers a how-to question in the chat, and opens a ticket when the answer needs a technician.

The platform

Open and track tickets

They describe the problem and the ticket opens. They ask where an open ticket stands, and the answer comes from the ticket.

Service desk

See their devices and invoices

They ask about their own devices and their company’s invoices, inside what their portal role allows.

Your clients

Reach your team

When THEO cannot help, the request becomes a ticket for your technicians with the conversation on it.

Your clients

Fixed on the spot

A stuck print queue is a routine request, and THEO has a runbook for it. When you have switched that runbook on for the client, THEO checks who is asking, clears the queue and tells the person it is done.

No ticket waits in line for something THEO already knows how to do. The run is still on the client’s record, so your team can see what was fixed and when.

Which requests are fixed this way is your choice, per runbook and per client.

Illustration, sample data. A routine request in the client portal: THEO confirms who is asking, runs the runbook and reports back.

What stays with you

Security findings and remediation arrive as a ticket to you, not as raw alerts to the client. The client is told their IT team has it.

A managed client’s user gets

  • Their own tickets, devices and invoices.
  • How-to help and routine fixes for their own device.
  • Plain status on a request.
  • A summary your team approved.

Your team gets

  • Security findings and alerts, as a ticket.
  • Investigation and remediation.
  • Requests that affect another person’s account or access, to approve.

Co-managed scope

A client’s internal IT gets more from THEO, inside the scope you grant.

Set per person

You mark a client’s internal IT person as co-managed. The wider scope belongs to that person, not to everyone at the company.

Co-managed IT

More, inside your grant

A co-managed user can ask THEO about their own company’s alerts and investigations, and request admin work and remediation, inside the scope you grant.

Co-managed IT

Still one company

The wider scope stops at their own company. Each request is checked against your grant and recorded.

Safety and control

Questions

Questions MSPs ask

Can my clients talk to THEO?

Yes. A client’s staff ask THEO in your client portal and on your phone line. They see your name, not ours.

What can THEO fix for a client without a ticket wait?

THEO fixes routine requests that a runbook covers and that you have switched on for that client, such as a stuck print queue. It checks who is asking first, and the run is recorded.

Can a client see another client’s data through THEO?

No. THEO answers a client’s user from their own company’s record, and a request that cannot be tied to a company is refused.

Do my clients see security alerts?

A managed client does not see raw alerts. Security findings and remediation arrive as a ticket to you, and the client gets status or a summary you approved.

Is THEO in the portal the same thing as THEO Bots?

No. THEO in the portal is support for the services you provide: tickets, devices, invoices and how-to help. THEO Bots is a separate subscription that gives a client’s staff assistants for their own work.

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.