Gaining Insight by Mining Simple Rules from Customer Service Call Data

Although the goal for most predictive analytic problem is to make prediction, sometimes we are more interested in the model learnt by the learning algorithm. If the learnt model could be expressed as s set of rules, then those rules  could be source of valuable insight into the data. For most Machine Learning algorithms, the learnt model is a black box and can not be interpreted in an intuitive way. However, Decision Tree is an exception. Decision Tree result is essentially a set of rules. There are few other rule extraction algorithms.

In this post I will cover solutions for mining simple rules based on one attribute only. It’s quick and dirty way of gaining insight into data. The solution is part of my open source project avenir. The implementation is in Hadoop. I will also discuss more complex rule mining algorithms based on Decision Tree and other algorithms.

Solution Strategy

The solution is two fold. First, we want to find how relevant the feature attributes are. A feature is relevant to prediction if it’s highly correlated to the class variable and weakly correlated with other feature variables. The features relevance is calculated based on entropy and mutual information. All the technical details can be found in my earlier post.

Second, once we have determined the relevance of the feature attributes we want to identify the values of the feature attributes that correspond to the positive or negative value of class attribute value.  In other words we want to find out how particular feature variable value discriminates between positive and negative class variable outcome

Various statistical scores are calculated based conditional distribution of the feature variables. They are as follows.

  1. Odds ratio
  2. Distribution  difference
  3. Minimum risk
  4. KL divergence

The underlying theme for all these techniques are the same. We take two conditional distribution values for the value of feature variable, one conditioned on the positive class variable value. and the other based on the negative class variable value.

Then we calculate a parameter, based on the the one of the 4 parameters listed above,  which reflects the difference between the conditional distribution values. I would call this discrimination score. The more extreme the value  of the score, the more discriminative power the particular feature variable value has in predicting the class variable. A high value corresponds to positive class variable and a low value corresponds to negative class variable.

Here are the detailed definitions of the statistical parameters listed above. They are defined for some feature variable xi. The class variable has the values t and f.

oddsRatio = ((pt) / (1 – pt)) / ((pf) / (1 – pf))
distrDifference = pt – pf
minRisk = pt (1 – pf)
klDivergence = pt log(pt / pf)
pt = p(xi | t)
pf = p(xi | f)
xi = ith feature variable
t, f = class variable values

Rule Definition

A rule has the following components. A rule is based on a set of numerical and categorical attributes.

  1. A rule has an antecedent and a precedent
  2. A rule antecedent  is a conjunction of predicates.
  3. A predicate contains an operand, operator and a value. In the rule age le 30, age is the operand, le (less than) is an operator and 30 is the value.
  4. A rule precedent is a class attribute value

In the context of a Decision Tree, a rule is a path from the root to the leaf of the tree.   All the nodes up to the leaf node constitute the antecedent of the rule. Each internal node corresponds to a predicate in the rule. The leaf node is the consequent of the rule, which contains the class attribute value.

Since we are working with rules involving only one feature attribute, our rules will have only one predicate.

Call Center Data

I will use call center call data and the related prediction problem is to predict whether the customer will hangup the call after the call is put on hold. The prediction could be used in various ways to improve the customer service experience. For example, if the customer is high value, the customer call could be re routed, so that more expedited service could be provided.

Here are the attributes of the call data. Customer ID is not used in the analysis. The last variable hungup is a binary variable which is the class variable.

  1. Customer ID
  2. Customer type
  3. Area code
  4. Issue
  5. Tome of day
  6. Hold Time
  7. Hungup

Here is some sample input data. The data is for the call center of a fictitious cable and internet service provider company.


The last field is cal variable i.e whether the customer hung up or not. The first field which is customeID is ignored in the analysis.

Relevance Analysis

Here are the results from relevance analysis. There are various algorithms for relevance score. I have used something called Joint Mutual Information. The first field is the attribute column index. The second field is the relevance score. Higher score indicates higher relevance.


Here is list of the feature attributes sorted by the relevance score in descending order.  As expected, hold time seems to be the most important predictor for call hang up. Next is the time of the day for the call. The people may behave differently depending on whether the call came in the morning or afternoon.

hold time 0.135
time of day 0.088
customer type 0.082
area code 0.061
issue 0.028

The output of relevance analysis has the following 3 parts. Distribution and mutual information are secondary output.

  1. Distribution and conditional distribution
  2. Mutual Information
  3. Relevance score

Class conditional distribution data is used as input to the discrimination analysis map reduce input.

Discrimination Analysis

In the next phase, we calculate the discrimination score for different values for each feature attribute. The Map Reduce implementation class is CategoricalClassAffinity. All the results are based on odds ratio. Let’s take a look at the feature variable holding time .


The first field is the feature attribute index. The second field contains the value of the feature variable, which is hold time in minutes and the last field is the discrimination score. Hold time of 8 minutes seems to be the strongest predictor for hang up. Interestingly higher hold time of 9 or 10 minutes are weaker predictors.

This is surprising, since one would think that a higher wait time will make it more likely for the customer to hangup. But let’s not forget that there are other variables involved and we are trying to make prediction based on one feature variable.  Maybe some customers may be willing to hold for longer time and not hang up, because of the issue they have.

Let’s look at another feature variable customer type which is either residential or business. Here is the result.


Here we find that residential customers more likely to hangup. Business customers are willing to stay on the line, possibly because resolving a service issue is more critical for a business. 

Rule Mining

The solution described so far only extracts rules based on one feature attribute. For mining rules based on multiple feature attributes as a conjunction of predicates, here are some of the popular solutions. I have plans to implement them.

  1. Decision tree
  2. CN2 
  3. Rise

Decision trees follow a strategy of generalization to specialization. Any path from the root of the tree to the leaf is a rule. There will be as many rules as the number of paths.

With CN2, one decision path at a time is built. After a path is created, all the data that match with the rule corresponding to the path are are removed and the process is repeated to find the next path.

Rise follows a strategy of specialization to generalization. Initially each data point is a rule. A rule is generalized is a such a way that the data point nearest to a rule is matched by the generalized rule.

Wrapping Up

I want to reiterate that we have gone through a solution of for singe attribute based rule mining. It’s a quick and dirty way to gain some insight on data. As I alluded to earlier,  for more rigorous rule mining. one of the algorithms listed earlier should be used. There is a tutorial available that documents all the steps necessary to run this use case.

For commercial support for this solution or other solutions in my github repositories, please talk to ThirdEye Data Science Services. Support is available for Hadoop or Spark deployment on cloud including installation, configuration and testing,


About Pranab

I am Pranab Ghosh, a software professional in the San Francisco Bay area. I manipulate bits and bytes for the good of living beings and the planet. I have worked with myriad of technologies and platforms in various business domains for early stage startups, large corporations and anything in between. I am an active blogger and open source project owner. I am passionate about technology and green and sustainable living. My technical interest areas are Big Data, Distributed Processing, NOSQL databases, Machine Learning and Programming languages. I am fascinated by problems that don't have neat closed form solution.
This entry was posted in Big Data, Data Science, Hadoop and Map Reduce, Machine Learning, Rule Mining and tagged , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s