We are at Dreamforce 2026, Industry Pavilion at San Francisco
January 18, 2026
Salesforce Marketing Cloud supports omnichannel marketing by holding one profile per customer and orchestrating every channel from that single profile, so an email, a text message, a push notification, and a web experience all reflect the same behavior and the same consent. The product is now branded Agentforce Marketing, and it covers three separate solutions rather than one. Which one you use decides how much omnichannel you actually get.
Most omnichannel programs do not fail on channels. They fail because the same person exists as four unlinked records, so no channel knows what the others did. That problem, and the naming that now sits on top of it, are what this article covers.
The two words get used interchangeably in vendor material. The difference is not the number of channels. It is whether the channels share state.
Multichannel means you are present in several places. Email, SMS, social, web, and a store all run campaigns. Each one is planned separately and reports separately.
Omnichannel means those channels read from and write to the same customer record. The cart a shopper filled on mobile is the cart the store associate can see. The email that goes out tonight knows about the support ticket that opened this afternoon.
Read that table from the bottom if you are scoping a project. The last row is the honest test. If adding WhatsApp means building a separate audience and a separate report, you are running multichannel with more tools, whatever the platform is called.
If you are researching this today, the naming will trip you up before the technology does. Salesforce's own marketing site now reads "Agentforce Marketing (formerly Salesforce Marketing Cloud)." The rename was announced in late 2025 and has worked through the site, the documentation, and the partner ecosystem since.
Agentforce Marketing is a brand covering several products, not a thing you log into. That distinction matters here, because those products do omnichannel very differently.
Editions add another layer on top of this, with Growth, Advanced, and Plus tiers appearing across the products. Those affect what you can switch on. The five names above are the ones that change what you can build at all.
None of this is cosmetic for an omnichannel program, because the product you land on sets your ceiling. Our wider walkthrough of what Salesforce Marketing Cloud is and how to use it covers the platform itself; this article is about orchestrating across channels inside it.
This is the decision that actually determines your omnichannel ceiling, and it is rarely framed clearly in a sales conversation.
The last row deserves plain speaking. Marketing Cloud Next is where Salesforce is investing, and its architecture is genuinely better suited to omnichannel because Data Cloud sits underneath it rather than beside it. It is also a different product, not a newer version of the one your team already knows. Practitioners moving across from Engagement have publicly reported gaps in areas they had come to rely on.
Build a proof of concept on your single most complex live journey before you commit to a migration date. If that journey can be rebuilt cleanly, the rest will follow. If it cannot, you have learned it for the price of a sprint rather than a program.
Search for "Salesforce Omni-Channel" and you will land on a different feature entirely.
Omni-Channel in Service Cloud is a routing engine. It takes incoming work, such as cases, chats, calls, and messages, and assigns each item to the right available agent based on skills and capacity. It is a service capability with no marketing function.
The two share a word and nothing else. A quick way to tell which one a document is about: if it discusses queues, routing configurations, and agent capacity models, you are reading about Service Cloud. If it discusses journeys, audiences, and channels, you are in marketing.
Omnichannel discussions tend to stay abstract. Here is what the channels are concretely, and what each one asks of you before it can join a journey.
Two of those rows do most of the work in mature programs and are usually scoped last.
Paid advertising earns its place through suppression. Not showing an acquisition ad to someone who bought yesterday is often worth more than any targeting improvement, and it is only possible when the ad platform audience is driven by the same profile as the email.
In-store data is what makes a journey feel connected rather than merely automated. Customers notice when a store visit changes what arrives in their inbox, and they notice just as sharply when it does not.
Getting point-of-sale or clienteling data into the profile on a useful schedule is an integration problem before it is a marketing one, which is why it belongs with integration architecture rather than campaign configuration. The channel and journey APIs themselves are documented on Salesforce Developers, and if your requirement is triggered one-to-one messages rather than campaigns, that is a different mechanism covered in our guide to the Marketing Cloud Transactional Messaging API.
Every omnichannel demo quietly assumes something your org may not have: the ability to state with confidence that this email address, this mobile number, this loyalty ID, and this web visitor are the same person.
Without that, omnichannel degrades into multichannel no matter which product you bought. Journeys fire on partial data. Suppression misses. Someone who bought in store yesterday still receives the abandoned-cart email today.
The last row is the one customers punish hardest. A promotional message arriving while a complaint is open reads as an organization that does not know who you are, which is precisely the impression omnichannel exists to remove.
Consent deserves separate attention. It is not one checkbox. Permission to email is not permission to text, and permission to text about deliveries is not permission to text about promotions. Model consent per channel and per purpose from the beginning, because retrofitting it means going back to customers and asking again.
The question comes up often enough to answer plainly. Sources word them differently, but four things must all be present:
Three out of four is a very common place to stall, and the missing one is almost always measurement. Journeys get built, orchestration works, and reporting stays stubbornly channel-by-channel, so nobody can prove the effort paid for itself and the program loses its budget.
Salesforce's own Trailhead module on omni-channel marketing frames the same work as three sequential steps: onboard your customers, activate first-party data, then measure. If your team prefers a checklist to a set of principles, that sequence is a reasonable substitute.
Order matters more than ambition here. Most stalled omnichannel programs started too wide.
First, pick one journey that crosses exactly two channels. Not a program. One journey, such as an abandoned cart, a post-purchase follow-up, or a renewal reminder, that has to work across email and one other channel.
Second, resolve identity for that journey's audience only. You do not need a perfect customer view to start. You need the specific keys this journey depends on to be trustworthy for the people it will reach.
Third, model the consent it requires. Write down which channel needs which permission and where that permission is currently stored. Close the gaps before you send anything.
Fourth, build global suppression in from day one. Retrofitting suppression after journeys are live is how over-messaging incidents happen, and they cost more trust than the journey earns.
Fifth, measure the journey rather than the channels. Agree the success metric before you build. If nobody can state how you will know it worked, it is not ready to build.
Sixth, and only then, add a channel. Every new channel should be an endpoint on a journey that already works, not a fresh project with its own audience.
This sequence is deliberately unglamorous. It is also the difference between a program that expands steadily and one that stalls after two campaigns. If your motion is B2B, the same discipline applies with different tooling, and the handoff between systems is worth designing early, which we cover in our guide to integrating Marketing Cloud with Account Engagement.
The AI story has moved, and it is worth being precise about how.
For years the pitch was Einstein: engagement scoring, send-time optimization, and content selection, all layered onto journeys a human designed. That is still how Marketing Cloud Engagement works, and it still delivers real lift. We cover those capabilities in detail in our breakdown of Einstein for Salesforce Marketing Cloud, so this article will not repeat them.
Agentforce is a different proposition. Rather than predicting inside a journey you built, agents are intended to take action: drafting campaign plans, assembling audiences, answering an inbound question inside a marketing conversation, and adjusting a campaign while it runs.
Two honest caveats belong here. First, an agent is only as good as the data and instructions behind it, so the identity work described above is a prerequisite rather than an alternative to it. Second, marketing-side agent capability is maturing at different rates across Engagement and Next, so confirm what is generally available for your edition rather than what a keynote demonstrated. Salesforce Ben has covered the platform rebuild at a practitioner level, and the Trailblazer Community is usually where real migration experiences surface first.
The pattern worth internalizing is that AI changes who does the work, not what the work requires. Connected data is still the precondition, and it is still the part most programs underinvest in.
Agentforce Marketing. Salesforce's own marketing site reads "Agentforce Marketing (formerly Salesforce Marketing Cloud)." It is an umbrella brand rather than a single application, and it covers Marketing Cloud Engagement, Marketing Cloud Account Engagement, and Marketing Cloud Next.
No. Marketing Cloud Engagement is the long-standing standalone platform with Email Studio, Mobile Studio, and Journey Builder. Marketing Cloud Next is built natively on the Salesforce core platform with Data Cloud as its foundation and Agentforce agents in place of Einstein add-ons. Moving between them is a re-platform rather than an upgrade.
Multichannel means being present on several channels that are planned and reported separately. Omnichannel means those channels share one customer profile, one consent record, and one suppression list, so behavior in any channel changes what happens in the others.
No. Omni-Channel in Service Cloud is a routing engine that assigns incoming cases, chats, and calls to available agents based on skills and capacity. It shares a word with omnichannel marketing and nothing else.
Salesforce is the wider platform, including Sales Cloud and Service Cloud. Marketing Cloud, now under the Agentforce Marketing brand, is the marketing portfolio within it. Historically Marketing Cloud Engagement ran on separate infrastructure and connected to the core platform, which is exactly what Marketing Cloud Next changes by building on the core platform directly.
Unified data with resolved identity, a consistent experience wherever the customer appears, real-time orchestration across channels, and closed-loop measurement at the journey level. Programs most often stall on the fourth.
Not strictly for Marketing Cloud Engagement, which can orchestrate channels using its own data extensions. In practice, you need something that resolves identity across systems and brings offline data in, and Data Cloud is the supported route for that. Marketing Cloud Next assumes it as the foundation.
Salesforce Marketing Cloud is a capable omnichannel engine, and under the Agentforce Marketing brand it is getting better at acting rather than only predicting. But the platform is never the constraint people expect it to be.
The constraint is whether one profile per customer actually exists, whether consent is modeled per channel and per purpose, whether suppression is global, and whether anyone can measure a journey rather than a channel. Get those right and adding a channel becomes trivial. Skip them and you buy an expensive multichannel stack.
At Minuscule Technologies we start omnichannel work with identity and data readiness, then design the journey, then connect channels one at a time. We also help teams decide honestly between Marketing Cloud Engagement and Marketing Cloud Next rather than defaulting to the newer name. If you want a clear-eyed view of where your Marketing Cloud implementation stands today, talk to our team about an omnichannel readiness review.
You've seen what's possible. Now, let's make it happen for your business. Whether you need an end-to-end Salesforce solution, a complex integration, or ongoing managed services, our team is ready to deliver.
Schedule a Free Strategic Call
