Postgres
Experience
Service
<!--NOLIM--><!--NLM011--><!--settings{"applyTo":"1","elemClass":"animat"}settingsend--> <script> (function(){ function t_ready(e) { "loading" != document.readyState ? e() : document.addEventListener ? document.addEventListener("DOMContentLoaded", e) : document.attachEvent("onreadystatechange", function() { "loading" != document.readyState && e() }) } var t396_waitForFinalEvent = function() { var e = {}; return function(t, n, o) { o || (o = "Don't call this twice without a uniqueId"), e[o] && clearTimeout(e[o]), e[o] = setTimeout(t, n) } }(); function checkscale() { let e = document.querySelectorAll(".t396__artboard_scale .animat .tn-atom"); Array.prototype.forEach.call(e, function(e) { let t = window.getComputedStyle(e.closest(".tn-atom__scale-wrapper")).transform; if(t!='none') { e.closest(".tn-atom__scale-wrapper").style.removeProperty("transform"), e.closest(".animat").style.transform = t } }) } t_ready(function() { if (window.isFirefox || window.isOpera) { let e = document.querySelector("body"), t = document.createElement("style"); if (e.appendChild(t), t.setAttribute("id", "nlm011delete"), t.type = "text/css", t.styleSheet ? t.styleSheet.cssText = ".animat{display:none!important;" : t.appendChild(document.createTextNode(".animat{display:none!important;")), document.querySelectorAll(".t396__artboard_scale").length > 0) { let elList = 0; let count = 0; let int = setInterval(function() { let e = document.querySelectorAll(".t396__artboard_scale .animat"); let elList2 = e.length; if (elList == elList2) { count += 1; if (count == 3) { clearInterval(int); if (e.length == document.querySelectorAll(".t396__artboard_scale .animat .tn-atom").length) { checkscale(); setTimeout(function() { checkscale(); }, 0); let e = document.querySelector("#nlm011delete"); null !== e.parentNode && e.parentNode.removeChild(e), window.addEventListener("resize", function(e) { t396_waitForFinalEvent(function() { window.isMobile ? document.documentElement.clientWidth !== window.tn_window_width && checkscale() : checkscale() }, 500, "resizeruniqueid") }, !0); window.addEventListener("orientationchange", function() { t396_waitForFinalEvent(function() { window.isMobile ? document.documentElement.clientWidth !== window.tn_window_width && checkscale() : checkscale() }, 500, "resizeruniqueid") }); } } } else { count = 0; elList = elList2; } },50); } } }); })() </script> <style> .animat{ overflow:hidden!important; } </style>
The customer gathered their client information from their site to Postgres database and information about the client and their neighborhood, neighborhood area wasn’t normalized and the customer wanted to have a complex decision logic on whether to create a lead or account and contact from the database information. This led to the impossibility of uploading this information into Salesforce using standard API.
Lack of integration between their Postgres database and Salesforce and manually entering customer information from the website into Salesforce on a daily basis.
The customer wanted to modify the out-of-the-box Knowledge cards available on the Salesforce Experience Self-Service portal.
Lack of an automatic, quick and clear, process for managing leads and allocating them to agents available at a given time.
Lack of a tool to connect the phone to a computer where customers can have conversations with customer service professionals who, in turn, can quickly manage and track customer cases.
According to the business logic and requests, the Vimera team proposed using Sales, Service Cloud and Experience clouds as the solutions.
Since the stored data in Postgres wasn’t normalized and the logic of creation of either Lead or Account was complex, the Vimera developer implemented a custom Apex Web service, created a Connected App in order to integrate their database with Salesforce and created an API documentation on RAML. Also, the Vimera team designed and implemented a data model for neighborhood logic. As a result, all tables have been normalized in Salesforce.
To achieve effective support services, and improve client centricity, loyalty program and trustworthy reputation, the Vimera team configured a skill-based Omni-channel with secondary routing, set up a Knowledge article base and migrated it to Salesforce, and configured a Self-service portal that included a Knowledge base and Web-to-Case form, configured Email-to-Case. Also, the Vimera team configured Computer telephony integration (CTI), a cloud-based telephone system in Salesforce.
The Vimera developer implemented automation of tasks and events to redirect the sales managers' team on high-priority tasks.
The Vimera developer overridden the Experience Cloud CSS styles to hide some standard Knowledge article attributes that the customer didn’t want to see on UI.