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 once the client has already turned heavy.
Tickets, SLAs and recurring contracts in the same place as quotes and invoices. Customers open and follow their requests from the portal.
A support contract is a fixed number. How many hours went into it is something you find out once the client has already turned heavy.
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. At month end you confirm it and issue it along with the fee.
Assignment, notifications, state changes and escalation on your own rules. Even someone on their first shift follows the procedure.
They are all in the core. These are the ones a company like yours opens first.
You can open a trial workspace on your own, or write to us and we will show it to you starting from the problem you have.
No newsletter. We only write to set up the demo.