Ask Why - Handling customer escalations calls
If you are a Product Manager in a B2B company, you will find yourself getting pulled into customer escalation calls. Going up the ranks, it is common for Product leaders to manage customer relationships - manage retention and help win new deals. During such calls, tensions can run high. It will start with the Sales team reaching with something along the lines of “this customer is very unhappy. They are about to churn because a feature is not available” or “the product is not working as expected” as common reasons. I have seen Product Managers avoiding such meetings as much as possible. However, these meetings are a good opportunity to get to know your customers, how they use the product, and their expectations from the product, to get feedback and to validate your roadmap. Photo by Andre Hunter on UnsplashReasons for having a customer escalation callSales or Customer Success, or customer facing teams, will normally send an SOS to the relevant Product Manager. The most common reasons cited are:
What to do next?Get to know more about the customer and their problem. Try to understand more about the situation from the Sales / Success Manager before the customer call. Set up a call or reach out via Direct Message (DM) to get to know more about the customer, their situation and their problem. I have found that Sales/ Success’s description might be biased and solely focused on getting to a solution. You may need to shift the conversation to understand what is the problem they are trying to solve and the expected outcome. Reiterate that you are willing to work with them to reach a solution. Work with the Sales or Success Manager to come up with agreed next steps. Possible next steps based on the escalation:
Call set upSales / Success will be responsible for setting up the call. You could optionally invite Product Design and Engineering counterparts to the call. It is a good opportunity to understand the problem right from the customers. Conversation with the customerFrom the customer’s side, the person on the call is your product’s sponsor inside the organisation. Put yourself in the person’s shoes. They were one of the key decision-makers during the buying process. Now he/she is getting the heat from their teams or management because of the bug or the feature gap. During the call - spend time understanding the problem In the beginning of the meeting, give the customer some time to describe their problem. It will give you an unbiased view of the customer's needs. There will be a strong urge to be defensive. Take a deep breath. Acknowledge the bug or the problem. This will significantly de-escalate the situation. Treat the customer as a partner/collaborator on the product If it is a bug, provide more details on the process of resolution. Aim to get more information from the business to replicate the issue. Highlight if you need more time to identify the root cause or to get the bug resolved. If it is a feature gap and you have acknowledged the problem, you could move the conversation in a couple of different directions -
After the call - follow up on your open questions/actionsIt is normal for the conversation to move to other product areas. It is great if you are familiar with those other areas. If you are not, it is perfectly acceptable to say you do not know and volunteer to follow up on the question / feedback. Share notes or recordings of your customer call with other Product Managers, Product Designers and Engineering teams. It is a good way to show your awareness of customers’ needs, proof of validation for your roadmap and create a sense of urgency for resolution. Always keep in mind - the feedback is for the product, not a personal attack. The customer is in a tough spot with his team. Frustration and anger are natural responses. Take a deep breath, look at the big picture and re-iterate that you are here to help. Other links/resources:Thank you for reading the article! You can help us:✉️ Subscribe using this button 🤜 🤛 Share this directly with your peers and others who will find this helpful. Apply what you have learned and teach it to someone else, it will make it easier to recall later. 💬 Share this article on your Social Media (Twitter (we’re @readaskwhy), LinkedIn) ❓ Suggest topics or ask us a question 📥 Email us your questions, comments, and ideas. Simply reply to this email to contact us. If your friends, peers or colleagues could benefit from this article or the Askwhy newsletter, share it with them today. They can learn and grow too. Follow us on Twitter @readaskwhy |
Key phrases
Older messages
User Experience Research (UXR) for Engineers
Friday, September 23, 2022
Why should you care what the user says and what to do about it
Building a strong relationship with Engineering x Product Management
Wednesday, August 31, 2022
How to collaborate with Tech Leads and Architects
Think like a user researcher to level up job hunting, problem solving, collaboration and more
Thursday, July 14, 2022
Level up job hunting, collaboration, and promotion discussions with this mindset
Understanding Product Leadership and how to grow as a Product Manager with Rich Mironov
Tuesday, July 5, 2022
A Q&A session with a seasoned product leader and product coach
Improve working across time zones in product development
Wednesday, June 29, 2022
Reduce that “did this need a meeting?” or remote FOMO feeling
You Might Also Like
The Design World’s 19 Most Beloved Travel Destinations
Thursday, March 28, 2024
Plus, designers share the AD projects that still inspire View in your browser | Update your preferences Architectural Digest AD PRO Logo WILD, WHIMSICAL MEADOW GARDENS ARE THE LANDSCAPE TREND TO WATCH
How Balsamiq uses AI
Thursday, March 28, 2024
A peek into our ChatGPT conversations ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
Adobe AI, Remote, Stripe Sessions, Node.js Redesign, light-dark()
Thursday, March 28, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar March 28 2024 Defining experience quality in large language
Are Photorealistic Renderings Worth It?
Wednesday, March 27, 2024
Plus, the go-to garden stores of top designers and landscaping pros View in your browser | Update your preferences Architectural Digest AD PRO Logo Image may contain: Home Decor, Lamp, Desk, Furniture,
CSS Variable Groups, Layout Rhythm, Animate Borders, Parallel Lives, Visualization Techniques
Wednesday, March 27, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar March 27 2024 Proposal: CSS Variable Groups lea.verou.me CSS
The History of Ikat
Tuesday, March 26, 2024
Plus, Kips Bay Decorator Show House New York announces designer lineup View in your browser | Update your preferences Architectural Digest AD PRO Logo Image may contain: Art, and Painting SAVE YOUR
#449: UX Research
Tuesday, March 26, 2024
UX research impact, research invite emails, research without access to users, and UX research methods cheat sheet. Issue #449 • Mar 26, 2024 • View in the browser Smashing Newsletter Joh-eun jeonyeog-
Progress Indicator, Lissajous Curves, Pixel to Ink, Azulejo, Mac at 40
Tuesday, March 26, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar March 26 2024 Front-End solution: progress indicator piccalil.
Responsive Font Size, Icon Design, text-emphasis, Inclusive Sans, Accessible Forms
Tuesday, March 26, 2024
The 5 best design links, every day. Curated by a selection of great editors. Email not displaying properly? View browser version. Sidebar March 25 2024 A formula for responsive font-size jameshfisher.
👏 Impressive Dashboard Design Files + 🏆 Challenge Updates
Tuesday, March 26, 2024
🌟 Brighten Your Day with UpLabs' Design News! Firstly, let's congratulate Syndell, the winner of our latest 📝 Todoist Dashboard Redesign Challenge! Congratulations!! Secondly, don't forget