Salesforce, Service, AI and … IoT
AI, IoT, and CRM, three acronyms. However, these three belong together and should not be treated or looked at separately. One important reason for this is that companies and organizations can provide significantly better service experiences and, more importantly, results, by combining the capabilities behind these acronyms. Good field service not only gets dispatched smartly but also equipped with the right parts and, ideally, in a proactive manner. This can get delivered by the combination of Field Service, AI, and IoT data. That’s why I found Salesforce’s early December announcement of having added a component “IoT insights” to its Field Service Lightning product quite interesting. As the press release said, this capability enables service agents and representatives to see IoT signals together with other CRM data, so that the triple p of personalized, proactive, even predictive service is possible. After all, Einstein is embedded into Field Service Lightning for quite some time now. Doing so, Salesforce wisely did not implement yet another IoT platform but enabled its system to ingest data from existing IoT platforms, thus sticking to the core competencies of the company. The solution helps in three areas: Enabling of early issue anticipation (rather than detection, which is responsive) and remote diagnosis Providing agents with more relevant information, to speed up issue resolution And automation via rules and workflows. Says Paolo Bergamo, SVP and GM, Salesforce Field Service Lightning: Let me first clarify that we’re not competing with IoT platforms from the likes of AWS IoT or Azure IoT. Our solution extends the value of these platforms – they provide streams of device data that then flow...
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...