aheadCRM

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 Light

The suite is back. I have said and written that a good number of times in the past few years. And that is a good thing (that the suite is back, not that I said it, of course), because one of the major challenges with a best of breed approach is integration. The suite is back, but it is in an incarnation that vastly differs from what we knew about suites back in the times before cloud computing and Salesforce brought back a supremacy of best of breed over the suite. Integrating different pieces of software from different vendors into one coherent whole is easily accounting for one third to one half of project budgets. And this part of the overall cost for implementing new software is often plaid down by best of breed vendors. Which is not a crime, especially if the benefits of the best of breed software outweigh the cost of integration. However. Often it does not. And not openly addressing cost of integration backfires. Always. Believe me. If you res