Salesforce Experience Cloud Reviews

There were a couple of different use cases for Salesforce Experience Cloud. One was working for a portal for end users wherein they would see the data of their associated partners and could create forms, submit details, send claims, reimbursements, and so on. This was within the healthcare industry.

The other one was within the real estate industry, and that was for the partners, not the end customers, to view their details such as successfully converted deals, commission calculations, and how those communications were processed.

What I appreciate most about Salesforce Experience Cloud is if you don't have anything particular in mind or don't want to get started with a blank slate, there are various templates available to help develop things for your client. That is something where Salesforce has an edge. Apart from that, how they curate things for partners and customers, how they clearly differentiate it, and how the licenses work for partners and customers is also something great.

Synchronizing department data is also a great point about Salesforce Experience Cloud. If I want to associate any end customers' data to my original CRM, the sync happens very easily. For example, if I am a partner and submit a reimbursement, I want the fulfillment of that reimbursement to be done in my organization which my own people use.

Personalized content is another valuable feature. For instance, if I have multiple partners, such as being a healthcare provider associated with an insurance company, and they have multiple healthcare providers, they can have branding for each healthcare provider within their Salesforce Experience Cloud site.

Wherever we implemented Salesforce Experience Cloud, they were using legacy systems. The customizations we can do using Salesforce Experience Cloud significantly improved the UI/UX. For example, if initially it took 10 minutes to fill out a form, after our customizations it just took three minutes or two minutes. This significant time savings helped them to do more business, resulting in substantial ROI.

There was one area that could be improved regarding document generation within Salesforce Experience Cloud. When submitting a form and wanting to have a PDF copy downloaded within the system, or when doing an integration with DocuSign while generating a document, we faced some challenges. This process could be made smoother.

I have been working with Salesforce Experience Cloud on and off for almost a year.

Salesforce Experience Cloud is 100% stable.

I haven't faced any challenges regarding the scalability of Salesforce Experience Cloud.

The customer service is great. It depends on what sort of partner you are for Salesforce. If there is anything wherein we need technical help from Salesforce, they are always on their toes. This was never a concern.

Positive

I haven't worked with something similar to Salesforce Experience Cloud from other vendors or competitors.

The initial setup was absolutely easy with Salesforce Experience Cloud.

The pricing of Salesforce Experience Cloud is totally fine. While we mainly work on the solutioning part, I haven't faced any problems with the pricing.

I am personally a fan of Salesforce and what they're doing in the Salesforce Experience Cloud area is great. I personally haven't faced any issues there. Salesforce Experience Cloud helps with branding goals effectively. On a scale of 1-10, I rate this solution a 9.

My main use case for Salesforce Experience Cloud is that I have used Health Cloud and Nonprofit Cloud for major medical companies and NGOs. When I open Salesforce Experience Cloud daily, I function as both a Salesforce admin and developer, so depending on the stories and current requirements, I do what is needed. Typically, the first thing I access when working in Salesforce Experience Cloud as an admin developer is the setup tab.

The best features of Salesforce Experience Cloud for my work are the Lightning Web Components, Apex classes, and Flows. Salesforce Experience Cloud has definitely changed how my team works together; it increased efficiency and made collaboration easier.

The biggest friction point I would say is that sometimes it is a bit difficult to debug errors. Currently, for building the Lightning Web Components, it would be faster if we had templates to start with.

I have been familiar with Salesforce Experience Cloud for around one year.

Before I landed on Salesforce Experience Cloud, we managed manually, then we moved to Salesforce Experience Cloud. When I was evaluating options, we considered different tools such as Zoho, but Salesforce Experience Cloud clearly stood out.

When I first implemented Salesforce Experience Cloud, it took time to get things up and running for my team, and we give a weekly report that depends on the stories we are currently implementing. We definitely had a three-month training to get started with Salesforce Experience Cloud.

The scope of that work is not on my own; I work for the company.

In terms of measurable impact, I would rate it nine out of ten. After moving to Salesforce Experience Cloud, I notice an efficiency increase of eighty percent in day-to-day workflows.

Salesforce Experience Cloud has a great impact on my organization. I give this review a rating of nine out of ten.

We are currently working on an Experience Cloud site. It is one site that you can create using Salesforce. It is a normal site where users can log in using their credentials. Their users, such as customers or partners, can process something on their own. It is independent of complete Salesforce. 

While the database is linked to Salesforce CRM, it remains an independent site with an independent URL. The URL can be changed, and it can be used anywhere. Any support team can use it, for instance. They can log into the site, enter the credentials, and perform some process or request. Those actions can be done using Experience Cloud.

By utilizing libraries like the personalization options Salesforce provides, it is easy to incorporate external libraries as needed.

We can create our own design and process requirements, unlike Service Cloud and Sales Cloud, which have standard applications and processes. This allows us to have a completely customized UI and processes tailored to our business approach.

The CSS library of Salesforce is not as customizable as I would prefer. I work with Windows, and the library is not very adaptable. It would be a great feature if Salesforce's library were more customizable according to user needs.

The solution has been used down for one and a half years.

It is stable.

It is scalable.

We aren't having a specified technical support team, but Salesforce has technical support engineers. They have good documentation and written processes for different tasks. If we need to connect with the support team, we raise a ticket.

Positive

I have only worked in the Salesforce ecosystem until now.

The initial setup took around one hour. If the system architecture or design needs discussing, it depends on what is required.

Setup can be done by anyone, but for architects or the main lead developer, they should consider all the scenarios. They should discuss everything with the business to understand the exact requirements and how they can be processed from an architectural perspective.

Implementing Experience Cloud is easier than if we want to create something from React using the same process. It takes less time to create and carry out the processes.

Everything is in the documentation. It is easy to create using the lightning web components.

I'd rate the solution nine out of ten.

We implemented a maintenance app for contractors. Within the Experience Cloud portal, contractors could log in, raise work orders for maintenance requests, and manage those tasks through the portal. Internal users can see specific actions based on criteria such as a request's status.

Salesforce Experience Cloud's community template for quick portal setup was valuable. The ability to set up layouts and create pages on the fly was beneficial. Additionally, the live chat feature and the option for users to view knowledge articles before raising a case were important features.

Some limitations include not being able to hide buttons based on criteria on the portal side and requiring complex workarounds. These limitations are known and are under consideration for future updates.

I used the solution within the last 12 months.

The solution is very stable. I rated it nine out of ten.

Salesforce's scalability is good, and It adapts to general requirements based on thorough market analysis. I rate it eight out of ten in terms of scalability.

Salesforce provides multiple types of support, including free support for configuration-related issues and paid premium support for complex needs. While the time for free support can be longer, their support is professional.

Positive

The initial setup was very easy due to Salesforce's standard templates, which allow for a quick setup of the community.

Salesforce products, including Experience Cloud, are considered high-cost products, especially when comparing global markets.

Before purchasing the Experience Cloud, users need to analyze what the cloud offers. This product is mainly used for portals, and if there are very complex requirements, these should be discussed with Salesforce beforehand.

I'd rate the solution ten out of ten.