Where AI actually helps a CS team, and where it's just more noise

Every CS platform on the market right now has an AI story. Predictive churn scores, sentiment analysis, auto generated QBR decks, agents that draft the renewal email before you've read the account. Some of it is genuinely useful. A lot of it is volume dressed up as insight, and the panel has spent more time than expected pulling those two things apart.

The clearest example came from Erin Felton, talking about what an early churn signal actually looks like. An account can be active, logging in, using the product, generating all the usage data a health score wants to see, and still be quietly dying because nothing real is happening in those sessions. Activity without value. That's the exact thing AI is worst at catching, because most tools are built to measure activity, not to judge whether the activity means anything.

There's a broader worry underneath that, one the group keeps coming back to. Models tuned to sound agreeable will tell a customer what they want to hear, and that's a real risk if AI becomes the layer between your team and the customer instead of a tool your team uses before or after talking to them. Erin's suggestion is a good starting discipline. Before you point AI at customer interviews, point it at your own sales calls first. Get comfortable with what it catches and what it flattens on a conversation you already understand, before you trust it on one you don't.

Where the panel is more genuinely excited is signal surfacing across systems that were never talking to each other. Diana Gabroveanu's work is close to a full time job built around this, tying advocacy, community, and loyalty data together with AI to catch things a single team would never see on its own. Anderson Campbell flagged something worth watching too, the way AI is changing how accounts get used day to day, including whether usage is spreading across a team or still sitting entirely on one person. That single-user heroics pattern, where the whole account collapses if one champion leaves, is exactly the kind of thing AI is well suited to flag early, if someone is actually looking at it and not just collecting the dashboard.

The honest version of where PSA lands on this: AI is good at finding patterns across more accounts than a human team could ever manually review, and it's bad at telling you which patterns actually matter to the person on the other end of the account. Use it to widen what your team can see. Don't let it replace the part of the job where someone picks up the phone and finds out what's actually going on.