Building a Product: Customer Support
Tags: product, customer, support, android
Published: 2019-12-23 00:25:15

Bad reviews affect your app's ranking and discoverability in the distribution channel. It can be frustrating when your app is receiving such reviews.


One of the lessons I learn from releasing [Typing Hero](https://www.typinghero.app/) to public over a year ago is how to turn bad review to five stars review. Is that even possible?


It depends!


Bad reviews are usually given by reviewer to express themselves. Of all bad reviews given for [Typing Hero](https://www.typinghero.app/), I learned that users are expressing one of the following:

* Frustration
* Accusation
* Principle
* Power


If users are expressing frustration or accusation, it is still possible to get five stars review from them. If users are expressing the latter, I find it a waste of time to even try, unless you focus your effort on explaining your principle for others to understand.


So, how does one turn bad review to five stars review? Customer Support!


# What is Customer Support?

In context of technology product; an app in this case, [customer support](https://en.wikipedia.org/wiki/Customer_support) is termed [technical support](https://en.wikipedia.org/wiki/Technical_support). Technical support provides help regarding specific problems with a product or service, and maybe delivered over by phone or internet.

Customer support is considered as one of the main data channels for [customer satisfaction research](https://en.wikipedia.org/wiki/Customer_satisfaction_research) and a way to increase [customer retention](https://en.wikipedia.org/wiki/Customer_retention).


# Dealing with reviews

I always respond to every review, doesn't matter if it's the perfect five stars review, or the horrific one star review. Some might find responding to each review as too much, but I personally find that it's the only way to show that the team who build the product care about the product and the users. I believe Customer support is a very critical aspect of a product, but often underrated and disconnected from the team developing the product itself.


## Bad review examples

### Frustration

![Frustration #1](https://thepracticaldev.s3.amazonaws.com/i/5vwjxy8wpgispi5h071z.png)

![Frustration #2](https://thepracticaldev.s3.amazonaws.com/i/oph3mbfy0bj8zttg8982.png)

One user is frustrated because Typing Hero stops working a couple of days later. Another is frustrated because Typing Hero never works!


### Accusation

![Accusation #1](https://thepracticaldev.s3.amazonaws.com/i/bgsjv5dluau0cbhsskxr.png)

![Accusation #2](https://thepracticaldev.s3.amazonaws.com/i/y9tmzmn9h16ph8vybb8p.png)


Typing Hero is accused of containing adware and slowing down user's device. How might you respond differently?


### Principle

![Principle #1](https://thepracticaldev.s3.amazonaws.com/i/o3gis4nyyt51przw4zv2.png)

![Principle #2](https://thepracticaldev.s3.amazonaws.com/i/f922rp7fx8b498rvnl08.png)


Users believe Typing Hero should not request internet permission due to its capability of reading what is typed on the device.


Don't get me wrong, this is a very fair concern. But I stand my ground for all the reasons I wrote in the reply for that review.


### Power 

![Power #1](https://thepracticaldev.s3.amazonaws.com/i/ound08w0j06q9vb92quh.png)

![Power #2](https://thepracticaldev.s3.amazonaws.com/i/54n4xo36tpa62t35s5td.png)


Users asking for translation and new functionality.


As you can see from the examples above, I'm not able to turn those reviews into five stars. That's sad, but at least I showed that I really tried to reach out to them, either to explain, stand my ground, or resolving their issues.


## Bad to five stars reviews

The following are some bad reviews that were changed to five stars after making them understand what the issue is, and helping them resolve the issue.


![Five Stars #1](https://thepracticaldev.s3.amazonaws.com/i/ih686wmm5swhrirhyho1.png)

![Five Stars #2](https://thepracticaldev.s3.amazonaws.com/i/hgc2afrc1kc95sn1ipgs.png)

![Five Stars #3](https://thepracticaldev.s3.amazonaws.com/i/ew1ss5h6m11grj2qqels.png)

![Five Stars #4](https://thepracticaldev.s3.amazonaws.com/i/fi6ysglds6q78gyt9r37.png)

![Five Stars #5](https://thepracticaldev.s3.amazonaws.com/i/ot2hzhm2rnwfw6p0l8aj.png)

![Five Stars #6](https://thepracticaldev.s3.amazonaws.com/i/yve2kys9mge2ct6pbv5j.png)

![Five Stars #7](https://thepracticaldev.s3.amazonaws.com/i/mvfbtbjl3djgild4ukhx.png)

![Five Stars #8](https://thepracticaldev.s3.amazonaws.com/i/p77l36uvr4iftgqmltu6.png)

![Five Stars #9](https://thepracticaldev.s3.amazonaws.com/i/cf0typy9ag0zb7dtw4ip.png)

![Five Stars #10](https://thepracticaldev.s3.amazonaws.com/i/7vkfilyb77d8mbqe7s8n.png)

![Five Stars #11](https://thepracticaldev.s3.amazonaws.com/i/08ne3806wvj5z9bdua3q.png)


# Lesson Learned

Bad reviews are calls for help from users. They could be a golden ticket to five stars review. The chance of getting five stars review from those who give bad review is higher than from those who don't rate or review at all.


Whatever stage your product is, always prioritize supporting your customer over working on new features. Help yourself by keeping your customer continue using the product you build.


As a company, consider making Customer Support part of the team designing and building the product. If Customer Support team is integrated with those teams, they will have the same in-depth knowledge of the product. Such knowledge will empower them answering questions from frustrated users with on point responses.