Skip to content

An AI agent that resolves IT issues end to end.

For MSPs. Start with a supervised workflow on Autotask + Datto RMM or ConnectWise PSA + Automate.

Interactive simulation · Example tickets and data. No live systems are connected.

C

Claudia · AI IT engineer

Acme Corp support portal

C

Claudia: Hi Priya, I’m Claudia, Acme Corp’s AI IT engineer. What’s going wrong? Pick one, or describe it in your own words.

Most common tickets

Interactive demo: you’re the user, then the technician. Names and data are illustrative; the fix is simulated.

Connects to the tools your desk already runs

Behind Claudia

The model behind the platform

See the platform
AI agent roles
21
Agent skills
79
Workflows
157

Catalogue definitions from operating model v4.408.0. These counts describe the design; each pilot workflow is validated on the agreed stack.

The problem

Where your desk loses time

One email ticket, worked the way most desks work it today, and the same ticket with Claudia.

4
people touch it today
1
person touches it with Claudia

Counted from this example, not measured across desks.

  1. Priya emails the desk

    “Email’s not working.” One line, no detail.

  2. Waits in the queue
  3. The dispatcher reads it and assigns it

    Every ticket crosses your desk before anyone can work it.

    Dispatcher or team lead →
  4. Waits for a technician
  5. A technician calls Priya back for the details

    Half of every ticket is working out what it actually says.

    Service desk technician →
  6. Escalated to the Microsoft 365 admin

    Who finds yesterday’s policy change and fixes it.

  7. Notes written later, if at all
  8. The client mentions it at the next review

    You learn a client is unhappy at the renewal call.

    Account manager →

How it works

Five service-desk roles, one ticket, one approval

They ask the right questions, get your technician’s approval, fix the problem, document it and close the ticket.

  1. 01

    Ticket opened

    Self-Service

  2. 02

    Gathering context

    Triage

  3. 03

    Questions

    Self-Service

  4. 04

    Diagnosis

    Resolution

  5. 05

    Checking permissions

    Dispatch

  6. 06

    Technician approval

    Dispatch

    + your technician

  7. 07

    Running the fix

    Resolution

  8. 08

    Verify

    Resolution

  9. 09

    Documented

    Resolution

  10. 10

    Ticket closed

    Watchdog

Self-Service
Asks the user for what’s missing, before a technician has to.
Triage
Gathers context, classifies the ticket and sets priority against the client’s SLA.
Dispatch
Checks permissions and routes the approval to the right technician.
Resolution
Diagnoses, runs the approved fix, verifies it and documents it.
Watchdog
Watches the SLA and follows up with the client.

The roles are built into the AI Autopilot platform. Claudia is one AI engineer working in all five.

See the platform

What Claudia reads

Context first, questions second

Before it asks your user anything, Claudia reads the systems your desk already runs.

Pick a source.See how it connects

Gathering context · Autotask

Reads ticket history, configurations and alerts.

  • Autotask: Device LAPTOP-PS14 · 2 similar tickets this month, both fixed in Microsoft 365For “I can’t send or receive email”
  • Autotask: One lockout ticket for Priya last quarter, fixed by re-signing a phoneFor “My account keeps locking me out”
  • Autotask: In warranty until March 2027 · no hardware ticketsFor “My computer is really slow”
  • Autotask: No open printer tickets for AcmeFor “The printer isn’t printing”
Claudia runs in Microsoft Foundry on Azure, with models from
  • Anthropic · Claude
  • OpenAI · GPT
Data in the cards is illustrative, from the demo above.

Guardrails

Every fix waits for your technician

That is how the supervised launch works. Pick an action to see what Claudia checks first, and what it refuses.

Ask Claudia to…

Checking permissions

  • Claudia can unlock accounts in Microsoft Entra
  • Unlocking a user is inside Acme’s approved scope
  • J. Okafor can approve account changes for Acme

Technician approval

Unlock Priya Shah’s account in Microsoft Entra

Requested of J. Okafor · Microsoft 365 admin

You’re J. Okafor now. Nothing changes until you decide.

Illustrative: the checks for Acme Corp in the demo above.

Your data

Agree how AI may use your data
Confirm the AI services enabled for your pilot and their training-use restrictions in the applicable data-processing terms.
Keep secrets out of ticket content
Use approved connection setup for credentials. Check masking and redaction with a harmless test value before granting access; do not put passwords or keys in tickets or website forms.
Test the permission boundary
Confirm the service account and requester permissions. Test a denied action and a different client boundary before accepting a workflow.
Start with technician approval
The launch scope is supervised. Agree the permitted action, reviewing technician and evidence to inspect before any expansion.
Join the waitlist

Claudia is invite-only for a limited supervised launch.

Built inside an MSP

Built inside ETech 7, the MSP Emil Isanov founded in 2012 — and run there first.

2012
ETech 7 founded
600
ticket types mapped into the platform by people who ran the desk
Research · Reference architectureThe Architecture of the Agentic IT EngineerWhat IT operations can learn from how frontier AI labs build coding agents.Read the brief

The list · 26 pages · PDF

The 10 ticket types that cost an MSP the most

The ten ticket types that cost your desk the most, with the lever for each.

Questions

What MSPs ask first

The launch, who stays in control, and where your data goes.

Getting started

Which stacks are the first launch focused on?

Starting with Autotask + Datto RMM and ConnectWise PSA + ConnectWise Automate. Claudia is invite-only for a limited supervised launch. Claudia’s AI agents resolve tickets end to end: they ask the right questions, get your technician’s approval, fix the problem, document it and close the ticket. Microsoft 365 is one of the systems Claudia works in alongside either pairing, not a third launch stack. Pilot scope and prerequisites are confirmed with your team.

Can Claudia act without a technician approving?

Not in this launch: it is supervised. The operating model defines higher autonomy levels for its agent roles, but unattended execution is not part of this launch offer. Any step further needs a separately agreed scope and evidence.

Do we have to migrate off our PSA?

The initial launch is designed around your existing Autotask + Datto RMM or ConnectWise PSA + ConnectWise Automate pairing. Confirm tenant access, permissions and the technician's workflow during scoping; catalogue coverage alone does not establish that every setup is ready.

Who does the setup work?

The published offer includes a two-hour onboarding session at no charge. Our team reviews the agreed workflow, integration prerequisites and technician walkthrough with you. The session is not a guarantee that every tenant or broader catalogue workflow will be ready in two hours.

Your data

Which AI providers do you use?

Request the current AI provider and region schedule for your pilot configuration. Review training-use restrictions, request retention and any monitoring or application logs in the applicable data-processing terms before connecting client data.

What happens to our data if we leave?

Review the export, deletion, backup and optional transition-assistance periods in your service agreement. Different records can have different retention requirements; request the applicable schedule before paid access.

Are you SOC 2 certified?

Not yet — our SOC 2 Type II audit is underway, with the report expected Q1 2027. In the meantime our 73 security controls are continuously monitored by Vanta and published live in our Trust Center, covering infrastructure, internal procedures, product, organisational, and data privacy controls. Ask us for the report once it is issued.

Start with a supervised workflow

Want to take Claudia for a spin in your IT environment? Claudia is invite-only for a limited supervised launch.

Your tracking preferences

Analytics help us understand website use. Visitor-identification tools connect visits to a company or CRM record for follow-up. Both stay off until you choose. You can allow analytics alone, and forms work with every choice. See the services and storage details.

Change your choice anytime using Tracking preferences in the footer.