High Velocity Sales
High Velocity Sales (HVS) was the original Salesforce product name for the cadence-and-Work-Queue sales execution tool, released in 2018 and renamed to Sales Engagement in 2022.
Definition
High Velocity Sales (HVS) was the original Salesforce product name for the cadence-and-Work-Queue sales execution tool, released in 2018 and renamed to Sales Engagement in 2022. HVS targeted SDR and inside-sales teams running high-volume outbound prospecting and inbound lead follow-up; it bundled Sales Cadences, a prioritized Work Queue, integrated email tracking, and Lightning Dialer voice. The 2022 rebrand to Sales Engagement was branding, not architecture; HVS users transitioned seamlessly to the renamed product without configuration changes.
The HVS name still appears in older documentation, AppExchange listings, third-party blog posts, and customer org configurations from before the rename. Salesforce documentation now redirects HVS references to Sales Engagement, but the legacy name persists in the wild. Anyone running a Salesforce org configured pre-2022 may see permission set names like HighVelocitySalesUser or page tab labels referencing HVS; these continue working but use the Sales Engagement product underneath. For new work, use the Sales Engagement name; for inherited configurations, recognize HVS references as the same product.
What High Velocity Sales was, why it was renamed, and where the old name still appears
The 2018 release and original feature set
Salesforce launched HVS in 2018 as a Sales Cloud add-on targeting SDR and inside-sales workflows. The original feature set included Sales Cadences (multi-touch sequences), the Work Queue (prioritized task list), Lightning Dialer integration for voice, and email engagement tracking. The bundle was positioned to compete with Outreach and Salesloft, which were dominant in the standalone sales-engagement-tool category at the time. Pricing was per-user as an add-on above Sales Cloud Professional or Enterprise editions.
The 2022 rename to Sales Engagement
The rename was a branding decision tied to broader Sales Cloud product positioning. High Velocity Sales sounded like a niche productivity tool; Sales Engagement positioned it as the core sales execution layer above Lead and Opportunity management. The underlying features did not change at rebrand; cadences, Work Queue, email tracking, and dialer integration all carried forward. Customers running HVS as of 2022 woke up to Sales Engagement with their existing configurations intact.
Why the old name persists
Three reasons. Legacy permission sets and page tabs in customer orgs still carry the HVS name (HighVelocitySalesUser permission set, HVS Tab); these continue working but were never renamed in production orgs that had them. AppExchange listings and third-party blog posts from 2018-2022 use HVS; the content remains accurate but the naming is stale. Customer admins still refer to the product as HVS in conversations, especially those who deployed before the rebrand. Recognize HVS references as the same product as Sales Engagement.
Permission set name mapping
Permission sets created before the rename are typically named HighVelocitySalesUser or HighVelocitySalesAdmin. Permission sets created after the rename are named SalesEngagementUser or similar. Both grant the same underlying capability; the names diverge only because Salesforce did not rename existing permission sets in production orgs. For new permission set assignments, use the Sales Engagement-named sets if available; for inherited orgs, the HVS-named sets still work.
Documentation and search
Salesforce Help redirects most HVS-named pages to the Sales Engagement equivalents. Searching "high velocity sales" on help.salesforce.com lands on Sales Engagement content. Old Trailhead modules tagged HVS are still discoverable but the modern content is under Sales Engagement. For canonical documentation, use Sales Engagement as the search term; HVS produces stale results.
Migration considerations
There is nothing to migrate. The 2022 rename was a label change at the product level; no admin action was required. Customer orgs continued running their existing cadences, Work Queue, and integrations under the new name. The only optional cleanup is renaming legacy HVS-named permission sets or page tabs to Sales Engagement for clarity; the rename is cosmetic and does not affect behaviour.
How to talk about HVS today
Two audiences. New customers and prospects: use Sales Engagement; HVS is unfamiliar to anyone who started with Salesforce after 2022. Existing customers from the HVS era: either name works, but Sales Engagement is the canonical current term. In documentation, the convention is "Sales Engagement (formerly High Velocity Sales)" on the first reference, then "Sales Engagement" thereafter.
Working with legacy HVS configurations in modern Salesforce orgs
There is no migration work for HVS to Sales Engagement; the rename happened at the product level. The pattern below covers cleanup of legacy HVS-named artifacts that linger in inherited orgs.
- Inventory HVS-named artifacts
Setup, Permission Sets, search HighVelocity. Setup, Tabs, search HVS. Note legacy artifacts: permission sets, page tabs, list views, custom field names. These continue working under the Sales Engagement product but use the old branding.
- Decide rename versus leave-alone
Renaming legacy permission sets is cosmetic and risk-free. Decide based on how much the legacy naming confuses new admins or hires. For orgs onboarding people who never knew HVS, rename. For stable teams that know the legacy names, leave-alone is fine.
- Rename legacy permission sets and tabs
Edit the permission set, change the label to SalesEngagementUser or similar. Edit page tabs similarly. The API name on permission sets cannot change after creation; if you need a clean API name, create new permission sets and reassign users.
- Update internal documentation
Replace HVS references in admin runbooks, training materials, and onboarding docs with Sales Engagement. Document the historical name on the first reference for context, then use Sales Engagement consistently.
- Brief the team on the naming
Confirm that the team knows HVS and Sales Engagement refer to the same product. New hires especially benefit from explicit naming context; experienced admins switch between names without confusion.
Continue working under the Sales Engagement product. Rename labels or leave alone based on team preference.
Legacy HVS tabs render correctly; rename for clarity or leave for backward compatibility with internal training.
Salesforce Help redirects HVS to Sales Engagement. Update internal docs to current canonical name.
Cannot rename after creation. Create new permission sets if a clean API name matters; reassign users.
- HVS and Sales Engagement are the same product. Treat them as synonyms; legacy configurations work under the renamed product.
- Permission set API names cannot rename. Cosmetic label changes are possible; structural rename requires recreation.
- Old AppExchange listings and blog posts use HVS terminology. Translate to Sales Engagement when consuming the content.
- The Salesforce Help search index biases toward Sales Engagement. Search for Sales Engagement, not HVS, when looking for current documentation.
- Customer-facing language matters. Refer to the product as Sales Engagement in customer conversations; HVS sounds dated to anyone post-2022.
Trust & references
This term has been renamed to Sales Engagement.
View current pageCross-checked against the following references.
- Sales Engagement Overview (formerly High Velocity Sales)Salesforce Help
- Sales CadencesSalesforce Help
Straight from the source - Salesforce's reference material on High Velocity Sales.
- Set Up Sales EngagementSalesforce Help
- Lightning DialerSalesforce 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 High Velocity Sales?
Q2. What does Sales Engagement include?
Q3. Who benefits most from Sales Engagement?
Discussion
Loading discussion…