The Secret Sauce of Success – Recipe unveiled by the DC Office of Unified Communications
Back in 2015 the Washington D.C. Office of Unified Communications (OUC) started a re-platforming exercise of their backbone from an on premise system to a cloud based customer service solution. The Washington, D.C. Office of Unified Communications manages non-emergency services for 311 callers across the District of Columbia, supporting 17 different agencies, including the Department of Transportation, the Department of Public Works, the Department of Motor Vehicles, and more. The OUC also manages emergency services for 911 callers. One of the main reasons for this re-platforming was the downtime challenge inherent to all on premise platforms: They need to be upgraded regularly, which causes service degradation or even unavailability. Other reasons included insufficient and slow reporting capabilities as well as the need to add more self-service channels. Having strong reporting and analytics capabilities are crucially important for call centers. The biggest thing for them is the answer and solution rate, which needs to be as high as possible. Additional self-service channels were necessary to be able to cope with the influx of requests and to both, improve customer satisfaction and modernize the customer experience. To further achieve the latter, a chat service and social media channels like Facebook, Instagram and Twitter have been added to the 311 services. All of these challenges have been addressed by migrating to a software solution based upon the Salesforce Service Cloud, along with some organizational measures. Being a main KPI, the answer wait time has been drastically reduced from 7 minutes to a mere 31 seconds. Doesn’t sound good to you? Consider that the service still serves 1.8 million calls per year with...
Einstein smartens up Salesforce Service Cloud
The News A few days ago Salesforce released a new iteration of its Service Cloud Einstein after infusing its artificial intelligence, Einstein, into the Service Cloud in February 2017. This release comes with three major enhancements to the Service Cloud: Einstein Bots for Service Lightning Flow for Service Einstein Next Best Action Einstein Bots for Service is providing the ability to easily configure chat bots that enable instant response to customers and a seamless handoff to customer service agents. Lightning Flow for Service gives companies the ability to automate processes with contextual, step-by-step guidance for fulfilling requests and resolving issues, using a graphical interface. Einstein Next Best Action is delivering intelligent recommendations and offers on any channel to increase customer satisfaction. While Einstein Bots for Service and Lightning Flow for Service are in General Availability since July 11, 2018, Einstein Next Best Actions will remain in a Pilot phase for some more time. The reason for this is that Salesforce wants to be double sure that this functionality is reliable. It needs a good amount of data and a good training set. And Salesforce cannot look into the data. The bots themselves do need to get trained and, once active, take feedback from the service agents. All three features work hand-in-hand. Salesforce uses a credit card scenario to make this point. When a customer goes to the web site for help the chat bot takes over and gathers the necessary contextual information and then escalates the issue to a customer service agent who continues the chat at the position the chat bot exited with all information available. A Lightning...
SAP CRM for S/4HANA – News from the Customer Frontier
It has been a little more than half a year now that I didn’t update on what is going on with SAP CRM and S/4HANA (which I will refer to as S/4 from now on; SAP it is time for you to change the unwieldy name to something more manageable). What Happened – So Far As you are well aware SAP is working on integrating a simplified version of SAP CRM into S4. The original roadmap offered a first customer release of an integrated product in early 2018, based on the September 2017 release of S4. The integration was planned as an add-on to S4. The initial scope of this CRM add on for S/4 was supposed to cover what is referred to as ‘core service’ functionality. This initial release shall be followed by ‘core sales’ functionality later in 2018. 2019 then is supposed to be dedicated to another round-off release covering further sales and service functionality, including loyalty management and migration tools. Roadmap and statements also so far have been fairly fuzzy about the strategic distinction between CRM as a part of S4 and the SAP Hybris line of CRM- and CEM systems. What does the Future have in its Basket? As it seems now, the release is not going to happen as fast as planned, nor in the originally planned way. Instead, in a webinar recently held for partners, SAP ‘announced’ two very interesting changes, with the second one likely also being a consequence of the first one. SAP CRM will no more be referred to as an add-on to S/4 but, at least for the service...