When Customer Service Became My Secret Weapon
I learned the power of consultation-based meetings while working with our customer service team at a previous company. Initially, our monthly meetings followed the standard format: I would present upcoming feature releases, planned maintenance windows, and other information the agents needed to know. They would ask clarifying questions, and we'd wrap up in thirty minutes.
But I wanted to transform these agents from passive recipients of product updates into active contributors to our product roadmap. This required completely changing how our meetings worked.
The first few sessions were awkward. I asked them for their product ideas and suggestions. But when agents brought up feature ideas, I then asked for evidence. As a product manager, I couldn't just act on "because customers will like it" or "because I heard someone mention it once." I needed some data to help weight their suggestions against all the other items in my backlog. From customer service, I needed ticket counts, customer verbatims, specific requests from sales leads, or quantifiable trends in support interactions.
Initially, the agents pushed back. Gathering this evidence felt like busywork that would slow down their ticket resolution times. But something shifted as we continued the consultation process: they started to see the purpose behind the data collection.
The agents realized that proper tagging and documentation weren't just administrative tasks. They were building cases that could drive real product changes. Their insights could influence the roadmap. Their contributions could be highlighted in performance reviews and team meetings. They went from being order-takers to being strategic partners.
The team started tagging tickets more effectively. They found creative ways to identify trends in the data. They asked more follow up questions when on the phone to customers. They became sources of key information about the product, the market, the industry, even our competitors who were trying to steal them away from us.
Our products got better because we were solving real customer problems with quantified evidence. Our customer service analytics became more valuable because agents understood how their data was being used. Most importantly, the agents' job satisfaction increased because they had genuine influence over the products they supported every day. All because we transformed a one-way information dump into an ongoing consultation on how we could better serve customers together.
What Made the Transformation Work
Looking back, the transformation worked because we changed four things about how those meetings operated.
Problem Framing
Instead of opening with "here are this month's updates," I started with a question: "What are the top customer pain points you're hearing this week?" That single shift changed the entire energy of the room. The agents weren't there to receive information anymore -- they were there to define the problem we'd solve together. The meeting had a purpose they owned.
Structured Input Gathering
I asked agents to come prepared with ticket data and customer verbatims. At first, this felt like homework nobody wanted. But once they saw their data actually showing up in product decisions, the preparation became a point of pride. They started tagging tickets more carefully specifically because they knew the data would be used. The meeting became the tip of an ongoing evidence-gathering process, not a standalone event.
Systematic Analysis
We evaluated ideas against actual support volume and customer impact, not just gut feelings about what customers wanted. When an agent proposed a feature, we'd look at it alongside competing priorities using the same criteria: how many customers does this affect, how severe is the pain, and how does it compare to what else is in the backlog? This kept the conversation grounded and made it clear that every suggestion got a fair hearing.
Explicit Decision Protocols
Every meeting ended with clear decisions about what would go into the product backlog, who would gather additional data if needed, and when we'd revisit open items. The agents could see exactly how their input translated into action. No more wondering whether their ideas disappeared into a void.
From Order-Takers to Strategic Partners
The agents went from being passive recipients of product updates to strategic partners who actively shaped what we built. And the product got better because of it -- we were solving real, quantified customer problems instead of guessing at priorities from the product team's distance. If your meetings feel like time-wasters, the fix probably isn't fewer meetings. It's redesigning the ones you have around consultation instead of information transfer.