Managed services give IT providers a workable alternative to selling consultants by the day. Instead of placing people on a client site, the provider pools specialists around a technology or an industry and delivers against an agreed scope. Both sides gain. Clients pay less, because the cost of a specialist is shared across several accounts rather than carried by one. Providers respond faster and protect their margins, because the same people cover more ground.That only holds if the tooling is right. A managed services team running on shared mailboxes and spreadsheets loses the efficiency the model was supposed to create. Six tools make the difference.
1.A ticketing tool
A ticketing tool lets you model how work actually moves through delivery, so that you can see:
- incidents
- user requests
- changes
- releases
- problems
It brings order to processes that involve people rather than machines — your own teams, subcontractors, partners, sometimes the client directly. Every request a provider receives lands in one place, and the steps around it (approvals, intake, assignment) stop being improvised.
Combodo’s take
A good ticketing tool handles as many processes as you need and adapts to how your team actually works, not the other way round. Tools built for service providers earn their place here. iTop, for instance, gives administrators the full back office while clients get a clean front office showing only what concerns them.
2.A self-service portal
A self-service portal lets employees and clients raise their own requests without an engineer in the middle. In practice it becomes the shop window of the service; the place where clients experience what they are paying for. It also takes pressure off a team that is permanently asked to do more with less and to be available at all hours. Costs come down, and client satisfaction tends to go up at the same time.
Combodo’s take
The portal is the interface between you and your client, so it has to be readable by anyone. Not every client is comfortable with software, and none of them should be looking at a complex back end. They should see what concerns them and nothing else. A responsive web app that works on any device is the right answer: simple, flexible, and quick to use. iTop supports several portal types from the same system : client portal, partner or subcontractor portal, a portal for technical teams or hosting providers.
3.A CMDB as the shared source of truth
A configuration management database (CMDB) holds the components of an IT system and, more importantly, how they relate to each other. It is where everyone goes to understand the infrastructure behind the services being delivered.
Those relationships are what separate a CMDB from an inventory. Knowing you own four hundred servers tells you very little. Knowing which application depends on which server, and which client contract depends on that application, tells you what happens when one of them fails.
For a managed services team that means a real-time view of dependencies, and the ability to judge the impact of any event on the services you have committed to.
Combodo’s take
Look for something configurable that survives contact with time. Some systems have to be reconfigured after every version upgrade, which quietly destroys your margin. With iTop, the customisations you build stay valid through updates.
The CMDB is also wired into ticketing, which is where it earns its keep. The impact analysis engine takes an incident on one component and works out what else is affected : which other components, which services, which applications, which contracts. You can tell clients before they notice. Nobody spends an afternoon working out the consequences of an incident, because they are already on screen.
4.A knowledge base
A knowledge base that is properly built, genuinely shared and actually used lets end users solve more of their own problems. FAQs and how-to guides document the procedures that otherwise live in someone’s head which matters when the same incident keeps coming back as a problem, or when turnover means the person who knew the answer has left.
Combodo’s take
Link the knowledge base to the CMDB, as iTop allows. Documentation then attaches to the components it describes rather than sitting in a separate wiki nobody opens.
5.Automation
Automating routine work is no longer optional if you want to cut execution time, improve return on investment and keep costs down. The pattern is always the same: a type of event triggers a defined response.
- approval rules applied automatically
- tickets routed to the right team on arrival
- notifications when a contract comes up for renewal or a licence expires
- alarms on resolution time, so SLA commitments are met rather than discovered late
Combodo’s take
Choose a system that arrives pre-wired and stays configurable, one that ships with a set of defaults drawn from how the work is actually done, so you are adjusting automations rather than building them from nothing.
6.Tools that talk to each other
None of the above is worth much in isolation. Your service management tool needs to interface with the CRM, the company directory, a BI platform, whatever else the business runs on.
Favour solutions built to connect. And if exchanging tickets between two different systems is straightforward rather than a project in itself, that is worth paying attention to.
One last thing
No two service providers work the same way, and each deserves a delivery platform shaped around how it actually operates rather than a generic one it has to work around. iTop lets providers build their own service management solution, matched to their service catalogue and their way of running it.
