You close the laptop at the end of the day because your regular shift is over. Maybe your manager even tells you to clock out, go home, and enjoy your night.
Then comes the catch, if something breaks after hours, you may still need to answer.
For many Managed Service Provider (MSP) technicians, after-hours IT support lives in that uncomfortable middle ground. You are technically off work, but not fully free from work. You can try to relax, but you are expected to be on the lookout for the alert that could interrupt the night.
That kind of waiting can wear on you, even during weeks when nothing happens.
In this blog, we’ll help you identify better language for what you are experiencing so you can start a clearer, more useful conversation about after-hours expectations.
After-hours IT support becomes harder to discuss when expectations are not clearly defined.
One helpful way to think about this is the difference between waiting to be engaged and being engaged to wait.
This can become a technical or legal distinction depending on where you live and how your role is classified, so this article is not legal advice. But as a practical framework, it can help explain why some on-call arrangements feel reasonable while others start to feel like you are still working.
Waiting to be engaged means your personal time is still mostly yours. You may be contacted if something urgent arises, but you can generally go about your life. You might step away from your desk as long as you can respond within the agreed window.
Engaged to wait is different. This is closer to being on duty while waiting. It is more common in roles where someone needs to be ready almost immediately, such as doctors, nurses, firefighters, or other emergency-response roles. They may not be actively handling an emergency every minute, but their time is controlled enough that they are effectively there to work if needed.
The problem starts when an MSP says the arrangement is closer to waiting to be engaged, but manages it like being engaged to wait.
A technician may be told, “You’re only on call if something urgent comes in.” But then the expectation becomes: answer immediately, acknowledge the alert within minutes, stay close to your laptop, respond to Slack right away, and explain yourself if you were not instantly available.
Managers can accidentally cross the line this way.
The written policy may suggest one kind of on-call arrangement, while the day-to-day behavior creates another. Even if it wasn't intended to make the policy unfair, the technician still feels the effect. Their evening starts to revolve around staying ready, because they know any delay may be questioned.
That mismatch creates stress. It also creates confusion around response times, compensation, escalation paths, and what “available” means.
Clear definitions matter because technicians should know what kind of waiting is being asked of them. Are you simply reachable if something comes up, or are you expected to behave like you are actively on duty?
Those are different experiences, and they should not be managed as if they are the same.
A quiet on-call week can be hard to explain.
When nothing major happened, no huge outage came in, or the phone barely rang (or not rang at all). From the outside, it can look like you had a normal week.
But if you were the person carrying the after-hours responsibility, it may not have felt normal. That is because being on call changes the way you rest.
Even when you are not actively working, part of your attention is still reserved for the possibility of work. This translates to needing to stay close to your laptop and avoiding plans that would be hard to interrupt. You may try to relax, but your brain is still listening for the alert that could pull you back in.
It is completely normal for that to feel like incomplete rest, especially when you take the responsibility seriously.
Most technicians care about their clients, their team, and the person who may be stuck dealing with an urgent issue after hours. That sense of responsibility is part of what makes you good at the job. It is also what can make it harder to notice when on-call work is taking more from you than you realized.
If you are starting to feel like you never fully clock out, that is worth paying attention to.
When on-call work starts to feel unfair, it is easy to assume your manager understands what it feels like and is choosing not to care.
Sometimes, the reality is more complicated.
After-hours support is not automatically a bad thing. MSPs do need a way to respond when urgent issues happen outside business hours. Clients have outages, and security risks show up at bad times. Business-critical systems do not always break politely between 8:00 and 5:00.
It’s totally normal to see this conversation as difficult. The business need is real, and so is the human cost.
Managers are watching ticket volume, SLA misses, escalations, or whether a major outage was handled quickly enough. Real concerns. But they do not show the strain of being the person carrying the phone.
This gap can get even wider in smaller or founder-led MSPs, where after-hours coverage often starts informally. Maybe the owner used to be the backup for everything. Maybe a senior technician became the person everyone texted when something broke. Maybe the team got used to handling urgent work through trust, loyalty, and the shared idea that everyone pitches in.
That can work for a while.
As the MSP grows, informal systems can become unclear or uneven. The same person may keep becoming the real escalation point. Newer technicians may feel pressure to prove themselves by always being available. The person with the most knowledge may feel like they can never fully step away.
Most of the time, this happens because the business is still using habits that made sense when the team was smaller. So, the conversation usually works better when you connect your experience to business risk.
Instead of only saying, “This is burning me out,” it can help to bring clearer observations:
Those questions make the conversation easier for a manager to engage with. They turn the issue from a vague feeling into something the business can examine.
If you are constantly planning your personal life around the possibility of a ticket, feeling like your time off never fully resets you, or carrying stress from one rotation into the next, it may be time to start a better conversation.
Empath Head of MSP Success Dean Trempelas covers this topic more deeply in an episode of Managing Up, a monthly Empath-exclusive livestream for operations managers, coordinators, dispatchers, and the people behind the scenes who want to better navigate workplace conversations and grow their influence inside the MSP.
In this specific session, Dean is joined by centrexIT Cybersecurity and Automation Manager Josh Hohbein to talk through the reality of on-call work from both the technician and manager perspective.
Dean also walks through the Holiday Risk Matrix Worksheet, a workbook designed to support better PTO planning and fairer rotations.
The recording of this session is available inside Empath, a learning and accountability platform built specifically for MSPs. You can access it with a 14-day free trial.
Subscribe to our newsletter 👇🏻