After-hours calls for a small MSP: triage without waking everyone

What does a 9:40pm call actually need?

It's 9:40 on a Thursday night. The owner of a twelve-person accounting office is still at her desk, the VPN has dropped, and she rings the number on your contract. There are four of you at the MSP. One is on call this week and went to bed early, because he was up at five for a server migration. What should happen to that call?

Our answer: it gets answered by something that can hold a conversation, it's asked a short fixed set of questions, and it's sorted by the client's own words into "call back tonight" or "written up for 8am". Nobody should be woken just to find out which it is. And nobody at the client's end should be left talking to a beep, because a voicemail that says "it's all broken, call me" tells you nothing about severity.

Which words mean urgent?

You can't diagnose from a phone call at night, and whatever answers your line shouldn't try. But severity shows up in how people describe the problem. Listen for scope and for stoppage.

• Everyone, or just me? "Nobody can log in" and "I can't log in" are different nights. Ask how many people are affected, and whether it's one site or several.
• Has work stopped? A warehouse that can't print shipping labels at 6am has stopped. A partner who can't open one spreadsheet at 11pm is annoyed.
• Security words. "I clicked something." "There's a message asking for payment." "My mouse is moving by itself." "The files all have strange names." Urgent, even when it's one person on one laptop.
• Physical words. A burning smell, beeping from the server closet, water, a power outage.
• Is there a workaround? If she can tether to her phone and carry on, that goes in the notes. It changes the priority.

What should the first ninety seconds collect?

The same things your best tech asks without thinking. Company and site. The caller's name and a direct number, not the main office line (which may be the thing that's down). What's wrong, in their words, written exactly. When it started, and whether anything changed just before: a new device, a password reset, an update, a storm. Who's affected. Any deadline, like payroll going out at nine.

Then the question people forget: what have you already tried? Not to coach them, only to record it. "I restarted the router twice" saves your tech ten minutes in the morning.

We'd tell the line in plain words not to troubleshoot. No "have you tried turning it off and on". It isn't a technician. It takes the details and passes them on. A wrong suggestion at midnight, followed carefully by a worried office manager, can make your morning much worse.

Who checks the contract?

A human. Always.

Some clients pay for after-hours cover, some pay per incident, and some have business-hours support only and have forgotten that. It's tempting to have whatever answers the phone look it up and tell the caller where they stand. Don't. Entitlement is a billing conversation with history behind it (the client you let off twice last year, the renewal that's half agreed), and getting it wrong in either direction costs you. Tell someone they're not covered while their server is encrypting itself and you've lost the account.

So the line writes down the company and the problem, and says what's true: the details reach the team in writing as soon as the call ends and a technician will call back tonight, or it's written up for first thing in the morning. Whether tonight is billable is for you to decide when you read the note.

Which calls get a callback tonight?

Write the rule down before you need it. Ours would be short. It's a tonight call when a whole site is down, when work has stopped and there's a deadline before morning, when the caller uses any security or physical words, or when the caller is on your short list of people who never wait until morning. Everything else becomes a written ticket.

Now the limit, and we'd rather you heard it from us. A CosVoice line can't put a caller through to anyone. It doesn't transfer, and it doesn't ring your on-call tech while the client waits. On an urgent call it answers at once, takes the details that matter, and tells the caller honestly that a technician will call them back. The written summary reaches you as soon as the call ends.

That's a callback, not a live transfer, so on the nights you promise cover, somebody has to be watching for those summaries. If your contracts promise a live hand-off to an on-call engineer, you need something else for that part.

You can mark contacts as approved or VIP, so your biggest client's operations lead is recognized when she calls. She's treated warmly, given time, and told you'll see this right away. She still gets a callback, the same as everyone. There's a starting brief to adapt on our professional services page.

What happens to the calls that can wait?

They become notes. Each call ends with a written summary: who called, from which company, what's down, who's affected, what they tried, the deadline, and what they were told would happen next. There's a morning email too, at the hour you pick, covering what came in overnight. Quiet nights send nothing.

That changes the first half hour of the day. Instead of three voicemails to replay and a client who has already emailed twice, the early tech reads a list and opens tickets in whatever system you use. (The line doesn't open them for you. It gives you the words.)

If you'd rather leave your main number alone, forward only the calls nobody answers. The codes are in conditional call forwarding, explained.

What should it never say?

Three things. A time to fix, because "someone will have that sorted within the hour" is a promise you didn't make. A cause, because "sounds like your router" is a guess. And anything at all about another client.

The line should never take a card number either, and ours doesn't. It will say it's an AI if the caller asks. At midnight most people take that better than you'd think. They wanted to be heard and written down, and they were.

How do you know the rules are right?

You read a week of them. Every Monday, pull up the after-hours summaries and ask two questions. Did anything get a tonight callback that could have waited? Did anything wait that shouldn't have? The first kind costs your tech sleep. The second costs you a client, slowly.

Then change one line of the instructions, not five. Add the phrase the client actually used. Move the payroll client onto the never-waits list for the last week of the month. After a couple of months the rules stop being a template and start being yours, which is the only version that works.

Common questions

More on professional services

• How a small agency should answer its phone
• A phone line for independent consultants
• Should a freelancer have a separate business phone number?
• The solo founder's phone problem