Skip to content

An AI practice, under your name.

THEO Bots is the AI service an MSP provides to its clients’ own staff in The One Stack, the platform MSPs run their whole business on. It gives a client’s people role-based assistants in your client portal, connected to the systems the client runs on. You allocate the seats, set the price and bill it.

Illustration, sample data. A bot in the client’s portal prepares an email draft, and it waits for the person to edit or send it.

Bots built around roles

A bot is THEO set up for a job in the client’s business.

A starter bot per role

Each industry comes with starter bots for the roles in it. A client enables a starter bot and renames it.

One THEO, one memory

Bots are roles of the same THEO. A person’s memory and past chats follow them from one bot to the next.

In your portal and your apps

Bots open from your client portal and from your branded mobile and desktop apps, with your name and colors.

The platform

They draft. A person decides.

A bot organizes, tracks and drafts. The person in the client’s business decides and sends.

Starter bots by industry

Proof slot

Launch industries and starter roles

The confirmed list of industries at launch and the starter role bots in each.

How a connector works

A connector is how a bot reaches a system the client runs on.

  1. 01

    Connect once for the company

    An admin connects the system once, for the whole company. No bot holds a sign-in of its own.

  2. 02

    Scope it

    Before anything is connected, the catalog shows what the connector reads and what it can write.

  3. 03

    A bot reads

    A bot reads through the connection, limited to what the person signed in is allowed to see.

  4. 04

    A bot prepares a draft

    When the work calls for a message, an entry or a change, the bot prepares it and puts it in front of the person.

  5. 05

    The person confirms

    Nothing is sent or changed in the client’s own systems until the person signed in confirms it. No setting skips this.

  6. 06

    Switch it off

    An admin can turn a connector off for bots without disconnecting the system from anything else. Each connection, use and refusal is recorded.

Illustration, sample data. Everything a person’s bots have prepared waits here until that person edits, sends or dismisses it.

Available connectors

Proof slot

Connector catalog

The connectors available at launch, by category, with what each one reads and writes.

The client stays in charge

What a bot prepares waits for a person, and the client’s admin sets the rules for the whole company.

One list of what is waiting

Everything a bot has prepared waits in one list for the person it belongs to. They read it, edit it, send it or dismiss it.

On a schedule

A bot can run a job on a schedule, as the person who owns it. It reads and prepares. Anything it would send waits in the same list.

Rules for the whole company

For each kind of action, the client’s admin chooses whether a bot asks first or the action is off. There is no setting that lets a bot act without asking.

Safety and control

A pause and a log

The admin can pause every bot with one control, and reads and exports the activity log.

Seats you allocate

Two people manage seats: you, and the client’s own admin.

You set the number

You decide how many seats each client has.

Their admin assigns them

The client’s admin gives seats to people and takes them back, inside your number, without asking you each time.

Your clients

You can step in

Your team can also assign a seat for a client directly.

Every change is recorded

Each seat change is recorded with which side made it. You and the client read the same record.

What you see

You are the seller, not a reader. What a client’s staff ask a bot, and what it prepares for them, stays with the client.

You see

  • The seats each client has and who holds them.
  • Usage for each client.
  • What to bill.

You never see

  • A client’s chats.
  • Their drafts.
  • Their automations.
  • Their memory.

How it is sold

THEO Bots is sold the way you sell client apps: through you.

A subscription bought through you

Your client buys THEO Bots from you. The One Stack bills you, and you bill your client.

Client apps

At your price

You set what a seat costs your client.

On your invoice

Seats are a recurring line on the client’s contract, and the invoice run bills them with everything else.

Contracts, invoices and payments

Priced separately

THEO Bots is priced separately from the platform plan. Your rate is on the partner rate card.

Pricing

Questions

Questions MSPs ask

What is THEO Bots?

THEO Bots is the AI an MSP provides to its clients’ own staff. It gives them role-based assistants in the MSP’s client portal, connected to the systems the client runs on, sold and billed by the MSP.

Can a bot send an email or change a record on its own?

No. A bot prepares a draft, and the person signed in confirms before anything is sent or changed in the client’s own systems. A bot does not pay, sign, approve, delete or change permissions.

Can I read my clients’ conversations with their bots?

No. You see usage and billing for each client. You do not see a client’s chats, drafts, automations or memory.

Who assigns THEO Bots seats?

You allocate seats to each client, and the client’s own admin assigns them to people. Your team can also assign a seat for a client directly.

How is THEO Bots priced?

THEO Bots is priced separately from the platform plan. You buy seats at your partner rate and set your own price to your clients. See pricing.

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.