Salesforce Go
Salesforce Go is a Setup-based feature discovery and implementation platform designed to help Salesforce administrators streamline configuration and drive user adoption.
Definition
Salesforce Go is a Setup-based feature discovery and implementation platform designed to help Salesforce administrators streamline configuration and drive user adoption. It bundles related features into curated sets organized around specific business objectives (Improve Sales Productivity, Increase Service Efficiency, Enhance Marketing Personalization), guiding admins through enabling, configuring, and rolling out each feature without requiring them to navigate the much broader Setup tree on their own.
The product addresses one of the longest-running operational pain points in the Salesforce ecosystem: customers buy licenses for capabilities they never actually adopt because the configuration burden feels too high. A typical Enterprise Edition org pays for dozens of features that go unused because the admin team did not have the time or knowledge to set them up. Salesforce Go bridges that gap with prescriptive, guided implementation flows that take the admin from feature discovery through user-facing rollout, often in a single session. The result is more value extracted from existing license investments, which is also why Salesforce has invested heavily in the experience over the past few years.
How Salesforce Go organizes feature adoption
Goal-oriented feature groupings
Salesforce Go organizes features by business goal rather than by Setup category. Instead of presenting the admin with a list of every Sales-related Setup page, Go presents groupings like Convert More Leads, Forecast Accurately, Coach Reps Effectively, Score Pipeline Health. Each goal includes the features that contribute to it: Web-to-Lead, Lead Assignment Rules, Lead Scoring, Sales Engagement, Collaborative Forecasting, and so on. The admin can pick a goal, see what features support it, and choose which to implement first. This goal-orientation matches how non-technical stakeholders think about Salesforce: they want outcomes, not Setup pages.
Guided implementation flows
Each feature in Salesforce Go has a guided implementation flow that walks the admin through the configuration steps. The flow includes prerequisites (license requirements, dependencies on other features), configuration steps with inline guidance, validation checkpoints, and rollout suggestions. Where the standard Setup pages might require the admin to know which sub-pages to visit in what order, Go consolidates the workflow into a single guided experience. For features the admin has not used before, the guided flow significantly reduces the time-to-value compared to figuring out the setup from documentation alone.
Recommendations and underused features
Salesforce Go analyzes the org's current usage data and surfaces recommendations for features that are licensed but underused. If the org has Collaborative Forecasting licensed but only ten percent of sales managers use the forecast page, Go recommends rolling it out to the rest. If the org has Einstein Lead Scoring available but disabled, Go highlights it as an underused capability. The recommendations are based on the org's specific configuration and usage patterns, making them more actionable than generic best-practice lists. The admin can take or ignore each recommendation, with no pressure but with the visibility that the value is sitting unused.
Adoption tracking and feedback loops
After enabling a feature through Salesforce Go, the platform tracks adoption metrics for that feature: how many users have used it, how often, what specific actions they took. The metrics feed back to the Go dashboard so the admin can see whether the rollout is sticking. Low adoption triggers follow-up suggestions: provide training, simplify the feature configuration, target specific user groups for re-launch. The feedback loop is what distinguishes Salesforce Go from a simple guided-setup tool; the adoption tracking ensures that enabling a feature is not the end of the work but the beginning of measuring whether the feature delivers value.
Integration with Setup and admin workflows
Salesforce Go does not replace Setup; it augments it. Every feature in Go eventually drops the admin into the standard Setup pages for the underlying configuration, with the Go wrapper providing context and guidance. Experienced admins can skip Go and work directly in Setup if they prefer; less experienced admins benefit from the guidance. Both paths produce the same underlying configuration. The two surfaces coexist, with Go acting as the friendly front door and Setup as the comprehensive admin toolkit. Mature admin teams use both, choosing based on how familiar they are with the specific feature being configured.
Customization and admin tailoring
Salesforce Go is increasingly customizable, with admins able to define their own goal-oriented groupings tailored to the organization's strategic priorities. A retail organization might define goals like Reduce Cart Abandonment, Drive Loyalty Program Sign-Ups, and Streamline Returns; each goal would surface the relevant Commerce Cloud and Service Cloud features. The customization lets the org's specific business priorities drive the admin experience, rather than relying on Salesforce's generic goal taxonomy. The custom groupings are managed through Salesforce Go's configuration page in Setup and shared across the admin team.
Reporting and value demonstration
Salesforce Go produces reporting that helps the admin team demonstrate the value of their work to leadership. Reports show: features enabled, users adopting them, time saved through guided setup, business outcomes (where measurable) tied to feature adoption. The reports support the conversation with the CIO or business stakeholder about Salesforce ROI: features rolled out per quarter, license utilization improvements, adoption metrics across the user base. For admin teams that have historically struggled to demonstrate the value of their configuration work, the Go reports provide a structured way to tell that story.
Beyond the basic guided experience
Salesforce Go represents one piece of a broader admin-experience initiative that Salesforce has been investing in over the past several years. Adjacent capabilities include Salesforce Optimizer (a separate tool that audits the org for technical debt and configuration issues), Setup Audit Trail (which records every Setup change), and the various Einstein-powered recommendations surfacing throughout Setup. Together these tools shift the admin role from manual configuration toward strategic feature curation and adoption management. Mature admin teams operate as feature product managers for the org, deciding what to roll out, when, to whom, with what training, and how to measure success. Salesforce Go is the tool that supports this product-management posture more than the older direct-Setup-page workflow. Teams that have adopted this posture report higher business stakeholder satisfaction and more visible Salesforce ROI; teams still operating as ticket-driven Setup configurers struggle to demonstrate value. The mental model shift takes time but is one of the most important professional development steps for senior admins in the current Salesforce ecosystem. The product itself (Salesforce Go) makes the new posture easier to adopt by surfacing the right information and supporting the right workflows; the admin who embraces the posture extracts more from the tool than the admin who treats it as just another Setup page. Both the technology and the operating discipline need to evolve together for the full value to land.
Use Salesforce Go to drive feature adoption
Working with Salesforce Go combines feature discovery, guided implementation, and ongoing adoption measurement. The workflow below covers the standard sequence for using Go to roll out a new capability and measure its uptake.
- Open Salesforce Go and identify a goal
From Setup, search for Salesforce Go and open the page. Browse the available goals organized by business outcome. Pick one that aligns with the org's current priorities (Improve Sales Productivity, Reduce Case Backlog, Increase Newsletter Engagement). Review the features Go suggests for that goal, including recommended starting points based on the org's current configuration and license footprint.
- Run the guided implementation for a chosen feature
Click into the feature and start the guided implementation flow. Go walks through the prerequisites, the configuration steps, and the rollout suggestions. Complete each step with the recommended values or customize as needed. Save the configuration. At the end of the flow, Go offers next steps: train users, monitor adoption, schedule a review. Follow through on the next steps rather than treating the implementation as complete just because the configuration is saved.
- Roll out to users and track adoption
Communicate the new feature to the user community: brief internal email, training session, documentation in the team wiki. Encourage users to try the feature and provide feedback. Return to Salesforce Go after two weeks and review the adoption metrics: who is using the feature, how often, what specific actions they take. The data tells you whether the rollout is succeeding or needs intervention.
- Iterate and demonstrate value
Based on the adoption metrics, iterate on the rollout: provide additional training where adoption is low, simplify the feature configuration if users find it confusing, target specific user groups for re-engagement. Report the adoption story to leadership using the Salesforce Go reports: features enabled, users active on them, business outcomes connected. The reporting closes the loop between admin effort and business value.
- Enabling features in Go without user-facing rollout produces zero adoption. The guided flow includes rollout steps for a reason.
- Salesforce Go does not replace deep Setup knowledge. For complex configuration, you still need to understand the underlying Setup pages.
- Adoption metrics in Go are based on platform telemetry. Some features without rich telemetry produce limited adoption visibility.
- Goal taxonomies in Go are generic. Customize them for the org's specific priorities or the recommendations may not match what you actually care about.
- Enabling too many features through Go at once overwhelms the user community. Pace the rollout based on absorption capacity, not Go's recommendations alone.
Trust & references
Straight from the source - Salesforce's reference material on Salesforce Go.
- Salesforce Go OverviewSalesforce Help
- Admin OverviewSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Salesforce Go?
Q2. What problem does it solve?
Q3. How is it organized?
Discussion
Loading discussion…