Using Net Promoter Score to help improve customer experience

Com­pa­nies are con­tin­u­al­ly look­ing for ways to improve the cus­tomer expe­ri­ence they pro­vide and to put their cus­tomers at the heart of every­thing they do. A pop­u­lar strat­e­gy to help achieve this is to lis­ten to the Voice of the Cus­tomer, by ask­ing for feed­back on their experience.

How­ev­er, to get the best results from a Voice of the Cus­tomer pro­gram, com­pa­nies need to make sure they ask the right ques­tion, at the right time, in a way that is rel­e­vant to the con­text of the user inter­ac­tion. They also need to ensure that they can apply the customer’s feed­back to actu­al­ly dri­ve improve­ment in the cus­tomer expe­ri­ence — i.e. to make the cus­tomer feed­back action­able.

For the last 12 months I have been work­ing with one of the worlds lead­ing tele­coms com­pa­nies on their voice of the cus­tomer strat­e­gy. The fol­low­ing arti­cle looks at the chal­lenges we faced in this pro­gram, and how we addressed them.

Chal­lenge 1: Ask­ing the right ques­tion. We have all seen lengthy web sur­veys where there is always one more ques­tion to answer. How­ev­er, go too far in the oth­er direc­tion, ask­ing only very gener­ic ques­tions, and the response will lack focus.

To ensure we only present short sur­veys that are not too much trou­ble for the cus­tomer to both­er respond­ing to, we made use of Net Pro­mot­er Score, a method­ol­o­gy that boils all the ques­tions you may want to ask into 2 sim­ple ques­tions – a score and a free text response.

Net Promoter Score - 2 simple questions

By com­bin­ing the response to these ques­tions with oth­er infor­ma­tion about the cus­tomer – what they were doing before and after sur­vey, why they were sent the sur­vey and oth­er data such as CRM or sales infor­ma­tion, we can asso­ciate their response with where they are in the user jour­ney. This allows us to under­stand their response in the con­text of their most recent inter­ac­tion with the com­pa­ny – the cus­tomer TouchPoint.

Chal­lenge 2: How to col­lect feed­back con­sis­tent­ly across the cus­tomer jour­ney. So dif­fer­ent respons­es can be com­pared, we need­ed to stan­dard­ize the way in which cus­tomer feed­back to col­lect­ed, processed and ana­lyzed. By using the same sur­vey ques­tions (NPS ques­tions) across all chan­nel and all stages in the user jour­ney, we can ensure results at dif­fer­ent stages in the cus­tomer jour­ney or on dif­fer­ent chan­nels can be compared.

This allows us to answer ques­tions like which ser­vice chan­nel deliv­ers the high­est lev­el of cus­tomer sat­is­fac­tion (web self ser­vice, call cen­tre, social, face 2 face etc. )? Why do peo­ple pre­fer that chan­nel? What about mul­ti-chan­nel experiences?

How­ev­er, the method of col­lect­ing the cus­tomer respons­es also needs to be stan­dard­ized to ensure they are com­pa­ra­ble. In this case we used a com­bi­na­tion of web and SMS based sur­veys, both ask­ing NPS sur­vey ques­tions with exact­ly the same word­ing. By using near real time (with­in 30 min­utes) trig­gers to ini­ti­ate pre­sen­ta­tion of the sur­vey, response rates were dra­mat­i­cal­ly increased. By using auto­mat­ed sur­vey trig­gers, vol­umes could be scaled far high­er than tra­di­tion­al “clip­board” or call cen­tre cus­tomer surveys.

**Chal­lenge 3: Sort­ing, cat­e­go­riz­ing and attribut­ing the dri­vers for pos­i­tive and neg­a­tive expe­ri­ences. **Once we had the foun­da­tions in place – what we were going to ask and how we were going to ask it — we need­ed to look at how we would process the respons­es. Here, we worked close­ly with the Adobe Part­ner, Clarabridge.

By using Clarabridge’s Nat­ur­al Lan­guage Pro­cess­ing (NLP) capa­bil­i­ty, we were able to process each sur­vey response to:

Chal­lenge 4: Get­ting a com­plete pic­ture. Through the com­bi­na­tion of robust, scal­able sur­vey col­lec­tion; auto­mat­ed pro­cess­ing and cat­e­go­riza­tion of the respons­es using Clarabridge; and match­ing sur­vey respons­es with oth­er sources of cus­tomer data (e.g. web and mobile behav­iour­al data from Adobe Ana­lyt­ics, social data from tools such as Adobe Social and oth­er sources of data such as the CRM sys­tem, Point of Sale data and IVR/call cen­tre records); we can pro­vide a com­plete pic­ture of the user’s seg­ment, actions and feel­ings as they moved through the cus­tomer journey.

This data, that com­bines qual­i­ta­tive voice of the cus­tomer feed­back with quan­ti­ta­tive data about actions tak­en, allows us to visu­al­ize any trends in the cus­tomer expe­ri­ence, to quick­ly high­light any prob­lems in real time, and apply busi­ness rules to the result to iden­ti­fy indi­vid­ual pieces of cus­tomer feed­back that need­ed reply or fol­low up.

As the pro­cess­ing of the free text “why” respons­es in Clarabridge pro­vides quan­ti­ta­tive data as the out­put (sen­ti­ment, NPS dri­vers, busi­ness cat­e­go­ry) this data can eas­i­ly be com­bined with oth­er sources of data (the NPS score, cus­tomer jour­ney stage, cus­tomer actions, demo­graph­ic, geo­graph­ic and con­tract data etc.) to give a com­plete data set for deep­er analysis.

Togeth­er these sources of data pro­vide both a macro view of the “big issues” or com­mon trends, and a micro­scop­ic view of indi­vid­ual cus­tomer prob­lems or challenges.

Chal­lenge 5: Clos­ing the loop with the cus­tomer. The final piece of the puz­zle was how to use this Voice of the Cus­tomer feed­back to actu­al­ly improve the cus­tomer expe­ri­ence and to guide busi­ness change.

Using busi­ness rules that look for com­bi­na­tions of cer­tain cus­tomer types, com­ments, dri­ver cat­e­gories and/or NPS scores, we can mark cer­tain sur­vey respons­es as need­ing fol­low up. The fol­low up action can then be man­aged using a light weight dash­board UI pro­vid­ed to NPS task forces, or the data about the feed­back and required fol­low up action can be fed into a CRM or work­flow tool.

Closed Loop Net Promoter Score Management

Closed Loop Net Pro­mot­er Score Management

The solu­tion put in place for this cus­tomer to address these chal­lenges, the Touch­Point Solu­tion, con­sists of 3 func­tion­al parts:

The TouchPoint Solution

The fol­low­ing is an exam­ple of the closed loop dashboard:

Closed Loop NPS Dashboard

In sum­ma­ry the Touch­Point solu­tion helps:

If you’re inter­est­ed in devel­op­ing a sim­i­lar strat­e­gy for your com­pa­ny, please get in touch with me.