← Back to blog
MSPGuidesHaloPSAConnectWise
17 October 2026Lewis Williams

7 warning signs an MSP client is about to leave

4 min read

Most MSP clients do not leave in a single moment. They drift. The signs are usually sitting in your PSA for months before the notice email arrives, and nobody spots them because nobody has time to read fifty accounts every week.

Here are the seven signs worth watching, what each one looks like in HaloPSA or ConnectWise, and how to tell a real warning from an ordinary quiet month.

First, measure each client against its own normal

A client raising four tickets a month is not a problem if it always raises four. The same number is a warning if it used to raise fifteen. Fixed thresholds across the whole book miss this, because every client has a different rhythm.

So for every sign below, the question is not "is this number high or low?" but "is this outside what this client does in an ordinary month?" Six months of history is usually enough to see a client's normal range: three to learn what usual looks like, three to compare against it.

1. Tickets dry up

The most reliable early sign is a busy client going quiet. It rarely means everything is working perfectly. More often, someone at the client has started fixing things themselves, gone to another provider for new work, or stopped bothering to raise issues because they have already decided to leave.

Where to look: tickets raised per month, per client, over the last year. Flag a client when the last three months sit well below its usual range, not just below last month.

2. First response times slip

Slower first responses are the first thing a client feels, and the first thing they mention at renewal. A queue change, a lost engineer or a new big client can quietly push one account to the back.

Where to look: median time to first response per client per month. Medians matter here: one ticket left over a weekend should not move the number, a pattern should.

3. The open backlog grows

A growing pile of open tickets for one client means work is arriving faster than it is being finished. The client sees the same issues come up again in every conversation.

Where to look: open tickets at the end of each month, and tickets left open far longer than that client's usual time to resolve.

4. The person who raised everything goes quiet

Many clients have one contact who raises most of the tickets. If that person stops, they may have left the business, lost interest, or been told the contract is under review. Either way, your relationship just got thinner.

Where to look: the requester on each ticket. Watch the share raised by the top contact, and whether that contact has raised anything recently.

5. More tickets arrive out of hours

A jump in tickets raised in the evening or at weekends can mean staff are frustrated enough to log issues as soon as they hit them, or that the client's working pattern has changed and your cover no longer fits it.

Where to look: the share of tickets created outside your support hours, compared with the client's own history.

6. A renewal arrives with nobody ready

Renewals decided at the last minute get decided on price. If a contract is ending in the next 90 days and nobody has spoken to the decision-maker about the year, you are negotiating from the weakest position you will ever have.

Where to look: contract or agreement end dates. Start the conversation at 90 days, propose terms at 60, confirm at 30.

7. They cost more to serve than they pay

This one is not about the client leaving. It is about whether you want to keep them on today's terms. A client creating far more work than their fee covers will eventually force a price conversation, and it is better to have it on your timing.

Where to look: monthly contract value divided by hours logged, compared with your typical rate across all clients.

What to do when you spot one

  • Call before you email. A short call to the main contact, before they raise it, changes the tone of everything that follows.
  • Say what you are changing. If response times slipped, say why and what you have done about it.
  • Show them the work. A one-page summary of what you resolved, how quickly, and what is still open does more than a long QBR deck nobody reads.
  • Write down what you did. Next month you will want to know whether it worked.

Doing this every week without a spreadsheet

You can track all seven signs by hand, but it takes hours per month and stops the week someone gets busy. Handover reads HaloPSA or ConnectWise every week, checks each client against its own normal range, puts a pound value on the ones that changed and gives you one ranked list, with the email already written for each. The free scan shows your own clients in about a minute.

Common questions

What is the earliest sign an MSP client might leave?
A busy client going quiet. When ticket volume falls well below that client's usual range for a few months, it often means they are fixing things themselves, using another provider, or have already decided to move.
How much history do you need to spot client churn?
About six months: three to learn what a normal month looks like for that client and three to compare against it. Contract end dates and accounts with no activity can be checked from day one.
Should I use the same threshold for every client?
No. Every client has its own rhythm, so compare each one with its own history. Four tickets a month is normal for some clients and a warning for others.

Run your free scan

See which of your clients are slipping, ranked by what they pay. Connect HaloPSA or ConnectWise with a read-only key.

About a minute, no trial, no card.

Share this article