Get CloudCherry to analyse your customer’s journey, solve problems and delight them
Puma enhanced their ‘Customer Experience’ with the help of CloudCherry.
Using Predictive Analytics to Smooth the Customer Journey
CloudCherry | August 22, 2018
In the contact center, the queue is king. We get our data from tags in the queue to learn insights. We get our happiness rankings from surveys sent out after our customer interactions in the queue. We get metrics from the actions that we take in the queue. But, shouldn’t we start to move on? As customers become more and more savvy, and our products become more technical and nuanced, shouldn’t we, too, be trying to level up our game and dethrone the king?
There are two different types of service: proactive and reactive. Reactive, the type of service described above, is what has become the norm for most companies providing support over the internet, whether they be online stores, financial services or B2B products. Conversely, proactive support is all about identifying and resolving customer issues before they become problems. Some simple fixes to increase your proactive support game are:
In this article we want to help you go deeper and use path analysis to create a truly remarkable, next-level proactive customer experience. According to ThoughtCo, path analysis is “a statistical analysis used to evaluate causal models by examining the relationships between a dependent variable and two or more independent variables.” But, what’s all of that science-speak mean for customer service? For us, it means figuring out all of the customer data that you have, and pulling it together in one place to analyze what your customer is going to do next. Then, using that knowledge to intercede with amazing support before they even know they need it.
But why go through all the work? Because people love proactive service. 87% of consumers want to be contacted proactively if it means it will save them from having to use support in the future. Beyond the satisfaction that you will give your customers, though, proactive support also provides the following benefits:
So, let’s get down to it. In order to start doing any kind of accurate or useful path analysis, you’ll need to get some data. The best place to start is by understanding your customer journey. The four most important actions to track within the customer lifecycle, in terms of setting up proactive support are:
You’d think that this would be pretty second-nature to track, but many companies don’t keep data about when their customers first learned about their product. This is the start of your customer’s journey, and it’s incredibly important to track and make note of. If you have a product that offers different versions or varieties, you may even want to differentiate between the two in your tracking. For example, when did they first become a member of your debit card services, and when did they then start using you for their credit card as well? While it may seem straightforward, the start date of when they make that switch, if you have one to make, can provide a good trigger for any time-based proactive support that you will do moving forward.
The time between first signing up and buying, as well as what prompts the customer to buy, is integral in the customer experience. It shows when they have found enough value in your app to actual exchange money for goods. Tracking this both on an individual customer basis, and for your overall customer base can be incredibly useful for proactive support moving forward. Not only is paying for your product an excellent differentiator for service-level offerings, but it can also be a great trigger for any time-based flows.
Know what pages and parts of your product customers have used and which ones they haven’t. What actions do they take? Are there pages that they avoid? Knowing this will help you be even better at targeting on a specific individual level, but will also let you know if there are overarching areas of your product that people just do not use, or do not understand. You can use this data for individualized onboarding flows, to create better documentation, to improve parts of your app, or for email marketing campaigns.
No one wants customers to leave, right? You probably want to do everything in your power to stop it. Because of that, this may be the most important and valuable information that you can get. When you are able to understand why an individual customer has left, you can reach out to them reactively to do damage control. But, when you understand the patterns behind why every customer that’s left has left, you can proactively attack those issues before they crop up. This is specifically helpful for targeting them with messaging in your app.
Just as important as what they are doing within your product is what actions a customer takes when contacting your agents for help. There are three pieces of data that can be pulled from your helpdesk software and be useful in terms of customer retention and proactive support. Luckily for you, you don’t even really need any fancy analytics tools to get this information, though matching it up with the data above can prove tricky without them.
Knowing when your customers reach out to support is incredible important when considering when and how to proactively support them. For this, match up your customer lifecycle data from above with your customer data from the inbox, and start to pinpoint when they first reach out to ask questions. Is it within the first day? Is it before they even become a customer? Try to navigate and identify that first point is, and create a trend analysis that you can later use to trigger your targeting campaigns of workflows.
For this, tagging is going to be your best friend. Take a deep dive into the aggregated data that you have about what your customers are reaching out about. Then, match that up with the timelines for when they are reaching out. For example, are more people reaching out about billing within the first few weeks of their trial, and then only reaching out about shipping and handling after a few months of being a customer? These layers start to add up, and give you some additional definition to your support.
Are there times in their lifecycle when your customers are more active? Perhaps you have a somewhat complicated part of your application, or maybe they just need a bit more hand-holding when they just get started? For example, billing and invoices almost always create more questions. Make note of these trends and what your customers are reaching out about. Chances are that you can create an email campaign or an in-product flow that will help to deflect some of these issues.
The last layer of this delicious data cake is user cohorts. You know what people are doing in/with your product. You know how they are interacting with your support team about it. The last thing that you need to know is how they are grouped together, and what stories that data might tell for you.
No matter whether you are a SaaS product, you will likely have a broad swath of customers. A few different ways that you can determine the type of customer that you are dealing with (or the type of customer that they potentially represent for your company) are: by the amount of employees they have or by the amount of money that they are paying you. The main reason that identifying cohorts is so important is: it’s possible that you do not want to pay to support certain groups of individuals, in that case proactive support (and ultimately self-service) are excellent ways to lower your cost while still offering an excellent experience. Similarly, different types of customers may need different things. The documentation and experiences that you are providing for your enterprise customers should be different from the ones you’re sending to people who have just signed up.
So, now that we have all that data and we have it all mapped out and overlapped to have an even better contextual understanding, what do we do with it? Create excellent, intuitive proactive support experiences for our customers. The two that we’ll be focusing on in this article are through email, or via onboarding within your website/application.
Customized email campaigns are great because you can set them and forget them and the only time that they need to be updated is if something changes. They also are significantly less costly than in-app messaging and, because of that, can be targeted a little bit more broadly. They are, however, opened less frequently than in-app messaging.
The main benefit of customized email campaigns for proactive support, beyond the comparison to in-app messaging, is that they can be spread out over the course of a significantly longer period of time. Here are some cases when it might be good to use the customer journey to create some proactive email campaigns for your customer base:
Onboarding and user experience have become hot topics over the course of the past few years, and it’s no surprise. Why not try to make sure that your customers are able to engage with your brand in the best way possible? Triggering messaging on your website, or even interactive guides are an amazing way to help get your message to your customer right when they need to see it, in the context of what you’re trying to talk to them about. Here are some ideas for ways you can do it in your app:
While none of us have magical powers and are truly able to know exactly what a customer is thinking every step of the way, using a data-driven approach to proactive customer support can make your team seem like wizards. These recommendations both for data points to collect and how to use them can help impact how your brand and company’s support are seen, as well as making the first contact with your customers one of delight instead of frustration and disappointment