Humanizing Customer Complaints using NLP Algorithms

Humanizing Customer Complaints using NLP Algorithms

  • November 27, 2018
Table of Contents

Humanizing Customer Complaints using NLP Algorithms

Last Christmas, I went through the most frustrating experience as a consumer. I was doing some last minute holiday shopping and after standing in a long line, I finally reached the blessed register only to find out that my debit card was blocked. I could sense the old lady at the register judging me with her narrowed eyes.

Feeling thoroughly embarrassed, I called my bank right away. To my horror, they told me that my savings account was hacked and thousands of dollars were already gone! Once the initial shock subsided down, I decided to resolve the issue right away.

I had to call another number, prove my identity and file a formal complaint with little hopes of getting my money back. After spending an hour on phone, I slammed it down. I was so angry!

Five minutes later, I saw a text from my bank asking, ‘Are you happy banking with us?’ My first reaction was a few choice words followed by some more frustration and disbelief. Amidst this multitude of questions, came a stark realization.

I realized that as a Data Science professional, I was doing the exact same thing. In my organization, we were treating our own customer complaints with the same indifference. Just another data point; just another drop in the ocean.

So how was I any different?

Source: towardsdatascience.com

Tags :
Share :
comments powered by Disqus

Related Posts

Understanding word vectors in NLP

Understanding word vectors in NLP

In this tutorial, I’m going to show you how word vectors work. This tutorial assumes a good amount of Python knowledge, but even if you’re not a Python expert, you should be able to follow along and make small changes to the examples without too much trouble.

Read More
Predictive Scaling for EC2, Powered by Machine Learning

Predictive Scaling for EC2, Powered by Machine Learning

When I look back on the history of AWS and think about the launches that truly signify the fundamentally dynamic, on-demand nature of the cloud, two stand out in my memory: the launch of Amazon EC2 in 2006 and the concurrent launch of CloudWatch Metrics, Auto Scaling, and Elastic Load Balancing in 2009. The first launch provided access to compute power; the second made it possible to use that access to rapidly respond to changes in demand. We have added a multitude of features to all of these services since then, but as far as I am concerned they are still central and fundamental!

Read More