Verity for IT services
An IT services business sells response commitments and delivers them with shared engineers. Verity connects the contract, the ticket, the asset and the person, so an SLA breach is predictable rather than reported.
Verity runs the services business. Your monitoring and toolset stay where they are.
Verity / Service desk
LiveOpen tickets
142
At SLA risk
11
Out of contract
23
Engineer coverage
3 accounts
Needs attention
Illustrative figures. Verity shows your own service desk in this shape.
How the business runs
A managed services business makes a commitment per account — response within a defined time, a scope of covered work, an agreed number of hours or devices — and then delivers all of those commitments from one team of engineers who are shared across every account. The tension between contracted commitments and shared capacity is the entire operational problem.
The commitment is measurable, which makes IT services unusual among professional businesses: an SLA either was or was not met, per ticket. What is usually not measurable is why. A breach happens because the engineer who knows that client’s environment was at another site, or because a ticket was misrouted, or because nobody escalated. Those causes are recorded nowhere, so the same breach repeats.
The second characteristic loss is out-of-scope work. Clients ask for things outside the contract, engineers do them because refusing is awkward and the request is small, and the effort is never billed. Twenty-three tickets a month outside contracted scope is a meaningful sum in a business with thin service margins, and most providers can only estimate it.
The third is key-person dependency. Three accounts depending on one engineer is a commercial risk that is entirely invisible until that person takes leave or resigns, because environment knowledge lives in their head rather than in documentation attached to the account.
Verity holds the contract, the ticket, the SLA clock, the asset, the engineer and the billing position as one set of records.
What Verity calls these things
What gets in the way
IT services difficulties come from contracts that are specific and capacity that is not.
SLA breaches are reported, not predicted
The monthly report says how many were missed. Nothing said which were about to be missed while there was still time to act.
In Verity The SLA clock runs on the ticket against the account’s contract, so tickets approaching breach surface with time remaining.
Out-of-scope work is done and never billed
A client asks for something outside the contract, an engineer obliges, and the effort disappears into the service margin.
In Verity Tickets are checked against contracted scope, so out-of-scope work is flagged as billable or as a recorded decision to absorb it.
Key-person dependency is invisible
Certain accounts only run because one engineer knows the environment, and this is discovered when they are unavailable.
In Verity Ticket ownership by account and engineer is recorded, so concentration surfaces as a measured risk with documentation gaps named.
Breach causes are never recorded
A missed SLA is counted but its cause — misrouting, availability, waiting on the client, waiting on a vendor — is not, so the same breach recurs.
In Verity Cause is recorded at resolution, so recurring causes become a list rather than a monthly number.
Client assets fall out of support unnoticed
Devices go out of warranty and licences lapse, and it becomes visible when something fails and cannot be replaced.
In Verity Client assets are records with warranty and licence dates, so renewals are raised ahead of expiry.
Account profitability is unknown
A fixed monthly fee against unmeasured effort means some accounts are subsidised by others and nobody can say which.
In Verity Effort recorded against the account produces cost against contracted fee, so loss-making accounts are identified.
The complete system
One system across contracts, tickets, engineers, assets and billing.
Work
Every ticket is work with an account, a category, a priority, an owner, an SLA clock, recorded effort and a resolution with a cause.
Why it matters here The ticket is where the contractual commitment, the engineer’s time and the client’s experience all meet.
In practice Eleven tickets within two hours of breach, four of them needing the same engineer.
Records
Each account carries its contract terms, response and resolution targets, covered scope, included hours and renewal dates.
Why it matters here Scope is what separates billable work from absorbed work, and it has to be checkable at the moment a ticket is logged.
In practice Twenty-three tickets outside contracted scope this month, quantified as effort.
People
The team is modelled once with skills, account familiarity, availability and on-call assignment, and every ticket shows who owns it.
Why it matters here Delivery capacity is shared across accounts with specific commitments, and matching the two is the daily job.
In practice Three accounts with a single-engineer dependency, surfaced with the documentation gaps named.
Inventory
Client assets are records with their site, configuration, warranty and licence dates, and the tickets raised against them.
Why it matters here An asset’s ticket history is the difference between another repair and a replacement recommendation.
In practice Forty-six devices out of warranty with no renewal raised, alongside the tickets they have generated.
Relationships
Clients are records with their contracts, sites, users, ticket history, escalations, satisfaction and balances.
Why it matters here Renewal decisions are made on service experience, and the evidence for that experience is the ticket history.
In practice An account approaching renewal with its breach history and escalation record in one view.
Workflows
Escalation tiers, change approvals, out-of-scope authorisation and after-hours work move through defined steps with recorded decisions.
Why it matters here Escalation that depends on someone deciding to escalate is escalation that happens too late.
In practice A ticket approaching breach escalates automatically to the tier that can resolve it.
Reports and analytics
SLA attainment and breach causes, out-of-scope effort, account cost against fee, asset lifecycle and engineer load come from the operational records.
Why it matters here Providers report SLA attainment to clients and rarely report account profitability to themselves.
In practice Cost against contracted fee per account, which usually identifies two or three that should be repriced.
Verity AI
Verity AI answers from your own ticket, contract, asset and engineer records, respects permissions, and can create assigned follow-ups.
Why it matters here The useful questions cross contract, capacity and history at once, which is exactly what a ticket queue view cannot do.
In practice "Which tickets are at SLA risk and who can actually resolve them?" returns eleven with reassignments proposed.
Communication
Notes, updates and activity attach to the ticket, asset or account they concern.
Why it matters here Most client dissatisfaction in managed services is about not being updated rather than about resolution time.
In practice An update recorded on the ticket, so the next engineer and the client see the same history.
Control
One permission model and one audit trail across every record, with change approvals recorded.
Why it matters here A services provider holds administrative access to client environments, which makes attribution a professional obligation.
In practice Every change carries the approver, the engineer and the time.
Locations
Client sites and internal regions are locations, with tickets, assets and reporting following the same structure.
Why it matters here On-site work has travel time and coverage constraints that only appear if sites are modelled.
In practice Engineer coverage by region against the accounts committed there.
Work in motion
These already run. As records with contract terms attached, the commitment becomes manageable rather than reportable.
Checking scope at intake is what turns absorbed work into either billable work or a deliberate decision.
The difference between predicting a breach and reporting one is roughly two hours, which is usually enough.
Making absorption a recorded decision is what stops it being the default.
An asset with a ticket history is a replacement conversation with evidence rather than an upsell.
Renewal is the only moment a mispriced account can be fixed, and it needs the effort data to be a conversation.
This is a commercial risk that is invisible until it is a crisis, and entirely measurable before then.
Verity AI
Verity AI reads the same ticket, contract, asset and engineer records the desk runs on. It answers from your own accounts, respects permissions, and can turn an answer into reassignments and escalations.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the ticket and contract records at the point the condition is met.
When
A ticket approaches its SLA target
When
A request falls outside contracted scope
When
An asset approaches warranty or licence expiry
When
Ticket ownership concentrates on one engineer
When
Effort on an account exceeds its contracted fee
When
A change is requested on a client environment
What you can understand
Commitment attainment and account economics from the same records.
Verity holds the service and commercial records. Monitoring, remote management and security tooling continue to do their own jobs.
One system, different ways of seeing it
Everyone works from the same records, and each role opens on what they need.
Services director
Which accounts are we losing money on?
Effort against contracted fee, out-of-scope leakage, SLA attainment, renewal risk.
Service desk manager
What is about to breach?
Tickets at SLA risk, engineer availability, escalations open, reassignments needed.
Engineer
What is mine and what is urgent?
Assigned tickets by SLA remaining, asset history, change approvals, updates due.
Account manager
How is my client actually being served?
SLA history, escalations, out-of-scope work, asset lifecycle, renewal position.
Accounts
What is billable and what is owed?
Billable out-of-scope effort, contract invoicing, balances ageing, absorption recorded.
Where it is used
The clock running on the ticket against the account’s contract, so tickets approaching breach surface with time remaining rather than in a monthly report.
Tickets checked against contracted scope at intake, so out-of-scope work becomes billable or a recorded decision to absorb it.
Cause recorded at resolution, so recurring failures become an addressable list rather than a monthly count.
Ticket ownership concentration by account, exposing a commercial risk that is otherwise invisible until someone resigns.
Effort at cost against contracted fee, identifying the accounts subsidised by the rest before renewal rather than after.
Assets with warranty, licence dates and ticket history, so renewal and replacement conversations carry evidence.
Escalation triggered by the clock rather than by someone deciding to escalate, which is usually too late.
Plain-language questions across contracts, tickets, capacity and assets, with reassignments raised in the same step.
Getting there
Your monitoring, remote management and security tooling continue to run and are mapped during implementation. Accounts, contracts, SLAs, client assets and open tickets are brought across, and Verity is introduced as the service and commercial layer over them.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own ticket, contract, asset and engineer records: which tickets are at SLA risk and who can actually resolve them, how much out-of-scope work was done and for which accounts, which accounts depend on a single engineer, which cost more to serve than their fee. Each answer can become a reassignment or an escalation.
No. Those continue to do their own jobs and are mapped during implementation. Verity is the service and commercial layer — contracts, tickets and SLAs, engineer allocation, client assets, scope control, account economics and reporting.
The clock runs on the ticket against the account’s contracted targets, so tickets approaching breach surface with time remaining and escalate automatically. Cause is recorded at resolution, so recurring failures become addressable.
Scope is checked at intake against the contract, so a request outside it is flagged with estimated effort and raised for authorisation. The work becomes billable, or absorbing it becomes a recorded decision rather than the default.
Effort recorded against tickets is costed and compared with the contracted fee per account, which usually identifies two or three accounts being subsidised by the rest — in time to reprice them at renewal.
Client devices and licences are records with their site, configuration, warranty and licence dates and their ticket history, so renewals are raised ahead of expiry and replacement recommendations carry evidence.
Ticket ownership concentration is measured by account and engineer, so accounts running on one person’s knowledge are identified with their documentation gaps named, rather than discovered when that person is unavailable.
Verity has one permission model and one audit trail, and changes to client environments move through recorded approval steps with the engineer, approver and time attached.
About four weeks: discovery and mapping of contracts, SLAs and the service desk, configuration, migration of accounts, assets and open tickets, then an ongoing operations partnership.
One is margin you are giving away and the other is the renewal conversation you will have next year. Tell us which matters more right now.