MSP Operations
How can MSPs cut ticket volume without adding headcount?
For most MSPs, ticket volume has been a headcount problem: more clients mean more tickets, which mean more technicians. An autonomous IT engineer breaks that link by resolving IT requests end to end, deployed multi-tenant across the entire client base with each client's data isolated. Because it resolves L1 through L3 autonomously and is priced per resolution rather than per seat, cost tracks the work done, not the number of technicians on the payroll.
- Updated
- July 2026
- Read time
- 10 min read
- For
- MSP owners, service delivery leads
- Topic
- MSP Operations
In brief
- For MSPs, ticket volume has historically been a headcount problem: growth means more tickets, which means hiring more technicians.
- An autonomous IT engineer deployed multi-tenant across the entire client base changes that math by resolving requests end to end rather than queuing them for a person.
- It handles L1 through L3 autonomously, from password and access work up to deeper configuration and troubleshooting, escalating only genuine judgment cases.
- Each client stays isolated with its own encrypted data, and the tool can be presented under the MSP's own brand.
- Outcome-based pricing means cost tracks resolutions, not seats: Dex, built by SysAid, is $1.99 per resolved ticket with a $100 free credit to start.
Best for
MSP owners and service delivery leads who need to scale the number of clients served without scaling technician headcount proportionally.
Grounded in how Dex, an autonomous IT engineer built by SysAid, is designed for multi-tenant MSP deployment.
Why do MSP margins break as they grow?
MSP margins break when growth is tied to headcount. In the traditional model, more clients generate more tickets, and more tickets require more technicians to work the queue. Because a large share of that queue is routine L1 and L2 work, the MSP ends up paying skilled people to reset passwords, grant access, and provision accounts. Revenue rises with each client, but so does labor cost, so the margin per client stays flat or shrinks as the operation scales.
The structural problem is that ticket volume and staffing are locked together. Every new client adds a predictable stream of repetitive requests, and the only lever a queue-based operation has is to hire, which is slow, expensive, and hard to reverse when volume dips. It also concentrates senior engineers on low-value work, which raises turnover risk and leaves less capacity for the higher-margin project work MSPs actually want to grow. To improve margin, an MSP has to break the link between the number of tickets and the number of people needed to close them.
Key takeaways
- Traditional MSP growth ties ticket volume directly to technician headcount.
- Much of the queue is repetitive L1 and L2 work handled by skilled staff.
- Margin per client stays flat because labor cost scales with volume.
How does a multi-tenant autonomous engineer change the math?
A multi-tenant autonomous engineer changes the math by resolving requests end to end across every client from a single platform, rather than adding each request to a technician's queue. Instead of hiring in proportion to volume, the MSP deploys one autonomous engineer that acts inside each client's environment and closes the routine and mid-tier work itself. Growth in client count no longer forces a matching growth in staffing, so capacity scales with software rather than payroll.
The model works because the engineer operates independently per tenant while being managed centrally. Dex is built multi-tenant, with per-organization isolated databases and encryption keys, so an MSP can run it across many clients at once without their environments mixing. Employees at each client interact with Dex Go inside Microsoft Teams and Slack, and the MSP's admins drive complex operations from the Dex Pro console using delegated permissions scoped to each tenant. The result is that the MSP's people spend their time on escalations and higher-value engineering, while the repetitive volume is absorbed by the engineer.
Key takeaways
- One autonomous engineer serves the whole client base, deployed multi-tenant.
- Capacity scales with software rather than with technician headcount.
- MSP staff shift from working the routine queue to handling escalations and project work.
What kinds of tickets get resolved autonomously?
An autonomous IT engineer resolves the bulk of an MSP queue: L1 through L3 requests handled end to end inside connected systems. That includes routine L1 work such as password and MFA issues, access requests, SharePoint permissions, and onboarding provisioning, and extends into deeper L2 and L3 troubleshooting, configuration, and admin tasks that used to require a senior technician. Dex targets resolving over 90 percent of IT requests autonomously, with only genuine architectural or judgment cases escalating to a person.
This range matters for MSPs because so much of the queue is exactly the repetitive, well-defined work that autonomous resolution handles best, while the extension into L2 and L3 means the engineer is not limited to the shallowest tier. Dex acts directly inside Microsoft 365, Google Workspace, Okta, and other SaaS, and can even build a new integration to a platform with a REST API mid-conversation when a task requires one. When a case genuinely needs human judgment, it escalates with full context attached, so the technician who picks it up is not starting from scratch.
Key takeaways
- Resolves L1 to L3, not just first-line password resets.
- Targets over 90 percent autonomous resolution across the queue.
- Escalates genuine judgment cases to a human with full context attached.
Examples
L1: access and provisioning
Password and MFA resets, SharePoint access, and new-hire onboarding provisioning across a client's Microsoft 365 tenant.
L2: configuration and troubleshooting
Diagnosing and fixing email delivery or device issues, and applying configuration changes that previously waited for a technician.
L3: deeper admin operations
More complex admin tasks across M365, Google Workspace, and Okta that a senior engineer would otherwise own.
How does it stay isolated per client, and can it be white-labeled?
Multi-tenant isolation is a core part of the design: each client runs on its own isolated database with its own encryption keys, so one tenant's data is never accessible to another. Actions in each environment run through delegated permissions scoped to that tenant, not a shared master key, and every action is captured in a full audit trail. Because the experience lives inside each client's own Microsoft Teams and Slack and the MSP controls the deployment, it can be presented under the MSP's own brand.
Isolation is what makes multi-tenant deployment safe to sell. Dex uses per-organization isolated databases and encryption, so serving many clients from one platform does not blur the boundary between them. Access is bounded by delegated permissions, following least privilege, and Dex Go is scoped so it can only act on each requesting user's own account. On the compliance side, Dex is certified to ISO 27001, 27017, and 27018, is SOC 2 Type 2 compliant, GDPR compliant, and HIPAA-aligned, which are the assurances an MSP's clients will ask about. This lets an MSP offer autonomous resolution as its own service while keeping each client's environment cleanly separated.
Key takeaways
- Per-organization isolated databases and encryption keep tenants cleanly separated.
- Delegated permissions scope access per tenant, and every action is audited.
- The MSP controls the deployment and can present it under its own brand.
How does per-resolution pricing help MSPs?
Per-resolution pricing helps MSPs because cost tracks the work actually completed rather than the number of seats or technicians. Instead of paying per user regardless of activity, the MSP pays only when the engineer resolves a ticket. Dex is $1.99 per resolved ticket, with a $100 free credit to start, and no per-seat fee. That aligns the MSP's cost with the value delivered and makes the economics predictable as the client base grows.
The shift matters most for MSPs because their cost base has always been labor, which is fixed and slow to adjust. Outcome-based pricing turns a large part of resolution cost into a variable that moves with demand: quiet weeks cost less, busy weeks cost more, and there is no idle capacity to pay for. Combined with autonomous resolution of the routine queue, this lets an MSP take on more clients without a proportional jump in either payroll or software seats. For a fuller treatment of how outcome-based pricing compares with per-seat and per-agent models, see the related guide on per-resolution pricing.
Key takeaways
- Cost tracks completed resolutions, not seats or technicians.
- Dex is $1.99 per resolved ticket with a $100 free credit and no per-seat fee.
- Variable, outcome-based cost makes scaling the client base more predictable.
Is there proof this works in the field?
Yes. Grand Traverse County reported unlocking significant value in a single day with Dex. In the words of Cliff DuPuy, Director of IT at Grand Traverse County, "Dex helped us unlock $67K in value in a single day." It is a concrete example of how much routine and mid-tier work an autonomous engineer can absorb once it is deployed against a real queue.
The underlying technology comes from SysAid, an established IT service management provider trusted by more than 3,000 organizations and millions of users, which is the track record behind Dex's autonomy and policy model. For an MSP evaluating whether to put autonomous resolution in front of clients, that combination of a documented customer outcome and a mature ITSM heritage is the kind of evidence that de-risks the decision.
Key takeaways
- Grand Traverse County reported unlocking $67K in value in a single day with Dex.
- Dex is built by SysAid, trusted by 3,000+ organizations and millions of users.
- A documented outcome plus mature ITSM heritage de-risks adoption for MSPs.
Scaling by headcount vs scaling with an autonomous engineer
| Feature | Autonomous engineer (multi-tenant) | Adding headcount |
|---|---|---|
| How capacity scales | With software, deployed across all clients at once | By hiring and training more technicians |
| Who handles routine L1-L2 work | The engineer resolves it end to end | Skilled technicians work the queue |
| Cost structure | Variable: per resolution, no per-seat fee | Fixed labor cost that grows with volume |
| Response to volume spikes | Absorbs spikes without new hires | Requires overtime or new headcount |
| Per-client isolation | Per-organization isolated data and encryption | Depends on tooling and process |
| Where senior staff time goes | Escalations and higher-margin project work | Split across routine tickets and projects |
| Auditability | Full audit trail of every action per tenant | Varies by ticketing and process |
What are the real trade-offs for an MSP?
Advantages
- Serve more clients without hiring technicians in lockstep with ticket volume
- Resolve L1 to L3 autonomously, freeing senior staff for higher-margin work
- Deploy multi-tenant from one platform with per-client data isolation
- Pay per resolution, so cost tracks value delivered rather than idle seats
- Present the service under the MSP's own brand
- Full audit trail per tenant supports client trust and compliance conversations
Limitations
- Each client's systems must be connected with correctly scoped delegated permissions
- The MSP needs to define policies that reflect what it will and will not allow per tenant
- A minority of judgment-heavy cases still escalate to a technician by design
- As with any new capability, MSPs should ramp trust with human-in-the-loop review before widening autonomy
How does an MSP adopt an autonomous IT engineer, step by step?
Adoption is a staged rollout that starts with a pilot tenant and widens across the client base as the results prove out.
- 1
Pick a pilot client and its highest-volume requests
Start with one client and the request types that recur most, such as password and MFA issues, access, and provisioning, where autonomous resolution delivers the fastest wins.
- 2
Connect that tenant with delegated permissions
Integrate the client's systems, such as Microsoft 365, Google Workspace, and Okta, using delegated permissions scoped to that tenant rather than a shared master key.
- 3
Define per-tenant policies
Set the code-level policies that govern what the engineer may do for that client, tuned by scope such as tenant, department, and action. No matching policy means no action.
- 4
Run with human-in-the-loop approval
Start with actions surfaced for review in Dex Pro before they execute, using "Approve Always" for repetitive bulk operations once you trust them.
- 5
Roll out Dex Go to the client's employees
Give the client's employees access inside Microsoft Teams and Slack so they can describe problems in plain language. Dex Go acts only on each requester's own account.
- 6
Verify results, then expand across the client base
Use the audit trail and resolution results to confirm value, then replicate the deployment across additional tenants, widening autonomy for request types that have proven reliable.
What should an MSP evaluate when choosing an autonomous engine?
These criteria separate a tool that genuinely reduces an MSP's labor dependency from one that only assists technicians.
- Multi-tenant isolation
- Confirm per-organization isolated data and encryption so serving many clients from one platform never mixes their environments.
- Resolution depth
- Verify it resolves L1 through L3 end to end, not just first-line password resets, so it absorbs a meaningful share of the queue.
- Permissions model
- Prefer delegated permissions scoped per tenant over a shared master API key with broad standing access.
- Pricing model
- Look for outcome-based, per-resolution pricing so cost tracks value delivered rather than seats or technicians.
- White-label and control
- Check whether the MSP controls the deployment and can present the service under its own brand.
- Auditability and compliance
- Require a full audit trail per tenant and recognized certifications your clients will ask about, such as ISO 27001, SOC 2 Type 2, GDPR, and HIPAA-aligned controls.
When should an MSP hire vs deploy an autonomous engineer?
Deploy an autonomous engineer
- A large share of the queue is repetitive L1 to L3 work
- You want to add clients without adding technicians in lockstep
- You need per-client isolation and a full audit trail to satisfy clients
- You want cost to track resolutions rather than seats
Add or keep human headcount
- The work is genuinely architectural or judgment-heavy
- You are handling escalations that require human decision-making
- You are delivering high-touch project work that is not repeatable
- You need on-site or relationship-led service the engineer does not cover
An MSP readiness checklist for autonomous resolution
Use this checklist to assess whether your MSP is ready to deploy an autonomous IT engineer across clients.
We can identify the highest-volume, most repeatable request types per client
These are the strongest first candidates for autonomous resolution.
Our clients' core systems support delegated permissions
For example Microsoft 365, Google Workspace, or Okta, scoped per tenant.
We can define per-tenant policies for what is and is not allowed
This becomes the policy set the engine enforces for each client.
We have a plan to start with human-in-the-loop approval before widening autonomy
We know how per-resolution pricing maps to our client contracts
Dex is $1.99 per resolved ticket with a $100 free credit to start.
We have identified how the service will be presented to clients
Including whether it is offered under our own brand.
Putting it all together: from problem to platform
Placeholder — a short paragraph framing the challenge and what a modern approach looks like, before outlining where automation, AI, and a purpose-built platform each play a role.
The challenge
MSPs are stuck between growth and margin: every new client adds a stream of routine tickets that, in a queue-based model, can only be absorbed by hiring more technicians. The challenge is serving more clients and closing more tickets without letting labor cost rise in lockstep with volume, and without compromising per-client isolation or auditability.
What good looks like
- Routine and mid-tier requests are resolved end to end across every client
- Each client's data stays isolated with its own encryption
- Senior staff spend their time on escalations and higher-margin work
- Cost tracks resolutions rather than seats or technician count
Where automation helps
- Executing repeatable operations such as password resets, access, and provisioning across tenants
- Acting directly inside each client's Microsoft 365 and other connected systems
- Absorbing volume spikes without adding headcount
- Building a new SaaS integration on the fly when a client's request requires one
Where AI helps
- Investigating the root cause of an issue rather than matching keywords
- Planning and adapting a sequence of actions for a novel request
- Resolving deeper L2 and L3 work that used to require a senior technician
- Deciding when a case needs a human and escalating with full context
Where a platform fits
- Deploying multi-tenant with per-organization isolated databases and encryption
- Using delegated permissions scoped per tenant and a full audit trail
- Pricing per resolution at $1.99 per resolved ticket with a $100 free credit
- Backing it with ISO 27001/27017/27018, SOC 2 Type 2, GDPR, and HIPAA-aligned controls
Placeholder — short, direct value statement
Placeholder supporting sentence. No jargon. One clear benefit.
See how Dex works for MSPsFrequently asked questions
Common questions about this topic, answered directly.
Dex is built multi-tenant, with per-organization isolated databases and their own encryption keys, so one client's data is never accessible to another. Actions in each environment run through delegated permissions scoped to that tenant rather than a shared master key, and every action is captured in a full audit trail. That isolation is what makes it safe to serve many clients from one platform.
Because the MSP controls the deployment and employees interact with Dex inside their own client's Microsoft Teams and Slack, an MSP can present autonomous resolution as part of its own branded service. Each tenant remains isolated with its own data and encryption while being managed centrally by the MSP.
They escalate to a human with full context attached. Dex targets resolving over 90 percent of IT requests autonomously across L1 to L3, and the remaining minority, typically genuine architectural or judgment cases, routes to a technician who receives the context rather than starting from scratch.
It is priced per resolution rather than per seat. Dex is $1.99 per resolved ticket, with a $100 free credit to start and no per-seat fee. That means cost tracks the work actually completed, which makes scaling the client base more predictable than paying for seats or hiring in proportion to volume.
It resolves L1 through L3 requests end to end inside connected systems: routine work such as password and MFA issues, access requests, and onboarding provisioning, and deeper L2 and L3 troubleshooting, configuration, and admin tasks across Microsoft 365, Google Workspace, and Okta. It can also build a new integration to a SaaS platform mid-conversation when a request requires one.
Yes. Cliff DuPuy, Director of IT at Grand Traverse County, reported that "Dex helped us unlock $67K in value in a single day." Dex is built by SysAid, whose IT service management technology is trusted by more than 3,000 organizations and millions of users.
The bottom line
MSPs can cut ticket volume without adding headcount by breaking the link between the number of tickets and the number of technicians. An autonomous IT engineer deployed multi-tenant across the client base resolves L1 through L3 requests end to end, keeps each client isolated with its own encrypted data, and can be presented under the MSP's own brand. Because it is priced per resolution rather than per seat, cost tracks value delivered rather than idle capacity. Dex, built by SysAid, is $1.99 per resolved ticket with a $100 free credit, targets over 90 percent autonomous resolution, and Grand Traverse County reported unlocking $67K in value in a single day with it.
See it in action
Placeholder — one sentence describing what the viewer will see in a product walkthrough or demo session.