Finding bugs in your product is part of your customer’s journey. Customer happiness comes from having a stable product and less user tension. But there’s more to making customers happy than having a bug-free product. This is where customer success comes in.
What is customer satisfaction, in simple words?
The term “customer happiness” was coined only recently, but it is already big with SaaS companies in the Valley. The idea is that making sure your customers are happy and successful ensures a higher customer LTV (Lifetime Value), reduces churn and boosts your NPS (Net Promoter Score).
At Server Density, we often consider customer happiness and success. Here are six things we do to ensure our customers are happy and making the most of our product.
Also Read:
A list of great user feedback widgets
Proper user onboarding sets the foundation for happy customers. At this point, you should nurture your customers and ensure that they are aware of and using all parts of your service or product.
When a user signs up with Server Density, a customer happiness manager personally reaches out to them to schedule a call to understand their monitoring requirements.
Using Totango, we note everything about the customer: what they need, the key contacts, how they see their infrastructure evolving, and how we can help them achieve their goals.
This may be something as simple as sending over relevant documentation or as significant as expediting feature requests or getting stuck writing scripts for them.
Regardless of what you do, make sure your success managers are doing something at this crucial stage of your customer’s journey.
It makes a big difference when you make contact early on and get to know your customers on a more personal level.
[Tweet “It makes a big difference when you make contact early on and get to know your customers on a more personal level.”]
But you can do more because onboarding doesn’t need to be an entirely manual process.
At Server Density, we send several automated lifecycle-related emails during the onboarding journey. It’s essential that you identify and create relevant campaigns that highlight your product’s most important parts.
We look at our most successful long-term customers and ask them what they’re doing. We find that they’re heavily invested in APIs, using our ops dashboard, and often make contact with our support team (note: lots of support requests from a customer don’t necessarily mean they’re unhappy).
A few days before the trial expiry, reach out again.
We do this to identify any blockers that would prevent customers from moving into a paid package. We try to achieve positive engagement, work with customers to solve any commercial problems, and genuinely ensure they’ll make the most of our product.
Customer support is something I’m personally very passionate about.
I truly believe giving your customers the best treatment when they contact you is a key to happier customers. Ask somebody why they’re loyal to Apple and he or she will probably say customer care. Ask a Server Density customer and they will also probably mention our support.
Make sure you are quick, concise, and personal.
Picking up the phone within 2 rings, accepting a live chat in seconds as opposed to minutes and pulling up a Zendesk ticket right after we get the notification is key here.
We start investigating an issue immediately. Our support team always knows our customers, their infrastructure, and their previous support requests to deliver unrivaled personal support.
Never send dull, one-liner responses.
Go above and beyond by sending links to relevant documentation, explaining issues, fixing scripts and debugging API calls. And if you think you should be speaking to the customer properly – pick up the phone and talk through it. Customers remember that.
At Server Density, we define internal SLAs (Service Level Agreements) to ensure we’re beating response time expectations. However, don’t do this if it results in your support engineers rushing to give answers. It looks sloppy, and you may as well not have the SLA!
For larger customers, we manually review accounts every 3 months. We use Totango to trigger tasks that are assigned to the user’s success manager. This is a good way to be proactive and ensure that you’re checking in with customers before they’re checking in with you.
When performing account reviews, it’s a good idea to have a template and know what you should be taking away from the meeting.
For us, we identify how our customer’s infrastructure is changing, how it’s recently changed, and their goals for the next quarter, talk about new features and any problems, and then open up the discussion for general chat. Not all customers will want a quarterly business review but offer it anyway.
Recommended Reading:
Recently, our CEO David came back from the USA. Part of this trip involved visiting some of our larger customers in person – and previously some others in Europe during summer. I don’t think we need to explain why we do this, but it goes a long way in tightening relationships with our customers.
Remember, these accounts make up a larger portion of your revenue.
Customer success software provides “out-of-the-box ” metrics, which are usually about how often your users log into your app, what they’re doing, license utilization, etc.
Crunching these figures just won’t work for all companies – Server Density included.
We use Totango’s custom metrics to build more relevant numbers that better help us identify the health of a customer. Our customer’s servers post back to Server Density (“payloads”) almost like a heartbeat. We then get the total daily number of payloads send this to Totango and perform the following equation:
This metric is called payload utilization, which, amongst other things, we use to judge whether or not our customers are making the most of monitoring. Think about what actionable unique metrics your company has, measure them, and then act on them if they’re not normal.
Most customer success software has default health profiles — poor, average and good health.
Often, these profiles segment accounts by how often users are logging into your app (e.g., daily for good health, weekly for average health, etc). These profiles aren’t suitable for some SaaS companies, Server Density included.
Some of our customers may log in every day, others every week, and the rest monthly. Therefore, we needed to define relevant health profiles.
This is where the custom metrics previously mentioned come in useful. If a customer’s payload utilization drops by 50%, this means they’ve removed 50% of their servers. That classifies the customer in bad health.
I can’t stress enough how important it is to really think about what classifies your customers as good or poor health. Set these up properly, and then make sure that your customer success managers are taking the correct action when accounts move between different profiles.
Harry Perks leads Customer Success and customer happiness at Server Density. He ensures customers are making the most of their monitoring, and should they run into any issue, he makes sure they’re delivered world-class support. You can find Harry on Twitter.
If you are looking for a way to improve your customer happiness, then it is time for you to implement customer feedback tools as well. For this, Usersnap is a great option.
This article was also brought to you by Usersnap – a customer feedback, screen recording, screenshot, and bug tracking tool for every SaaS company. Try it out for free with your team now, sign up for a 15-day free trial.
Ever wonder how some companies make product updates feel like the highlight of your day? …
Picture this: You’re in the middle of a hectic workday, balancing strategic decisions with daily…
Ever wish customer feedback came with subtitles? With the right feedback analytics tools, you can…
Survey design is the backbone of effective data collection, enabling businesses, product managers and researchers…
Wondering how to master Jira’s vast capabilities for strategic project/product success? Epics are the key…
In this article, we walk you through the ultimate in-app feedback how to strategy, including…