XOP Command
One measurement. Four ways to look at it.
AI analysis on every service ticket feeds intelligent insights you can run your business on.
Where it comes from
Nobody fills in a form. Nobody answers a survey.
The measurement is a by-product of Assist-X being in the ticket while the work happens. Sentiment, clarity, empathy, cadence, response quality, escalation risk, captured because an engineer used the tool that saves them time, not because anyone was asked to report.
Which account is quietly unhappy right now? You find out at renewal, or you find out today.
Escalations
The account you were going to lose quietly.
“27 days without follow-up after promised resolution. Support commitment not honored, ‘early next week’.”
An escalation, scored 9.5 out of 10.
That is not a sentiment reading. It is a specific, checkable fact about a promise that was made and then missed, on a ticket nobody had flagged. Most MSPs meet that fact for the first time in a renewal conversation.
Every escalation arrives with its reasons in plain language, and a link straight into the ticket. Your service desk decides what to do; the system’s job is to make sure the decision gets made while it still matters.
Three ways onto the board
Raised by the machine
Every ticket is read and scored out of ten, continuously, whether or not anyone suspected there was a problem. Sixteen days without a response on a multi-user event does not need reporting by the person who let it happen.
Raised by a person
An engineer escalates from inside the ticket and says why, in a sentence, in their own words. The ticket status changes to escalated in your PSA, so the escalation is a fact about the ticket rather than a note in another system.
SLA violations in your PSA
Your PSA already tracks response and resolution targets against the agreement you sold. A breach is not a judgment call, so those tickets arrive on the board on their own, without anybody having to go looking for them.
Your rules, not ours
You decide what counts as urgent here.
A managed services business that lives on SLA attainment and one that lives on executive relationships do not want the same tickets raised. So the weights are yours to move, and the whole queue is re-scored against them.
- Disruption Score
- Priority
- Age
- Cadence
- Follow-up
- Acumen
- Skills
- Chronic
- Recurring issue
- Clarity
- VIP User
Turn cadence up and follow-through failures rise to the top. Turn disruption up and the CEO who cannot print their tax return outranks a server alert nobody noticed. Change them and re-analyze, and the tickets that matter change with them.
Client Health
It is not a dashboard. It is a briefing.
Building these views by hand is a project: somebody designs the metrics, somebody maintains the connections, and somebody still has to turn the numbers into something worth saying out loud. This arrives already built and refreshes every day off live data.
It is written for the person who is not close to the account. Today they are briefed by whoever owns the relationship, filtered, and only what that person chose to raise, or they walk into the review and improvise.
Workload and utilization
What was done, how much effort it took, and how much of the agreement was used. No rates and no financial data: you hold those.
Sentiment and response quality
How the account actually feels, across every interaction rather than the two people who answered a survey.
Training needs
The skill gaps behind recurring tickets, with an estimate of what closing them would remove from the queue.
Technical debt and lifecycle
Ageing infrastructure surfaced from your asset data through ScalePad Lifecycle Manager, not guessed from ticket text.
Expanded engagement
Projects worth proposing, each with the signals behind it and a confidence score.
The opportunities are not an appendix. They are the agenda for the renewal conversation.
A firewall that went end-of-life over a decade ago, on an account whose main contact holds the budget. An invoice that reached the service desk instead of accounting. Each one arrives with the reasoning attached, and writes back to ConnectWise as a ticket assigned to an account manager, so it lands in someone’s queue rather than dying in a report.
Engineer Coaching
Throughput is not performance.
Your PSA already reports tickets closed, hours billed and utilization. None of it tells you whether the customer was handled well. Throughput tells you who is busy. It does not tell you who is good.
Follow-through, cadence and empathy cannot be scored from a ticket count. Scoring them means being present in the interaction, which is what Assist-X already is. A manager spot-checks a handful of tickets a month; this reads all of them.
Engineers are your largest cost of revenue and your most important asset. Coaching is the only lever that improves that asset rather than replacing it, and the reason good engineers leave is rarely money alone.
Scored on the work, not on a form
Technical acumen alongside clarity, cadence, empathy and customer satisfaction.
Skills rated from real tickets
Twenty technical competencies, drawn from what an engineer has actually resolved.
Ranked development priorities
Three things worth working on, in order, with the tickets behind them.
A 1:1 that goes somewhere
Notes and due dates attached to the conversation, so coaching does not evaporate the moment the meeting ends.
It scores the ticket, and coaches the person. The measurement is of the interaction, which is what makes the conversation specific rather than personal: not “you need to communicate better”, but “response cadence is the gap, and here are the three tickets”.
Scheduler
Most tools fill a ticket. This one can fill a day.
Dispatch normally runs one way: look at a ticket, find someone to take it. That works, and Scheduler does it. But a dispatcher does not experience the job as a queue of tickets, they experience it as a set of people whose days need filling.
So it runs the other way too. Open an engineer’s empty Tuesday, click the start of the day, and it fills with the work that best fits that person. Above a confidence threshold you set, it can assign without being asked at all.
Filling a day is the utilization number, and utilization is margin. This is not an ops convenience.
What the match is scored on
Technical skills
Rated from tickets they actually resolved, not from a spreadsheet somebody maintained once.
Availability
What is genuinely free, against the day already committed.
Client familiarity
Who knows this account, and will not spend the first twenty minutes catching up.
Workload
So the same three people do not absorb everything.
Skills come from Engineer Coaching, which rated them from resolved tickets. The measurement does not just get reported, it decides who does the work.
Rev Ops
The view is comingThe capability already runs. The dashboard is what is missing.
Assist-X already does both halves of this inside the ticket today. It checks every request against that client’s agreement and flags work you are about to give away, and it spots the unsupported platform or the project worth quoting and writes it back to your PSA for an account manager.
What Rev Ops adds is the fifth view: all of it in one place, by client, so leakage and opportunity are numbers you manage rather than events you happen to catch.
Working in Assist-X now
- Requests checked against the agreement in real time
- Possible excluded service flagged with the reason
- What the client actually bought, visible to the engineer
- Opportunities written back to the PSA, assigned to a person
Marked honestly rather than listed as shipped. Everything above is in Assist-X today; only the aggregate view is not.
What it means to each of you
Four people read this console, looking for four different things.
The owner, and leadership
Which account is quietly unhappy right now?
You find out at renewal, or you find out today. Surveys come back from a few percent, mostly the furious and the delighted. Quarterly reviews are filtered by whoever owns the account. The cancellation call is the first completely honest one, and by then the decision has been made. Every ticket your team works is already saying how that account feels.
It also arrives already built. Nobody on your team designs the metrics, maintains the connections, or turns the numbers into something worth saying out loud before a client meeting.
The service manager
The tickets that matter, by your definition of matter.
Escalations arrive risk-scored with the reasons in plain language, from three directions: the machine reading every ticket continuously, an engineer raising one from inside the ticket, and the SLA breaches your PSA already tracks.
And the weighting is yours. A business that lives on SLA attainment and one that lives on executive relationships do not want the same tickets raised, so you move the weights and the whole queue re-scores against them.
Your engineers
Coached on the work, not on the ticket count.
Throughput tells you who is busy. It does not tell you who is good. Follow-through, cadence and empathy are scored from real interactions, and twenty technical skills are rated from tickets an engineer actually resolved.
The measurement then does something rather than getting reported: those same skills decide who gets dispatched, which is how a development priority turns into different work instead of a line in a review.
Your clients
The promise nobody was tracking gets kept.
Twenty-seven days without follow-up after a promised resolution is the kind of fact most providers meet for the first time in a renewal conversation. Here it surfaces while it can still be fixed.
The opportunities are the other half. The firewall that went end-of-life a decade ago, the project worth quoting, the skill gap behind a recurring fault, each with the evidence attached, which turns a renewal meeting into an agenda rather than a defense.
What it costs
$500
a month, five manager licenses included.
Command is priced flat rather than per engineer, because it is read by your managers and owners, not by your desk. Five licenses cover most MSPs’ leadership outright.
It is a separate line from the agents, and it needs Assist-X underneath it, because the measurement is a by-product of engineers using something that saves them time. There is no version of this that works without adoption.
Bring it to your next review.
The quickest way to judge Command is to open it on an account you already know well, and see whether it tells you something you did not.