The retainer does not know its cost
A support contract is a fixed number. How many hours went into it is something you find out when the client turns heavy, not before.
Tickets, SLAs and recurring contracts in the same place as quotes and invoices. Customers come in through the portal, not through your inbox.
A support contract is a fixed number. How many hours went into it is something you find out when the client turns heavy, not before.
Email, phone, a message to the technician. Half the requests never become tickets, so they do not exist at renewal time.
The job outside the contract gets done and then forgotten: nobody sends it to billing because nobody recorded it as billable.
An MSP that does not know how many hours sit inside a retainer does not have a contract: it has a bet renewed every year.
The request attaches to the customer’s contract and its terms. Hours logged on the ticket tell you whether the fee holds.
Customers open and follow their own tickets from the portal, without counting as users. Documents, quotes and job status live there.
What falls outside the fee lands in the billing queue as its own line. You confirm and issue it, instead of reconstructing it from memory.
Assignment, notifications, state changes and escalation on your own rules. The procedure lives in the system, not in whoever is on shift.
The core includes everything: these are the ones you open first.
Start on your own with the trial, or let us walk you through it.
No newsletter. We only write to set up the demo.