It's 11:40 on a Tuesday night and a client's office manager calls the support line because the shared printer won't print payroll stubs. Your on-call tech fixes it in twelve minutes from the couch. Next month the client's invoice looks exactly like last month's. Was that call included? Billable? Nobody can say, because the agreement says "after-hours support available" and nothing else, and the tech meant to write a ticket in the morning.
Yes, MSPs should charge for after-hours support. But the multiplier is the easy part. The decision that actually protects your margin is charging for two different things: the availability (someone carrying the phone all week, whether it rings or not) and the work (the calls that come in). Most MSPs price only the work, and most agreements don't say which calls count.
The short answer
- Put a defined set of emergencies inside the agreement, and price the on-call cost into the monthly fee.
- Bill everything else after hours at a multiplier with a minimum, stated in the agreement before the first call.
- Make every after-hours call end in a ticket, or you can't bill it, count it, or tell whether the client is worth the coverage.
What the common advice gets right, and what it skips
The vendor guides that rank for this question agree on the rate. IT Glue's guide says requests outside business hours "may not be included in the basic service contract and can be billed on an hourly basis," and that you "may charge 1.5 or 2 times the regular price." OnPage's guide gives the same 8-to-5 baseline and 1.5x after 5 p.m. and on weekends.
That's a reasonable starting point. What none of them gives you is a minimum, a definition of an emergency, or the cost of keeping someone on call in the first place. Those three decide whether after-hours support makes money.
Price the pager, not just the hours
The cost of after-hours coverage starts before anyone calls. Somebody has to carry the phone, stay sober enough to log in, and answer within whatever window you promised.
Most MSPs that take on-call seriously pay for that. In an r/msp thread on on-call pay, owners and techs described weekly stipends from $50 to $225, usually plus overtime for time actually worked; one said their $125 weekly rate hadn't changed in "over 15 years," and another paid "$50 per call answered" with an answering service taking first contact. Those are anecdotes from shops of unknown size, not a benchmark, but the pattern is clear: availability costs money every week of the year, quiet or not.
So run the arithmetic on your own number. As an example, a $150 weekly stipend is $7,800 a year before a single call is worked. Spread across 20 managed clients, that's about $33 per client per month just to have the phone answered. If your agreement says after-hours emergencies are included and your price doesn't carry that cost, you're paying it out of margin.
That's the case for a line in the agreement (or a higher tier) that covers availability, separate from the hourly multiplier for work. It also answers the client who asks why they pay for after-hours coverage they rarely use: they're paying for the phone being answered, the same way they pay for insurance.
Define the emergency before 2 a.m., not during
"Emergency support included" without a definition means every call is an emergency. The caller decides, at the worst possible time, and your tech isn't going to argue with a client at midnight.
Write the definition in terms the client can check before they call:
- Included emergencies: the whole office can't work (internet, email or the line-of-business app down for everyone), a server or firewall is down, or a suspected security incident.
- Billable after hours: anything affecting one user or one device, scheduled work the client asked to move to evening, and "while you're on, can you also…" requests.
- Next business day: everything else, unless the client agrees to the billable rate on the call.
Then set the rate and the minimum per work type, not one number for everything. We covered this in should MSPs bill in 15-minute increments: remote daytime work can carry a small minimum, but an after-hours callout should carry one that reflects pulling someone off their evening. In the r/msp thread, one owner paid techs 1.5x overtime "with a 1 hour minimum for ALL calls." Whatever you pick, a minimum is what stops the twelve-minute printer fix from costing more in disruption than it brings in.
The printer call from the opening fails the emergency test (one device, one user, nothing down for the office). Under this definition it's billable at the after-hours rate, or it waits until morning. Either answer is fine. "Nobody knows" isn't.
The call that never becomes a ticket
Here's the failure point the pricing guides miss entirely. You can have a perfect after-hours clause and still not bill a dime of it, because after-hours work is the work least likely to reach the PSA.
The on-call tech handles the call from their phone, maybe from a personal cell, fixes it, and plans to write it up in the morning. In the morning there are new tickets. The call never becomes a ticket or a time entry, so it doesn't show up on the invoice, the client's effective hourly rate looks better than it is, and at renewal you can't show the client the six midnight calls they made last quarter. We walked through how this inflates per-client margins in MSP profit margins, and why the phone is where time goes missing in MSP time tracking.
Three rules fix most of it:
- After-hours calls go to one number that routes to whoever is on call, not to techs' personal cells. Then the phone system has a log you can check.
- No after-hours fix without a ticket, opened during the call or before the tech goes back to bed, with the work type set to after-hours so the PSA bills it at the right rate.
- Review after-hours calls against tickets weekly. Pull the call log for the on-call line and look for calls with no matching ticket. It's tedious by hand, which is why a phone-to-PSA gap check is worth running before you rewrite any pricing.
If your SOPs don't already cover the on-call handoff, add it; it's one of the ones in MSP SOPs: write the ones that end in a ticket first.
Should after-hours support be included at all?
It depends on the client, which is why it belongs in your tiers rather than in every agreement. A dental office that closes at 5 and never works weekends doesn't need to pay for availability; give them next-business-day support and a published callout rate. A manufacturer running a second shift, or a client with staff in other time zones, needs coverage they can count on, and should pay for it in the monthly fee. MSP pricing models covers how to put after-hours in writing as an exception or a tier, whichever pricing unit you use.
The one thing to avoid is the middle: "after-hours available" on the proposal, no price, no definition. That's free 24/7 support for whichever client calls the most.
Where tooling helps
None of this needs new software to start. A routed on-call number, a work type for after-hours in your PSA, and a weekly check will get most MSPs most of the way.
If the gap is that nobody wants to answer the phone at 2 a.m. for a call that turns out to be a printer, that's where an answering layer helps. Vight's AI voice agent can answer after-hours calls on a Vight phone number, ask follow-up questions, capture the caller's details and open a ticket with the context in ConnectWise, Autotask, HaloPSA or Syncro. Its after-hours escalation agent summarizes those calls, decides whether they need someone now, and pages whoever is on call on your on-call schedule (role by role, by email, Teams, Slack, SMS or phone call) until someone acknowledges the ticket. That doesn't decide your policy, but it means the urgent call reaches a person and the printer call becomes a ticket for the morning, with a record either way.
If you want to see how that would fit your current on-call setup, book a demo.
FAQ
How much should an MSP charge for after-hours support?
Vendor guides commonly suggest 1.5x to 2x your standard hourly rate for after-hours work, with a minimum per callout. Price the on-call availability separately, from what you actually pay techs to be on call each week, divided across the clients who get the coverage.
Should after-hours support be included in a managed services agreement?
Include a defined list of emergencies (office-wide outages, server or firewall down, suspected security incidents) and price the on-call cost into the fee. Bill other after-hours requests at a stated rate, or move them to the next business day.
What counts as an after-hours emergency for an MSP?
Write it in terms the client can check before calling: something that stops the whole office or a critical system, or a possible security incident. Problems affecting one user or one device usually aren't emergencies.
Why don't MSPs bill for after-hours work they do?
Usually because the work never becomes a ticket or a time entry. On-call techs handle calls from their phones and mean to document them later. Route after-hours calls to one number and require a ticket for every call so the PSA can bill it.