
The agent-run managed services back office
A managed services business runs the same back office for every client: tickets, monitoring, onboarding, licenses, billing and the quarterly report. This is the pattern for running it with governed agents, each under a named person, with every client commitment kept human.
The short answer
An agent-run managed services back office is a set of governed agents that each run one part of service delivery for every client: the service desk, network operations, onboarding, licenses, billing and client reporting.
Each works under a named person. Every client commitment, system change and invoice is approved by people.
Why does a managed services business feel busy but stuck?
A managed service provider sells the same promise to every client, and behind it runs the same back office for each: tickets to sort, alerts to watch, new users to onboard, licenses to true up, invoices to build and a quarterly report to assemble. As the client list grows, that back office grows with it, one hire at a time. Engineers end up doing coordination, account managers rebuild reports by hand, and margins shrink with every new client.
Who is this for?
The owner or operations director of a managed service provider, or the head of an internal IT group that serves several business units the same way. It suits a business that already runs its delivery through ticketing, monitoring, a billing system and written runbooks, and can name who owns each part. The department described here is a pattern built up workflow by workflow. This page describes that pattern and its roles, and claims no department already delivered or measured.
Which parts of service delivery can agents run, and who owns each?
| Part of the back office | What the agent does | Who decides | Where it starts |
|---|---|---|---|
| Service desk | Sorts tickets per client and escalates by your rules | Engineers diagnose and fix | Ticket triage across queues |
| Network operations | Coordinates alerts, timelines and shift handoffs | The operations lead and on-call engineers | The NOC coordinator role |
| Client onboarding | Chases documents and opens setup requests | The service delivery manager | Customer onboarding coordination |
| Licenses and assets | Reconciles seats and devices per client | The client's account owner | Asset and license reconciliation |
| Billing | Drafts each client's invoice from usage and contract | Finance signs off every run | Monthly client billing |
| Client reporting | Assembles the periodic service report | The account manager approves and presents it | Recurring reports |
How it works, step by step
A department is built one proven workflow at a time, under one accountable director.
Start with the workflow that costs the most
Add workflows under named owners
Keep every client's data separate
Connect the workflows through records
Human gate: people own every client commitment
Learn from every incident without blame
Prioritise security work by evidence
What stays with people in the department?
Client relationships
Account managers own every conversation and commitment.
Changes to client systems. Engineers make them, after the right approval.
Money
Finance approves every invoice and every credit.
What the department takes on
The operations director adds workflows one at a time.
Accountability. Each workflow has one named owner, and the record shows who decided what.
Where this fits
A department of several AI Employees working together is the scope of Tier 3, AI Department, and it is reached only after individual workflows have run well. The same pattern for a general operations team is the agent-run operations back office, and the billing workflow already exists as monthly client billing on autopilot. The readiness checklist is the place to choose the first workflow, and the use case library holds each one in detail.
How does a department differ from a set of separate workflows?
| Question | Separate workflows | An agent-run department |
|---|---|---|
| Who is accountable | Each workflow's owner | Each owner, plus one director for the whole |
| How they connect | Through people passing information | Through shared records |
| How it grows | Ad hoc | One proven workflow at a time, by plan |
| What the client sees | Uneven service | The same disciplined service, approved by people |
Related reading
- The agent-run operations back office: the same department pattern for general operations.
- Monthly client billing on autopilot: one of the department's workflows, already described in full.
- Customer onboarding coordination: how a new client gets set up.
