Most MSP tools are a ticketing system with a few extras bolted on. TaskForge is built around the actual chain of work an MSP runs every day — from the moment a client raises an issue through to the invoice that closes it out.
Every one of those steps lives in the same system, using the same record. Nothing gets re-typed between tools, and nothing falls through the cracks between them.
A ticket comes in against a specific client and site. It's assigned to a technician, who can pull the client's asset history, connect to their systems over RMM, and see what's already in stock before heading out. Labour, travel, and parts used on the job roll up automatically into an invoice the moment it's signed off. If that client has an SLA with separate remote and onsite quotas, the job is checked against it before billing — not after.
That's the actual day-to-day of running an MSP, and it's the reason TaskForge exists as one platform instead of five disconnected tools. Here's how every other part of the platform ties into that same chain.
A client isn't a flat entry — it's a real hierarchy. Each client can have several sites and locations underneath them, each with their own address. That address is what feeds the Client Map: every site with a valid address is plotted automatically, so you can see your whole coverage area at a glance. Billing terms, SLA hours, and compliance documents are all set per client too, not globally.
The Sales Pipeline tracks a prospect — company name, contact details, an estimated value — through stages from first contact to won or lost. The moment a lead is marked won, converting it creates a real client record directly, with the contact details already filled in. The original lead stays on record as a history of where that client came from.
RMM Agents installed on a client's machines report their status back continuously. From inside a job card, a technician can look up a device by the username on the ticket and connect remotely in one click — no separate RMM console, no re-typing an IP address. The same underlying connection also powers uptime monitoring: if a critical system goes down, a job card is created automatically and an alert goes out immediately.
Every technician is a real account in the system, not just a name on a job card. Leave requests and expense claims both link back to that account, and both follow the same simple pattern: a technician submits, a manager approves or rejects, and the record stays visible either way.
Software licences, asset warranties, and compliance documents (SLA contracts, tax clearance certificates, and similar) are all tracked with their own expiry dates. The main dashboard shows a live count of anything expiring soon across all three, so nothing lapses silently in the background.
A real client hierarchy — each client's own sites and locations live underneath them, not a flat list mixed in with your own offices.
Look up any device by username right from the ticket and connect in one click.
Separate monthly remote and onsite hour quotas per client, with only the work types you choose actually covered — go over, and it flags it before you bill outside the contract.
Set COD or 30-day terms per client — an overdue or COD-outstanding account flags automatically before new work proceeds.
Labour hours, travel, and parts used all roll up automatically into an invoice the moment a job card is signed off.
A rollup view across every site and technician — the numbers leadership actually wants to see.