Salesforce Health Cloud is a patient and member relationship platform designed to deliver personalized engagement, and provide a complete view of the patient. With Health Cloud, care teams have access to clinical and non-clinical patient and member data including current health conditions and medications, appointment history, communication preferences, and data from the EHR and other systems. Teams are able to work across entire patient and member groups to provide care, faster.
N/A
Salesforce Service Cloud
Score 8.4 out of 10
N/A
Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
When it comes to Health Cloud in other CRM we have to create the related object and fields and we have to set [up] a complete architecture for the healthcare business to run over the CRM. But here Salesforce is proving a managed package, which is Health Cloud, has the framework …
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is …
Zoho is not very real-time, it has limited integration capabilities, and the UI is not very satisfactory for any incoming customer. The performance is slow and impacts the overall customer journey. The data stored in the backend is slightly scattered and needs to be cleaned …
Salesforce is a really great case management tool. Made things a lot easier for our team. Wanted something fairly simple that had a variety of capabilities we could customize.
We used Salesforce for years, Left for Hubspot, and then came back to Salesforce (SF). As they say, don't fix it if it's not broken. Salesforce and customizing were better for us.
Salesforce Service Cloud offers deep integration with our current and expanding CRM data, along with numerous pre-built features that didn't exist in Kayako when we used it. (We used to use an instance Kayako installed in a private cloud environment.) Salesforce Service Cloud …
Zendesk has it's own challenges in terms of Administrator difficulties and a completely different back-end than Salesforce Service Cloud. I would recommend Salesforce Service Cloud if you need a clean database of Companies and Contacts. Zendesk does not excel in overall CRM …
I'm not at the level where I would be part of the decision making process for choosing a vendor or product for the organization. Every position I've held, I've come into a company that has already implemented or is in the process of implementing Salesforce. Honestly I would not …
All of the software's are well established and good, but what gave the edge to us its easy integration capability with other systems, experience cloud integration and Einstein analytics which made us move forward Salesforce. Salesforce also have better service and industry …
The major value proposition is that service cloud offers integrated services. That covers a multitude of lacking features. All of our agents preferred Freshdesk. Salesforce service cloud was lacking so many basic features compared to it that it was frustrating to switch. Simple …
Salesforce service cloud is more configurable than Zendesk and Freshdesk. It has its own inbuilt AI chatbot also which further improves service agent efficiency. Salesforce is more integration agnostic and has pre-built connectors with multiple 3rd party systems. However, in …
We were after a robust and very scalable solution, which could be rapidly implemented. Salesforce Service Cloud not only fitted the bill, but it was much easier to source skills and find on-line learning to help achieve our goals. Although the other technologies could have …
Salesforce allows a lot more visibility and allows us to build better reporting. It is initially trickier to set up and learn, however, comprehensive training and processes have lead to increased customer satisfaction and retention.
Salesforce is lightyears behind Zendesk. You have to be trained as a Salesforce admin to do anything, while Zendesk takes minutes to set up and is actually customer friendly. There are not native telephony options within Salesforce and the tools you use to integrate are …
We previously used a home grown, proprietary system for our needs. This started to get costly and clunky as our database grew. We ended up going with Salesforce because they are purely cloud based. They also have a large footprint and very robust solution so they help us …
Customer Success Support Specialist, EF Corporate Solutions
Chose Salesforce Service Cloud
Well, I worked with SAP in the past when I was in other companies. It was way more complex and not user-friendly. You had to take a lot of steps in order to accomplish simple tasks and not everyone could work at the same time in the same program. I would 100% recommend …
Zendesk changed their agreements making us unable to continue with them due to our agreements with our customers. SalesForce allowed us to maintain our customer agreements.
I used other products in another company as a database and can say that Salesforce Service Cloud is much more user friendly for customer service needs and makes work faster to process than the named program before. Integration between departments is more clear and simple to …
The best scenario [is] that it has [a] particular object which can directly store the records of the client [who] has purchased the policy and practitioner details with [their] expertise. The users can directly book the appointment using LWC or Aura components which can be exposed on websites. The object will be linked with each other [using] a lookup relation which creates a complete framework to handle the cases and details of the clients, [their] policies, and other details as well. Booking or finding a practitioner can be done with the [Salesforce] Health Cloud app where it can use [your] current location and provide details of [available] nearby doctors. Health Cloud supports live agent as well where a user can get the details on his insurance policy and get other help if he need from the chat option with live agent.
This cloud is a good option for attracting large numbers of customers for mid-scale and large-scale organizations. However, it’s not suitable for small companies or startups due to its high cost. For use cases where real-time input from customers is taken and then processed on the cloud to give them output, this platform is a must.
[There] are particular objects such as person accounts which [are] linked with [health care company accounts if they have a policy].
We have flows and pages where a user or client can book [their] appointment with a practitioner and get instant help by raising a case or request for [an] appointment.
[Salesforce] Health Cloud keeps all the records of clients and practitioners and can link them when and where ever needed.
Objects in the managed package have [a] standard field which gives a perfect solution with out-of-the-box functionality without creating such a model or structure.
We can raise cases or requests and [use] automation tools like flows [so] the case will be assigned to [a] practitioner or the queue of the user.
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
The software offers a wide range of functionality, which I truly appreciate. However, there is so much there that a lot of drilling into information can be required. This can create a significant learning curve for new users.
I love that the Salesforce Service cloud provides all of the functionality that I need when implementing business processes for our customer support representatives. It even has enough functions and features that allow us to customize and expand upon our current processes, giving us the ability to go above and beyond what we've thought we could ever do. Using cases coupled with Salesforce's automation tools help ease the workload and keeps our data integrity intact.
Salesforce's Trust Center clearly communicates occasional issues to anyone who subscribes, down to an organization's cloud instance. Bundled sandboxes ease updates, and seasonal upgrades are seamless, scheduled well in advance with plenty of information about what's coming. Support agents have noticed intermittent Omni-Channel disconnects due to internet connections, and these are clearly notified.
Load times can be slow, but this is also based on how much customization you have done. We added a lot of custom fields which could cause additional slowness in loading. This was never anything that affected our overall efficiency. I did not notice that Service Cloud slowed down any of the systems we had it integrated with
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is expensive as well.
We have cut our service team in half over the past 5 years due to the efficiency of the tool
The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person