It is not a question of “if” it is only a question of “when” you will start deploying chat and chat automation at your bank. It should be on your radar screen for several reasons, the first of which is that it will soon be the fastest growing and the most preferred communication channel among your customers. That trend got a boost when Apple announced last week the production release of its Business Chat product.
Assume for a second that your bank screws up and causes a problem. The customer comes in or calls to complain - Do you apologize? Of course, you do – but then what? For the most part, community banks are fantastic and solving problems and making customers happy. What comes after an apology for a bank is mostly natural. However, given the rise of data analytics, now there is starting to be a science. In this article, we explore what it quantitatively takes to not only restore customer satisfaction but to make it better than before.
In past articles, we have talked at length about using agile methodology for application development, for technical product innovation, and for your risk processes. We are fans of forsaking the traditional “waterfall” approach for new products whenever possible and getting to marketing in a pilot program as quickly as possible so you can learn and iterate to success.
In our third and final part of mobile banking app usability testing, we looked at the top 25 major banks, and reduced their mobile banking app to a set of design elements and then turned 60+ designers loose to get creative and come up with variations that fit our brand. We then took various aspects of each design and tested each before 415 customers and potential customers. We looked at usability and asked them to rate each feature. In each case, we chose a base case and then compared variations for usage and desirability by each customer.
After getting frustrated with not being able to find usability data for mobile banking, we gathered 415 customers and potential customers to ask them what they thought of a variety of features. The results surprised us. We presented some of our findings earlier this week, and now we present Part Two of three covering four more specific topics. In each case, we chose a base case and then compared variations for usage and desirability by each customer. The numbers below are the percentage points difference, positive or negative from the base case (Version A).
If you are looking to improve your banking app, you will find that everyone has opinions, but few people have data. Even the specific app design shops or user experience “experts” largely have design experience but have never applied any rigor to figuring out what banking customers want. Given this issue, we decided to take it upon ourselves to convene 415 customers and potential customers in order to get their opinion and usage data on what features and design they like the best.
A couple weeks ago we walked into a community bank conducting a customer persona exercise. We were impressed, but quickly noticed that not all of senior management were believers. The question arose, what is the value of a quality customer experience at a bank?