SLA tracking usually means a spreadsheet someone updates after the fact, discovered to be wrong the month a client disputes an invoice. TaskForge ties SLA quotas directly to the job cards being worked - separate monthly remote and onsite hour allowances per client, only for the work types you've actually agreed to cover, checked automatically as work happens.
Most SLA contracts don't treat remote and onsite support the same way, and neither does TaskForge. Set a monthly quota for each, choose exactly which work types actually count against the contract, and every job card worked against that client draws down the right bucket automatically - no manual reconciliation at month end.
The moment a client is about to exceed their contracted hours, it flags before the work goes out the door - not after the invoice lands and the client questions it. That single change turns SLA compliance from a monthly audit exercise into something that's simply always up to date, because it's built from the same job cards your technicians are already logging.
Separate monthly remote and onsite hour quotas per client, with only the work types you choose actually covered.
A real client hierarchy - each client's own sites and locations, with SLA terms attached at the right level.
COD or 30-day terms per client, with an overdue account flagged automatically before new work proceeds.
A custom report builder with exports, beyond the standard dashboard views.
A rollup view across every site and technician - the numbers leadership actually wants to see.
SLA contracts and other client documents stored with automatic expiry warnings.