What I like most about Salesforce Customer Success is the practical guidance and expertise it provides throughout the Salesforce journey. It helps teams drive adoption, solve challenges faster, and continuously get more value from the platform. Review collected by and hosted on G2.com.

The main drawback is that the level of support can vary depending on the service and engagement model. Some resources can also feel broad or require additional effort to find guidance specific to a particular business need. Review collected by and hosted on G2.com.

They are quick and they do log into our site and try to help so they are on the same page. Review collected by and hosted on G2.com.

I do not like that they just chalk it up to limitations. I feel with technology and how we are evolving there has to be a better solution to the smallest obstacles. I would prefer not to export reports and do a lot in excel. I would also prefer not to have limits on filters. Review collected by and hosted on G2.com.

I like the UI framework of Salesforce Customer Success; it's quite user-friendly and that really makes a difference for me. Cloud capabilities are another strong point that encourages me to continue using their services. The methodologies they use and the expertise of my colleagues who work with them are valuable, adding to the overall experience. I also appreciate that I don't feel the need for any significant changes at the moment, as I am quite satisfied with their current services. Review collected by and hosted on G2.com.

Good Review collected by and hosted on G2.com.

Salesforce Customer Success provides valuable expertise, best practices, and proactive guidance that help us optimize our Salesforce environment, improve user adoption, and maximize ROI. Review collected by and hosted on G2.com.

My primary concern is that the value of Salesforce Customer Success can vary based on the level of engagement and available resources. While the strategic guidance is helpful, organizations may still need significant internal expertise to execute recommendations and drive adoption. More prescriptive guidance and measurable success benchmarks would further enhance the experience. Review collected by and hosted on G2.com.

The best solution would be to create a unified customer view that combines customer health, product usage, support cases, engagement, and renewal information. AI can then identify at-risk customers, recommend the next best action, and automate proactive outreach and follow-ups. This would help Customer Success teams move from a reactive approach to a proactive, data-driven customer engagement model, improving retention and customer satisfaction. Review collected by and hosted on G2.com.

I don't have to discuss which I don't like Review collected by and hosted on G2.com.

I use Salesforce Customer Success as a strategic partner throughout the full implementation lifecycle. As an architect and director of technology, the Customer Success team helps ensure clients get maximum value from their investment. I appreciate their proactive approach, particularly around Agentforce and the evolution of agentic AI. The quality of engagement at events like TDX 2026 genuinely reflects Salesforce's culture. The Premier and Signature Success Plans provide direct access to product and engineering, which is valuable for complex multi-cloud implementations. The Customer Success Manager relationship is key, providing quarterly business reviews and early visibility into relevant feature releases, making it genuinely valuable. What stands out most is the quality of the people—knowledgeable, curious, and invested in outcomes. Executive and technical briefings on product direction are invaluable, providing a genuine dialogue that speeds up strategic planning. The proactive roadmap guidance, particularly the Agentforce transition, showcases value by allowing early architectural planning. The team facilitates crucial support during implementations, like resolving a compliance issue in a Data Cloud project within 48 hours, avoiding potential long delays. Their people and guidance make the Customer Success program a genuine asset. Review collected by and hosted on G2.com.

More technical depth at the architect level for complex multi-cloud scenarios. The guidance can occasionally feel optimized for the median customer rather than for the edge cases. In multi-agent Agentforce architectures involving custom Apex invocable actions, Data Cloud real-time triggers, and cross-cloud orchestration, the Customer Success guidance tends to stay at the feature adoption level rather than the architectural design level. Review collected by and hosted on G2.com.

It helps us understand best practices, resolve complex Salesforce challenges, and make better use of the platform. Their guidance helps us improve our processes, adopt new Salesforce capabilities, and find solutions more efficiently. Review collected by and hosted on G2.com.

At times, it can take some effort to find the right resource or expert for a very specific technical question Review collected by and hosted on G2.com.

Users appreciate Salesforce Customer Success most for its fast issue resolution, helpful support teams, and clear insight into customer health. Review collected by and hosted on G2.com.

Users frequently dislike Salesforce Customer Success for its slow response times, inconsistent quality of support, and high costs relative to the value provided Review collected by and hosted on G2.com.

I find the expert coaching and architectural review sessions within Salesforce Customer Success extremely valuable. Having access to specialists allows us to validate our designs before going live, acting as a critical technical catalyst. Immediate access to deep platform expertise eliminates the trial and error phase that typically slows down complex integrations. I also like their alignment with the future of the agentic enterprise. These aspects make me likely to continue or even expand our partnership with them. Review collected by and hosted on G2.com.

One of my biggest frustrations has been the quality and accessibility of the documentation. When I hit an issue in the middle of a workflow—whether I’m troubleshooting an integration, trying to customize a view, or figuring out why a report isn’t pulling the right data—the help articles often read like they’re written for administrators or developers, not for the people using the platform day to day as sales reps. The wording is overly technical, the instructions assume a level of backend knowledge most AEs simply don’t have, and it’s not unusual to work through an entire guide only to realize it doesn’t apply to our specific setup or even our subscription tier. Review collected by and hosted on G2.com.

The depth of technical expertise, direct access to product specialists, and structured guidance around governance and platform scalability are invaluable. They provide proactive recommendations that keep long-term maintenance overhead low. Review collected by and hosted on G2.com.

Engagements can sometimes feel overly framework-heavy or generalized for standard setups, requiring additional effort to tailor recommendations to highly customized orgs or specific architectural edge cases. Review collected by and hosted on G2.com.