How to Coach Your CSMs to Say No Without Losing the Customer Relationship

Speaker A: M Before we dive into today's episode, a quick question for customer success leaders. Does your team have a clear way of guiding customers to value or measuring value today? If your answer is no, then my Value Realization Framework Online course is for you. It's a self paced online program that helps you install a repeatable system so your team delivers value, proves outcomes, and drive retention and expansion. Check out the program details@csrevspeak.com VRF get instant access and lifetime updates when you enroll again. That's csrevspeak.com VRF see you there. I, uh, want you to think about the last time a customer asked your team for something that was outside scope. Maybe it was a feature request, they want to treat it as a priority. Maybe it was a custom integration that wasn't in the contract. Or maybe it was a demand for a dedicated resource your team simply doesn't have. And I want you to think about what your CSM did if they said yes or some version of yes without thinking twice about it. That's what this episode, uh, is about. Because here's what's actually happening when a CSM can't say no. They're not being customer centric, they're being conflict averse. And those two things look identical on the surface, but they produce completely different outcomes. The CSM who says yes to everything thinks they're building trust. What they're actually building is a customer who expects more than you can deliver, a team that stretches beyond capacity, and a relationship that's quietly heading towards disappointment. The ability to say no confidently, clearly and without damaging the relationship is one of the most important skills a CSM can have. And most of them have never been taught how to do it. That's what we're fixing today. Let's get into it. Welcome to the CSREVspeak podcast, where we talk about practical insights, strategies and frameworks that will help customer success leaders who carry a revenue number drive sustainable growth, maximize customer lifetime value, and crush their numbers. Before we get into frameworks and language, there's a mindset shift your CSMs need to make first. Because the tactics won't land until the belief underneath changes. And the belief I want to challenge directly is this that saying yes is what being customer centric looks like. I want to start here because this is the reframe your CSMs need before anything else will land. Most CSMs who can't say no genuinely believe they're doing the right thing by the customer. They've been told that their job is to make customers Successful to be the customer's advocate, to prioritize the relationship above everything else. And in their minds, saying yes is how you do all of those things. So when you tell them they need to learn to say no, the first thing they hear is be less customer focused. And that creates resistance because they're working from a belief that needs to be directly challenged. So here's the reframe. Saying yes to everything is not customer advocacy. It's customer appeasement. And there's a meaningful difference. Customer advocacy means understanding what a customer actually needs to be successful and helping them get there, even when that means having an uncomfortable conversation. Customer appeasement means avoiding discomfort at all costs, giving customers what they ask for in a moment and hoping it doesn't create problems later. The appeasement approach feels kind in the short term, but here's what it actually produces. It creates expectations that can't be sustained. When a CSM says yes to something outside scope, they set a precedent. The customer now believes that's what the relationship looks like. And when the next requests come in, because it always does, the bar has shifted. And now the CSM is in an even harder position because saying no feels like a withdrawal of something that was already promised. It also erodes the customer's trust and CS as a strategic partner. When a CSM agrees to everything without pushback, they stop being an advisor and become an order taker. And customers don't renew because they have a great order taker. They renew because they have a trusted partner who tells them the truth, helps them make good decisions, and holds them accountable to the outcomes they said they wanted. The CSM who can say no thoughtfully, respectfully, and with a clear reason is actually doing more for the customer relationship than the one who says yes every time. That's the reframe. Make sure your team has internalized it before you teach them the mechanics. Okay, your CSM understand why no matters now they need to know when to use it, because not every situation calls for the same response. And one of the things that makes this hard is that the lines aren't always obvious. There are broadly three types of situations your systems will encounter where the answer isn't a, uh, straightforward yes. The first is a request that's clearly out of scope. Something that's not in the contract, not aligned with what was sold, not something your team can or should be doing. This is the clearest case for a no. But even here, the no needs to be delivered in a specific way. Not a flat refusal, a, uh, redirect that's not something we can take on within the current engagement, but let me help you think through what it would take to get there. We'll talk more about the language in the next segment. Okay. The second is a request that's in scope but poorly timed or poorly prioritized. The customer wants to focus on something that isn't actually aligned with their stated goals or they're pushing for a sprint on a fee feature before the current implementation is even stable. This isn't a no to the request itself is a no to the timing. And that conversation sounds like I want to make sure we're putting our energy where it's going to have the most impact for you right now based on where you are. I'd actually recommend we focus here first. Here's why. That's not a refusal, that's guidance. And that's exactly what a strategic partner does. The third is a request that needs to go somewhere else to product, to support, to sales. This is the escalation category and what I say Most often is CSMs who absorb these requests themselves because they don't want to redirect the customer and risk the customer feeling passed off. So to take it on, they try to handle it informally and they create two problems. They overload themselves and they deprive the customer of the right resource. Coach your CSMS to understand that escalating or redirecting is not a failure of service, it's actually better service. That's a really important request and I want to make sure it gets the right attention. The best person to handle this is on our product team. Let me connect you directly and make sure the context gets transferred properly. That's a CSM who is advocating for the customer and not abandoning them. The diagnostic question your CSM should be asking themselves in any ambiguous situation is this. Does saying yes to this actually serve the customer's goals, or does it just make the conversation easier? If it's the latter, the answer is probably a no or a redirect. Now they know when to say no. The next question is how? Language is usually the first thing CS leaders reach for when they're trying to solve this problem. And I understand why. It's the most tangible, the most teachable part. But I, um, want to be honest, the language only works if the mindset from our earlier segment is already in place. A ah, CSM who doesn't believe saying no is okay will deliver even the best scripted response in a way that comes across as apologetic or uncertain. The belief has to come first. With that said, here's how you actually do it. The structure I want your CSMs to internalize is three parts. Acknowledge. Redirect. Anchor Acknowledge means naming what the customer is asking for and showing that you heard it, not dismissing it. You're not jumping straight to the no. So something like, I hear you, you're looking for X and I understand why that feels important right now. Redirect means explaining what you can do instead of or before whatever it is that they're asking for. This is where the no lives. But, uh, it's framed as a direction rather than an outright refusal. So something like what I'd recommend instead, and here's why, is that we focus on why first, based on where you are in the journey, that's going to get you to the outcome you're after more directly. Anchor means tying the redirect back to something that the customer already said they care about. So their goals, their business outcomes, the success criteria you defined together at the start of the engagement. You told me, uh, at the start of this quarter that your biggest priority was getting your team to full adoption before the renewal conversation. This is the path that gets you there. When a no is anchored in the customer's own goals, it stops feeling like a restriction and starts feeling like real advice. That's the shift that you're coaching your CSMs for. Let me give you a concrete example. A customer asks their CSM to build them, um, a custom report that's outside the scope of the engagement. A CSM without this framework says, I'll see what I can do, takes it on, spends three hours on something that wasn't in the plan and quietly resents the customer for it. A, uh, CSM with this framework says, I appreciate you flagging this. Having that visibility clearly matters to your team. Customer reporting is outside what we can take on within our current engagement. But I want to make sure you get what you need. There are two options I'd suggest. One is connecting you with our solutions team to scope what that would look like as an add on. The other is working with what's already available in the platform. I can walk you through what's there and whether it covers what you're looking for, which would be more helpful. So same situation, right? Completely different outcome. The customer feels heard they have options and the CSM hasn't overextended or set a precedent they can't sustain. One more thing on language teacher csms to avoid over apologizing. I'm so sorry, I just don't think we're able to immediately Signals that the no is a problem, which makes the customer feel like they should push harder. Confidence in the delivery is what makes the no land as a professional boundary rather than a personal rejection. The tone should be warm and direct, not apologetic. This is something I work through with sales leaders in my one on one coaching program quite a bit. Because getting a team to shift from apologetic to confident in how they hold boundaries requires both the framework and deliberate practice. If your team is consistently caving under customer pressure is exactly the kind of dynamic we dig into together. Everything we've spoken about so far is about what your CSMs need to do. This one is about what you need to do as their leader. Because the ability to say no is not something CSMs develop on their own. Okay, scratch that. Of course it's something that they need to develop right through practice. But it also helps when their leader makes it safe to do so, coaches them towards that behavior consistently, and models it themselves. Let's start with safety. Most CSMs who can say no aren't missing a framework. They're missing permission. They've absorbed from the culture from past managers, from the way escalations get handled. That saying no to a customer is risky. That if an account churns and they said no to something that customer asked for, it will come back on them. And until you explicitly dismantle that belief, no framework will stick. So the first coaching move is to say it out loud in your one on ones in your team meetings. Say say no to a customer request when it's the right call is not a failure. It's good judgment and I will back you when you do it, then actually back them when they do it. If, uh, a system holds a boundary with a customer and it creates friction, don't quietly signal that they should have just said yes, but debrief it. Talk through whether the call was right. Reinforce the behavior even when it's uncomfortable. The second coaching move is to practice the language together before it needs to be used. Live roleplay is one of the most underused tools in CS leadership. Bring a real scenario to a one on one, ideally one. Your CSM is actually navigating and practice the Acknowledge redirect infrastructure together. This is a way of helping them find their own voice inside the framework so that when the moment comes, it doesn't feel scripted. The third coaching move is to debrief the real situations as they happen. When a CSM comes to you and says the customer pushed back hard when they said no, that's a coaching moment. Walk through it. What did they say, how did the customer respond? What could have landed differently? That kind of real time debriefing, uh, is where the skill actually builds. But, and the last piece is modeling it yourself. As a CS leader, you're in customer conversations too. Executive escalations, strategic account reviews, tough renewal conversations. When you say no in those moments, clearly, confidently, with a, uh, redirect and an anchor, your team sees what it looks like in practice. They see that the relationship doesn't collapse. They see that the customer respects it, and they internalize that. Saying no from a place of conviction is a form of leadership, not a failure of service. The CSMs who are the most trusted by their customers are really the ones who say yes to everything. They're the ones who tell the truth, hold the line when it matters, and show up as partners rather than pleasers. Your job as your leader is to build that, uh, capability deliberately through the permission you give, coaching you provide, and the behavior you model every time you're in a room with customer. Okay, let's bring this together. First, reframe what saying no actually means is not a failure of customer centricity. It's the opposite. A, uh, CSM who can hold the boundary thoughtfully is a more effective partner than one who says yes to everything and quietly erodes the relationship over time. Second, teach your CSMs to know when to say no, when to redirect, the timing, and when to escalate. The diagnostic question is simple. The saying yes to this actually serve the customer's goals? Or does it just make this conversation easier? Third, give them the language, acknowledge, redirect, anchor, hear what the customer is asking for, offer a direction that serves their actual goals and tie it back to what they said they care about and coach them to deliver it with confidence, not apology. And fourth, create the conditions where saying no is safe, practiced and modeled. Give your team explicit permission, role play the scenarios before they go live, debrief the real situations as they happen, and model the behavior yourself in the customer conversations you're part of. Here's what I know from working with customer success leaders on this. Getting a team to the point where they can confidently say no and hold that line without flinching requires more than a framework. It requires a shift in how the team sees their role and a leader who is actively coaching that shift week to week. And sometimes the most effective way to make that shift happen isn't just through your own coaching. It's by bringing in direct enablement for your team, giving them the frameworks, the language and, and the practice in a setting designed specifically for that work. If you're managing a team that defaults to yes and you want to build this capability at the team level, not just through your one on ones, but through a structured enablement experience, that's something I offer. We work with your team directly, build the skill in a real practical way through trainings or role plays, and give your CSMs the confidence to hold the line without feeling like they're being less customer focused on. If that's something you want to explore for your team, check out csrevspeak.com enablement, schedule a consultation call and let's talk through it. Thanks for being here. I'll see you in the next episode. If you enjoyed today's episode and you want to learn more about CSREVspeak's coaching and training services, head on over to www.csrevspeak.com. i specialize in working with Customer Success Leaders leaders who carry your revenue number and I look forward to helping you confidently run a revenue generating customer success team. Don't forget to connect with us on LinkedIn and join our Customer Success Leaders hub for more discussions, resources and networking opportunities. You can access the links on the show Notes. See you next episode.