Does Salesforce Have WhatsApp Integration? Every Native Option Explained

Short answer: Yes. Salesforce Service Cloud has a native WhatsApp channel called the Enhanced WhatsApp Channel, which requires the Messaging add-on and links to a WhatsApp Business Account you create during setup. Marketing Cloud Engagement has a completely separate offering, WhatsApp-First Business Messaging, sold as its own SKU and used inside Journey Builder. A third path connects the Meta Cloud API to any Salesforce object through a webhook. Which one is right depends on whether your team works Cases, journeys, or Opportunities.

The reason this question keeps getting asked is that Salesforce has shipped, rebranded, and retired several WhatsApp offerings over a few years, and most tutorials online describe a version that no longer exists. Here is the current state, and the parts that surprise people at go-live.

Option one: the Enhanced WhatsApp Channel in Service Cloud

This is the native path most people mean when they ask the question. WhatsApp arrives through Messaging, the Salesforce conversation platform that also carries Enhanced Chat and other enhanced channels. Salesforce's training material puts the requirement plainly: "to create enhanced WhatsApp channels, you need Messaging," and "each enhanced WhatsApp channel in Salesforce is linked to a WhatsApp Business account (WABA)."

Setup walks you through creating that WABA and associating it with your phone number, using Meta's embedded signup flow. Once it is live, inbound WhatsApp messages land in the Service Console as messaging sessions, can be converted into Cases, and route to agents through Omni-Channel or a routing flow. For a support organization that already lives in the console, this is genuinely the path of least resistance, and we would rather say so than pretend otherwise.

Two things to know before you build. First, the older Standard WhatsApp Messaging Channels are being retired in favour of Enhanced channels. If a consultant or a blog post from two years ago has you configuring a Standard channel, stop, because you are building on something with an end date. Second, Messaging is a licensed add-on. Salesforce does not publish its price on a public pricing page, so ask your account executive for the line item in writing rather than trusting a number you read somewhere.

Option two: WhatsApp in Marketing Cloud Engagement

Marketing Cloud is a different product line, and its WhatsApp support is a different product too. You reach it from Mobile Studio and use it as a WhatsApp Message activity inside Journey Builder, with its own templates, audiences, and phone number. The current offering is called WhatsApp-First Business Messaging, which connects to Meta. There is also a legacy path, WhatsApp Chat Messaging, that ran through Sinch.

They are not interchangeable, and the migration is destructive in a way worth reading twice. Salesforce documents it directly: after you purchase the WhatsApp-First Business Messaging SKU, all outbound messages and existing journeys and templates on the Sinch app stop working. You rebuild the WhatsApp Business Account, register a new number, recreate the templates, and rebuild the journeys. Teams treat this as a configuration change and discover halfway through a campaign quarter that it is a project.

The SKU itself requires a purchase and account executive approval. And a further wrinkle: previously registered WhatsApp numbers are not supported, so the number your marketing team has been printing on collateral may not be reusable.

Option three: the Meta Cloud API and a webhook

The most flexible route, and the one that suits sales organizations rather than support ones. You register a phone number on the WhatsApp Business Platform, receive Meta's webhook at an HTTPS endpoint, and write the events into whatever Salesforce objects you care about using the REST API, Apex, Platform Events, or Flow.

The practical shape of it: an inbound message from an unknown number creates a Lead with LeadSource set to WhatsApp. From a known number, it logs to the Contact's Activity timeline. A support question opens a Case. A reply during an open deal logs against the Opportunity and can advance the stage. Delivery statuses (sent, delivered, read, failed) write back so you know a quote actually landed. And a Flow can create a follow-up Task when nobody replies, then cancel it the moment the customer does, because the inbound event fires.

Building this yourself means a Meta developer app, a public Apex REST service on a Force.com Site to handle both the GET verification challenge and the POST message events, a Named Credential holding the access token, and a plan for rotating it. That is a real sprint. A platform like WaBulkSend receives the webhook for you and hands Salesforce clean events, which is the same architecture without the maintenance. Our Salesforce WhatsApp integration page maps every webhook event to its Salesforce object.

Can Salesforce send WhatsApp messages?

Yes, with one rule that governs every path above. Business-initiated outbound messages must use a message template that Meta approved in advance. You cannot start a conversation with free-form text. Free-form messages are only allowed inside the 24-hour customer service window, which opens when a customer messages you first, and those are free.

Template approval is where projects slip. Rejections on first submission are common, and the reasons are often about wording rather than intent. Get the templates approved before the sprint that depends on them, not during it. If you are new to this, our guide to WhatsApp message templates covers what gets rejected and why.

The US restriction that breaks most Salesforce WhatsApp plans

This is missing from nearly every Salesforce WhatsApp tutorial and it is the single most important fact for an American team. Meta's documentation states that WhatsApp "does not currently deliver marketing template messages to WhatsApp users with United States phone numbers." The pause began on April 1, 2025 and no resume date has been announced as of July 2026.

So if the plan is a Journey Builder campaign sending promotions to a US list, it will not deliver, regardless of how the Salesforce side is configured, which SKU you bought, or which partner you used. The restriction sits at Meta's delivery layer.

What does deliver to US numbers is the useful half anyway. Utility templates go through: order confirmations, shipping updates, appointment reminders, quotes, renewal notices. Authentication templates go through. And free-form replies inside the 24-hour service window go through at no cost, since service conversations became free for all businesses on November 1, 2024.

Design accordingly. Use click-to-WhatsApp ads or a website button to get the customer to message first, which opens the free window and creates the Lead. Then tie utility templates to real record events: an Opportunity moving to Closed Won, a shipment record updating, an appointment being booked. That is a Salesforce WhatsApp integration that works in the United States this quarter, rather than one waiting on a Meta policy change nobody has committed to.

What it costs, honestly

Two bills, from two companies. Salesforce charges for the licence, either the Messaging add-on for Service Cloud or the WhatsApp-First SKU for Marketing Cloud, and does not publish those prices publicly. Meta charges separately per delivered template message, priced by category and country, with non-template messages free and service conversations free since November 2024.

That double structure is why the Cloud API route is frequently cheaper for sales teams specifically. You pay Meta per delivered template either way. What you avoid is a second per-seat licence for people whose job is closing deals rather than working Cases.

Two limitations nobody warns you about

Your historical WhatsApp chats do not come with you. Integrations start logging from the moment the connection goes live. Threads that lived on someone's phone or in the WhatsApp Business app do not import into Salesforce. Export anything you need before you register the number.

And the number leaves the app. Once a phone number is registered to the Cloud API it stops working in the WhatsApp Business app entirely. Never use the number your store manager answers on their phone. Register a fresh, dedicated business number and tell the team the day it goes dark, because otherwise somebody finds out from a customer.

Picking one

If your agents work Cases in the Service Console all day and you already own Messaging, use the Enhanced WhatsApp Channel. It is fewer moving parts than anything you can assemble, and that is worth more than flexibility you will not use.

If you are a marketer running journeys and your audience is largely outside the United States, the Marketing Cloud SKU is built for exactly that. Budget for the migration if you are coming off Sinch.

If you are a sales team that needs WhatsApp threads on Leads and Opportunities, wants to schedule and send in bulk, and does not want to pay per agent for the privilege, the Cloud API route through a platform is the pragmatic answer. Same underlying webhook, none of the licence maths.

Whichever you choose, the conversation is rarely the end of the workflow. A deal agreed over WhatsApp still becomes an Opportunity that has to close, and the last step is almost always getting a document signed and returned. Wiring the messaging channel into Salesforce is worth doing properly precisely because it feeds everything downstream of it. For a broader view across CRMs, our WhatsApp CRM integration guide covers HubSpot, Zoho, Pipedrive, and custom systems on the same webhook.