Salesforce Experience Cloud Reviews

Salesforce Experience Cloud's main use case for us is building secure customer and partner portals that enable self-service and improve collaboration. We use it to allow customers to create and track support cases, access knowledge articles, manage their profiles, and interact with our support team. On the partner side, it helps users access shared records, collaborate on opportunities, and securely exchange business information. My role involves customizing the portal using Experience Builder, Lightning Web Components, Apex, and Flows.

Salesforce Experience Cloud's best feature is its ability to build highly customizable and secure customer and partner portals on the Salesforce platform. Experience Builder stands out because it allows us to create and modify portal pages quickly with minimal effort. Another strong feature is the seamless integration with Salesforce data, which makes it easy to expose standard and custom objects to external users while maintaining security through profiles, permission sets, and sharing rules. The platform also supports Lightning Web Components, Flows, and Apex, giving developers the flexibility to build custom functionality while keeping the user experience responsive and scalable. Overall, it provides a good balance between low-code configuration and advanced customization.

Salesforce Experience Cloud has had a significant positive impact on our organization by providing customers and partners with a secure self-service platform. It reduced the number of manual support requests because users could create and track cases, access knowledge articles, and manage their own information online. This improved response times and increased customer satisfaction. From an internal perspective, it streamlined collaboration between teams, reduced administrative effort, and enabled faster delivery of services.

Salesforce Experience Cloud is a strong platform, but there are a few cases where it could improve. One area is performance. Pages with many custom Lightning Web Components or complex data retrieval can sometimes load slowly and require additional optimization. The initial setup and configuration can also be challenging for organizations with complex security and sharing requirements. I would like to see more out-of-the-box templates and UI customization options to reduce development effort for common portal use cases. Finally, troubleshooting and debugging issues for external users could be more straightforward with enhanced diagnostic tools and logging. These improvements would make the development and maintenance even more efficient.

I would also appreciate improvements to documentation and debugging tools, especially for complex implementations involving custom components and integrations. Better monitoring and more detailed error logs for external users would help developers identify and resolve issues more quickly. In addition, having more pre-built, industry-specific templates and reusable components would reduce implementation time and make it easier for organizations to launch new portals. Overall, the platform is highly capable, but these enhancements would improve both the developer experience and long-term maintenance.

I am using Salesforce Experience Cloud. I have been using it for two and a half to three years as part of my overall Salesforce development experience.

Salesforce Experience Cloud is very stable in my experience. We have not faced any major stability issues, and the platform has been reliable for day-to-day operations and production workloads.

Salesforce Experience Cloud is highly scalable. It can support growing numbers of users, portals, and business requirements without significant issues. As an organization grows, it is easy to add new features, users, and integrations while maintaining performance.

I have had some interactions with Salesforce support. Overall, the support experience has been good. They are responsive and knowledgeable, especially for critical issues, although some complex cases can take longer to resolve.

We previously relied on a custom portal with manual processes. We switched to Salesforce Experience Cloud because it offers better integration with Salesforce, stronger security, easier customization, and a much better self-service experience for customers and partners.

Overall, the onboarding process was fairly smooth since our team already had experience with the Salesforce platform. Adopting Salesforce Experience Cloud was straightforward. The low-code capabilities in Experience Builder helped us to start quickly, while developers could extend functionality using Lightning Web Components, Apex, and Flows whenever needed. Salesforce also provides good documentation and Trailhead learning resources, which helped new team members ramp up. The main learning curve was understanding the external user security, sharing rules, and license models, but once those concepts were clear, the team was able to work efficiently.

We saw a positive ROI by reducing manual support efforts and increasing customer self-service. Although I do not have exact metrics, we experienced improved operational efficiency, faster case resolution, and better user satisfaction.

Overall, I found the pricing reasonable for the features it offers, but licensing can become expensive for organizations with a large number of external users. The setup process was straightforward with proper planning, and overall, it provides good value for enterprise portal solutions.

We evaluated Microsoft Power Pages and custom web portal solutions before choosing Salesforce Experience Cloud. We selected Salesforce Experience Cloud because of its seamless Salesforce integration, strong security, and faster development capabilities.

One thing I found particularly valuable was how flexible Salesforce Experience Cloud is when it comes to customizing the user experience while maintaining security. In one project, we needed to support different types of external users with different levels of access. We implemented role-based access using sharing rules, profiles, and permission sets, while customizing the portal with Lightning Web Components to meet specific business requirements. One challenge was ensuring users could only see the records relevant to them without affecting performance. We addressed this through careful sharing model design, optimized SOQL queries, and thorough testing. The end result was a secure, scalable portal that significantly improved the overall user experience.

I would also mention the platform's scalability and flexibility. As business requirements evolve, it is relatively easy to extend the portal by adding new pages, components, and automations without redesigning the entire application. I appreciate the mobile-responsive design and the ability to integrate with other Salesforce products and external systems through APIs. From a developer's perspective, the combination of declarative tools through Flows and Experience Builder and custom development using Lightning Web Components and Apex makes it easier to deliver solutions that are both maintainable and aligned with business needs.

Salesforce Experience Cloud offers excellent customization capabilities. We can build highly tailored customer and partner portals using Experience Builder for low-code development and extend functionality with Lightning Web Components, Apex, Flows, and custom integrations whenever business requirements become more complex.

Salesforce Experience Cloud integrates very well with other systems because it is part of the broader Salesforce ecosystem. In our projects, we have integrated it with external applications using REST API, Platform Events, named credentials, and middleware where required. It also works seamlessly with Sales Cloud, Service Cloud, and standard Salesforce objects, allowing data to flow smoothly between internal users and external portal users. One of the biggest strengths is the flexibility to support both declarative and programmatic integration depending on the business need. The main challenge comes when integrating with legacy systems or external applications that have complex authentication or limited API support.

The user experience is one of the strongest aspects of Salesforce Experience Cloud. For customers, it provides a secure and intuitive self-service portal where they can create and track support cases, access knowledge articles, update their profiles, and view relevant information without contacting support. For partners, it enables secure collaboration by providing access to shared opportunities, accounts, reports, and other business data based on their permissions. The platform is mobile-responsive and offers a consistent experience across devices. From a development perspective, Experience Builder and Lightning Web Components allow us to create a modern, branded interface that aligns with business requirements.

Salesforce Experience Cloud supports regulatory compliance through its strong security and governance features. In our organization, we use role-based access, profiles, permission sets, sharing rules, field-level security, and object-level permissions to ensure users only access data they are authorized to see. We also leverage audit trails, login history, and secure authentication features such as single sign-on and multi-factor authentication to help meet organizational security and compliance requirements. Since Salesforce Experience Cloud runs on the Salesforce platform, it also benefits from Salesforce's enterprise-grade security standards and regular platform updates.

We manage user roles and permissions using Salesforce's standard security model. Based on the user type, such as a customer, partner, or internal user, we assign the appropriate Salesforce Experience Cloud license, profile, and permission sets. We use roles and sharing rules to control record-level access, while object-level and field-level security ensure users can only view or edit the data they are authorized to access. For more specific business requirements, we use permission set groups to simplify permission management and Flows or Apex for dynamic access where needed.

We typically handle branding and theming using Salesforce Experience Builder, along with custom branding assets. We customize the portal by applying the organization's brand colors, logos, fonts, page layouts, and navigation to create a consistent user experience. For more advanced requirements, we build custom Lightning Web Components and use CSS to achieve unique designs while maintaining responsiveness across different devices. We also create reusable components to keep the design consistent throughout the portal. One tip I would recommend is to establish a clear design system with reusable styles and components from the beginning.

We monitor and maintain our Salesforce Experience Cloud portals using a combination of Salesforce's built-in monitoring tools and development best practices. We regularly review debug logs, login history, event monitoring, and setup audit logs to identify issues. We also monitor Apex jobs, API usage, and integration logs to ensure everything is running smoothly.

My advice is to clearly define your business requirements before implementation and plan your security model carefully. Make good use of Experience Builder, Flows, and Lightning Web Components, and follow Salesforce best practices. With proper planning, Salesforce Experience Cloud is a scalable and powerful platform for building secure customer and partner portals.

Salesforce Experience Cloud is a powerful platform for building customer and partner portals with strong integration capabilities across the Salesforce ecosystem. It provides flexibility, scalability, and customization options to create a personalized digital experience. Organizations should plan their implementation carefully and invest time in configuration and user adoption to get the maximum value from the platform. I would rate this solution a nine out of ten.

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.