Strategically loud
How I stopped escalating every feature request and started building a relationship with product that trusts my read.
Early in my career, every feature request got the same treatment. Customer mentions it on a call. I write it up. I ping the product manager. I make the case. Next call, next request, same motion.
On paper, that looks like advocacy. That’s what a CSM is supposed to do, right? Fight for your customers. Be their voice internally.
In practice, it did something else. It told the organization I couldn’t look at feature requests and product prioritization through a strategic lens. Because most of what I was pushing wasn’t threatening retention. It wasn’t blocking expansion. It was just things customers wanted. And product could tell the difference, even when I couldn’t.
The shift
I’m still loud. Anyone who has worked with me will confirm that. But my relationship with product has changed from loud to strategically loud.
This doesn’t mean ignoring requests. Every request still goes through the proper channel. It gets logged, tagged, and tied to the account. The system of record stays complete.
The filter applies to what happens after. Which requests actually merit a direct message to a product manager? Which ones deserve a conversation with leadership? That’s a much smaller list. It should be.
The bar for escalation
A request earns my voice when it benefits more than one customer. It has to matter to the business, not just the account.
What that usually looks like: it unlocks a market we can’t currently sell into. It removes a blocker that’s threatening expansion revenue. It opens up use cases the product can’t support today. Or it’s a critical dependency stopping customers from growing with us.
If a request doesn’t hit one of those, it still gets logged. It just doesn’t get escalated.
Being intentional about where you apply your voice changes how product sees you. You stop being the person who forwards requests and start being an advisor. Someone who understands that product has limited time, that prioritization is real work, and that the business is a business. That understanding is what earns you the room when you do escalate.
The fair objection
The obvious pushback: isn’t this under-advocating? If you’re filtering, some customers’ requests never get a champion behind them.
Effectively, yes. And that’s the point. Selective advocacy is what makes advocacy work. When you escalate everything, product stops listening. Your requests blur together. You burn the political capital you need to actually move people to action. The customers with requests that genuinely matter end up paying for the noise generated by the ones that didn’t.
You won’t always get the call right. I don’t. But the goal isn’t perfect judgment. It’s earned attention.
Context does the work
When I do escalate, I lead with context, not volume. Three questions do most of the work.
What’s the market trend I’m seeing? What’s the pattern across the customer base? Which customers are hitting this today, and which industries would it unlock tomorrow?
If I can’t answer those, the request probably isn’t ready to escalate. If I can, the escalation stops being a complaint and starts being a business case.
The other shift is framing. I open a conversation instead of filing a demand. “Here’s a pattern I’m seeing across four accounts, here’s what I think it could mean, what’s your read?” lands very differently than “Customers need this, when is it shipping?” One invites product into the thinking. The other puts them on defense.
The reputation this builds
Do this consistently and your reputation inside the company changes. You stop being a request taker who processes tickets and yells on the back of them. You start being someone who monitors trends, thinks from a bird’s-eye view, and cares about how the organization protects and expands its revenue.
That reputation compounds. Product starts seeking out your read before roadmap planning. Leadership asks what you’re seeing. Your escalations get taken seriously precisely because there aren’t many of them.
You don’t have to get quieter. You have to get deliberate about where the volume goes.
Loud is easy. Strategically loud is earned.