If you’ve been in the Salesforce ecosystem for long enough, you’ll know all about Salesforce’s reputation for renaming. Some of its biggest products – including Agentforce, Marketing Cloud, and Data 360 – have fallen victim to a rebrand more than once, and the issue has become so well-known that a site called renameforce.com has been created to help keep users as updated as possible.
For years, this habit has largely been a tongue-in-cheek observation – an occasional jokey complaint in the community. However, as Salesforce continues to grow in complexity, introduce new products and features, and attract new talent, the confusion around the renaming has become hard to ignore. Has it finally made the platform too confusing to use?
Salesforce’s Extensive Renaming History
Salesforce has been known to love a rebrand for quite some time now. Rebrands are normal in tech, especially as products develop, but when it becomes confusing or difficult to keep up with, a company should consider whether the effort is worth the result.
If you asked anyone in the community to give you an example of a notable rename in Salesforce, they would probably say Marketing Cloud.
In 2022, Pardot, the marketing automation segment of the cloud, was renamed to Marketing Cloud Account Engagement. Although it was due to an effort to make Salesforce’s extensive product suite easier to understand, it has often been regarded as a strange choice, given the wordiness of the new name. It does have the tendency to get confusing when trying to distinguish between Marketing Cloud Engagement and Marketing Cloud Account Engagement, for example.
Since then, it has had more developments that have made it difficult to certify which tool and product is for what: Marketing Cloud Growth (MCG), Marketing Cloud Advanced (MCA), and Marketing Cloud Next.
Marketing Cloud is not the only product that has had a facelift or name change. Within the last year, Data Cloud was renamed to Data 360, the AppExchange became the AgentExchange, and Agentforce has become Agentforce 360. In fact, it is estimated that over 30 products and features within Salesforce have undergone a rename.
Why This Is a Problem in the Agentforce Era
Keeping up with Salesforce’s product, tool, and feature renames has been difficult enough thus far, but it has only become more disconcerting since the release of Agentforce. As Agentforce and its AI product portfolio are Salesforce’s number one focus, the company is likely feeling pressure to continuously innovate and offer more AI solutions to its customers. Although this has resulted in a wide range of options across multiple verticals, it has also begun to confuse the community.
At SF Ben, we’ve begun to ask, “How many agents is too many?” but this doesn’t apply to just agents. With every release, conference, and update, we’re seeing new agents, features, fixes, and more, and although Salesforce’s continuous development is largely positive, when does it become too much?
An insightful thread on r/Salesforce highlighted one user’s frustrations with Salesforce’s different voice offerings. In just his post, he referenced seven different products and tools that he was struggling to discern the difference between: the Voice Call standard object, Sales Dialer, Service Cloud Voice (renamed to Salesforce Voice), Agentforce Contact Center, Agentforce Voice, Agentic Contact Center, and the Telephony Integration API.
“Salesforce, I just want to click the phone number in the CRM and have a little screen-pop widget for the call, then when I hang up, a call record gets logged – and optionally, an AI summary of the transcription gets copied to the call log record,” the user wrote. “Is it a thing or not? Does it require a 6-month implementation roadmap or is it a license and a feature toggle? I am so tired of their marketing content SEO-hack smokescreen that do nothing but inhibit navigation to the actual product specs.”
Another thread from user Apart-Tie-9938 explained that their boss was hesitant to sign off on Agentforce for Service because he didn’t want to risk the business on a “new platform”, showing evident confusion over the constant renaming.
Salesforce clearly wants to get customers on board with its Agentforce portfolio, and is actively releasing as many different variations of tools and features as possible to appeal to as many customers as possible. However, is this just backfiring, confusing customers, and stressing out the professionals responsible for implementing them?
Does Salesforce Need to Slow Down?
At last year’s Dreamforce, Salesforce Co-Founder Parker Harris admitted that Salesforce had “lost its way”, acknowledging the community’s frustration over the constant bombardment of Agentforce and AI announcements. However, he also admitted something poignant: “If we don’t go all in, we’ll go obsolete.”
There is an undeniable pressure from the company’s investors, competitors, and customers to carry on building and releasing the most cutting-edge AI solutions, especially as traditional SaaS offerings are becoming a thing of the past. The “SaaSpocalypse” is more than just a buzzword – it’s reshaping the way the sector operates and what its customers expect from it.
At this point, can Salesforce afford to slow down? In between navigating the ongoing AI race and relentless stress from Wall Street to grow exponentially, the company has to keep up the scale of innovation.
However, this unfortunately leaves its community in a difficult situation. Salesforce will need to consider how it markets and offers its growing AI portfolio before it spirals out of control. This could include tighter bundling, feature merging, or even just updated communication and education on the product differences through avenues such as Trailhead.
Final Thoughts
Although Salesforce’s renaming habit hasn’t repelled its customers from the platform in droves, it is undeniably becoming a point of contention. Pair it with the SaaS giant’s growing AI suite, and working out the best tools to use quickly becomes difficult for professionals and users alike.
Hopefully, as Salesforce’s AI offerings mature, we will begin to observe more clarity around the different options, but we will see what they rename next first – my bet is on Agentforce.
