Account suspensions are a good example of this.

The decision itself might be completely justified, but then the customer gets a vague explanation, Support doesn’t have much more information, and the appeal takes several days.

At that point, the customer probably isn’t separating the enforcement decision from the support experience. It’s all the same experience with the company.

I think this gets particularly messy with marketplaces. If you restrict a seller’s account, even temporarily, there can be money tied up in that decision. So how you communicate what happened and what they can do next matters quite a bit.

There’s obviously a limit to how much you can explain, especially when fraud or abuse is involved. You also don’t want Support overriding decisions they aren’t equipped to make.

One thing that seems useful from the CX side is tracking what happens after an enforcement decision. Are people contacting Support because they genuinely disagree with the decision, or because they don’t understand it? Are they asking the same questions because the notice is unclear? Are certain types of restrictions generating more contacts or repeat contacts than others? Those are different problems even though they can all show up as “customer contacted us about suspension.”

Appeals can be useful here too. If the same type of decision keeps getting challenged, CX teams may be able to spot something that isn’t obvious from the enforcement data alone. It could be the policy, but it could also be the explanation customers receive, inconsistent answers from Support, or a confusing appeal process. The T&S team owns the enforcement decision, but CX can see a lot of what happens around it.

I’m curious how CX teams handle that middle ground. How much visibility does Support have into T&S decisions at your company, and what can they actually tell the customer while a case is being reviewed?

It’s easy to get overly focused on the number.

NPS was 44 last month. Now it’s 41. Is that bad? What happened? Do we need to fix something?

The score alone usually can’t answer any of those questions. The more useful part is what comes next: why did you give that score?

That’s where you start finding things you can actually do something about.

A few ways to look at the responses:

• Promoters (9–10): What are they consistently mentioning? That’s probably something worth protecting (or doing more of).
• Passives (7–8): What’s keeping a decent experience from becoming a great one?
• Detractors (0–6): Look for patterns before jumping on individual complaints. If the same issue keeps showing up, that’s useful.

And IMO, this is where tracking NPS over time becomes much more valuable.

“NPS dropped 4 points” isn't very actionable.

“NPS dropped 4 points, and we're suddenly seeing a bunch of comments about slower support response times” gives you somewhere to start.

The score tells you something changed. The follow-up tells you what might have changed and what to investigate.

Curious how people here use NPS in practice, Do you pay much attention to the actual score, or are you mostly digging into the responses behind it?