{"id":109215,"date":"2018-12-04T10:19:43","date_gmt":"2018-12-04T18:19:43","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/metro-bank-customer-greet-app\/"},"modified":"2024-10-03T10:08:32","modified_gmt":"2024-10-03T17:08:32","slug":"metro-bank-customer-greet-app","status":"publish","type":"power-apps","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/metro-bank-customer-greet-app\/","title":{"rendered":"Metro Bank uses Power Apps to improve the in-store customer experience"},"content":{"rendered":"
Metro Bank<\/a> opened its doors in July 2010 as the first new high street bank to open in London in more than 100 years. Since then they\u2019ve grown to over 50 branches (aka “stores”) serving over a million accounts. In this blog post we take a deeper look at the PowerApps solution that has been deployed across all their stores since December 2017. You can watch a presentation and live demo of the application at the PowerApps general session at Ignite<\/a>.<\/p>\n Metro Bank wanted to differentiate themselves by providing a high quality in-store welcome experience for customers. A key objective was \u2013 \u201cif a customer walks in the door, let\u2019s solve their problem today.\u201d<\/i>\u00a0 This VIP customer service differentiated them from other banks, some of which required appointments to be booked weeks in advance.<\/p>\n They envisioned a scenario where a customer was welcomed by a greeter with an app on a tablet device. The app would help determine with high accuracy the estimated wait time, and pair up the customer with the appropriate representative. The customer could then wait inside the store or leave and be notified via a text message 10 minutes before their appointment.<\/p>\n The historical data created by the app would help train their wait time estimation models, further increasing the accuracy of those estimates, leading to a better store visit experience.<\/p>\n Prior to the Power Platform implementation, the greeter at the bank used a paper clipboard to write down customers names. They had to go back to their desk if they needed to look up customer info in their CRM system. This was not a great customer experience. Moreover, they were unable to accurately predict how quickly a customer could be served as they did not have any data to analyze customer traffic patterns and adapt their staffing accordingly.<\/p>\n They developed a PowerApps tablet app that is used by greeters in the bank to welcome customers and ensure the best possible experience. The app first went live in April 2017 and has been in production and used daily in all 50+ stores since December 2017.<\/p>\n PowerApps<\/b> \u2013 The app allows the greeter to search for the customer, lookup who is waiting, what employees are available, and additional data such as when will the next customer service agent come back from lunch. The app can accurately predict wait times. The customer can choose to wait in the store or leave and be notified via a text message when the teller is available. They can also check wait times in other stores nearby or book an appointment for a following day. Dynamics 365<\/b> \u2013 The solution uses the Dynamics 365 connector to directly connect to the Metro Bank CRM system. All customer information is stored here.<\/p>\n Azure functions<\/b> \u2013 Used to calculate wait times, down to one-minute of accuracy.<\/p>\n The app uses Dynamics 365 Customer Engagement for storing information about queued customers (linked to Contact entity), employee shift patterns (linked to System Users). An Azure Function is used to read this information every minute and simulate the customer handling according to preset rules. The output is the estimated current wait time as well as a per-customer forecast on when each person waiting will be served. A PowerApps Canvas app maintains the queue and service representative availability data, enabling actions such as matching customer with a service representative, and presenting the wait time forecast for any new customer walking into the store.<\/p>\n It took four weeks to develop the first version and was deployed to the first store in two months. The app has now been live in all stores since December 2017.<\/p>\n Storyboard of the customer meet and greet experience<\/em> Welcome screen:<\/p>\n <\/p>\n Match customers (left) with Customer Service Representatives (right):<\/p>\n <\/p>\n Customer Service Representatives use the app to manage their shifts:<\/p>\n <\/p>\n Power platform customer success story – Metro Bank used PowerApps connected to Dynamics 365 to improve the accuracy of estimated wait times and create a more personalized experience when customers walk into the bank. <\/p>\n","protected":false},"author":90,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","power-apps-category":[1580],"power-apps-tag":[1581,1600],"coauthors":[2350],"class_list":["post-109215","power-apps","type-power-apps","status-publish","hentry","power-apps-category-case-studies","power-apps-tag-customer-story","power-apps-tag-dynamics-365"],"yoast_head":"\n\n
\u201cThe ability to build an app within a few days or a few weeks is just fantastic. And then to rapidly get it deployed out to our business is something we’ve not seen before.\u201d <\/em><\/h4>\n
Business scenario<\/h3>\n
Before Power platform \u2013 process, challenges and opportunity<\/h3>\n
Power platform solution \u2013 Meet & Greet app<\/h3>\n
\nCustomer service representatives (CSRs) also use the app to indicate their shift times and lunch breaks. Collectively, this results in a lot of valuable data being made available for analysis and insights.<\/p>\n
\nPower BI<\/b> \u2013 Dashboards are used to gain insights such as average wait times per customer and per CSR. They have exact heatmaps showing stores, days of the week and times of day when they needed to staff up. This was built into their existing Power BI dashboards.<\/p>\nBenefits from using the Power platform<\/h3>\n
\n
Solution architecture<\/h3>\n
From concept to implementation<\/h3>\n
<\/h4>\n
\n
\nOriginal mock-up which was converted into an app using the PowerApps WSIWYG editor<\/em><\/p>\n<\/h3>\n
Additional screenshots<\/h3>\n
Relevant links<\/h3>\n
\n