Why eNPS Matters More at an MSP
In an MSP the technicians are the service. Clients experience you through the people who answer the phone, work the tickets and show up on site. When a good technician leaves, you lose more than a seat: you lose their knowledge of each client's quirks, their relationships with key users and the hours it takes to recruit and train a replacement. eNPS is an early warning for that turnover, and it moves before resignations do.
It uses the same scoring as client NPS: promoters score 9 or 10, detractors 0 to 6, and the result is promoters minus detractors. For current targets, see the Employee Net Promoter Score KPI.
Running It Well
- Keep it anonymous, and say so. In a small team people will not answer honestly if they think the owner can tell who said what.
- Run it on a regular schedule, such as every quarter. A single reading says little; the direction over several rounds is the signal.
- Add one open question: what would make this a better place to work?
- Share the result and what you will change. A survey with no visible follow-up teaches staff that answering is pointless.
Small MSPs have a special problem: with a handful of staff, splitting results by team can identify people. Report the company score only until each group is large enough to stay anonymous.
Keep the question worded exactly the same each round and send it at a similar time, avoiding the week of a big project cutover or the end of a bad month. Timing alone can move a small team's score, and you want changes in the number to reflect changes in the workplace.
What Usually Drives the Score
| Common theme | Where to look |
|---|---|
| Workload and burnout | Endpoints per technician and ticket volume |
| Pay | Market rates for each role |
| No path to grow | Training, certifications and promotion criteria |
| Difficult clients | Which accounts generate the most frustration |
Several of these connect to numbers you already track. A team carrying too many devices each will score low however good the culture is, so read eNPS beside endpoints per technician and employee turnover. If pay comes up, check it against your local market before assuming the problem is elsewhere.
Connecting It to Clients
Staff sentiment reaches clients quickly. A falling eNPS often shows up a few months later as slower tickets and weaker CSAT. Treat a drop as an operational issue, not only an HR one, and bring your service lead into the conversation about what to fix.
Common Questions
Should contractors be included in eNPS?
Include long-term contractors who work like staff, and leave out short project help. Keep the choice the same each round so the trend stays comparable.
Which tool should an MSP use to run eNPS?
Any survey tool that keeps responses anonymous works. What matters is that staff trust the anonymity, so avoid tools that tie answers to logins you can see.
Can eNPS predict a technician leaving?
Not for a specific person, since responses are anonymous. It shows whether the risk across the team is rising or falling.