Salesforce WhatsApp Integration and WhatsApp Integration With Salesforce CRM
Salesforce has a native WhatsApp channel, and it is not the one most guides describe. Standard channels are retired, Marketing Cloud sits on a separate SKU, and the DIY Cloud API route is still the most flexible. Here is each path, honestly, with the limits nobody mentions until go-live.
The demo gives you 25 messages on your own number, one time. No card required.
What your webhook code can write
Your Apex or FlowWaBulkSend has no native Salesforce app. The record writes above are what your own endpoint does with the events.
Start sending →The short answer: Yes, Salesforce integrates with WhatsApp. Service Cloud offers 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 separate offering, WhatsApp-First Business Messaging, sold as its own SKU. The older Standard WhatsApp channels are being retired. If you need conversations logged against Leads, Contacts, Cases, and Opportunities with full control over the automation, the Meta Cloud API plus a webhook into Salesforce remains the most flexible route. WaBulkSend fits the sending side of that route: it sends your approved templates in bulk or through its REST API and forwards replies and delivery statuses as signed webhooks to an endpoint you own. It has no native Salesforce app, so the Apex or Flow that writes those events to Salesforce is yours to build.
Does Salesforce have WhatsApp integration?
It does, and the confusion is understandable, because Salesforce has shipped several different WhatsApp offerings and quietly retired some of them. What exists today depends entirely on which cloud you bought.
In Service Cloud, WhatsApp arrives through Messaging, the conversation platform that also carries Enhanced Chat and other channels. The specific object you configure is an Enhanced WhatsApp Channel. Salesforce's own training material is explicit that "each enhanced WhatsApp channel in Salesforce is linked to a WhatsApp Business account (WABA)" and that "to create enhanced WhatsApp channels, you need Messaging." The older Standard WhatsApp Messaging Channels are on a retirement path, so anything you build should target the Enhanced channel.
In Marketing Cloud Engagement, WhatsApp is a different product line altogether, reached from Mobile Studio and used as a WhatsApp Message activity inside Journey Builder. There are two variants: WhatsApp-First Business Messaging, which connects to Meta, and a legacy WhatsApp Chat Messaging path that ran through Sinch. They are not interchangeable, and moving between them is destructive. More on that below, because it catches teams out.
The three ways to integrate WhatsApp with Salesforce
Pick by what you need the conversation to do, not by what a demo shows you.
| Path | What it is | What it needs | Best for |
|---|---|---|---|
| Enhanced WhatsApp Channel (Service Cloud) | Native inbound messaging into the Service Console, converted to Cases and routed with Omni-Channel | The Messaging add-on, plus a WABA created during channel setup | Support teams who live in the Service Console all day |
| WhatsApp-First Business Messaging (Marketing Cloud) | A WhatsApp Message activity in Journey Builder, with its own templates and audiences | A separate SKU, purchase and account executive approval, a new WABA and number | Marketers running journeys, outside the US marketing pause |
| Meta Cloud API plus webhook | You receive Meta's raw webhook and write to any Salesforce object through the REST API, Apex, Platform Events, or Flow | A Meta app, an HTTPS endpoint and code that writes to Salesforce. A sending platform like WaBulkSend can handle bulk and scheduled template sends and forward events to that endpoint, but the Salesforce side is still a developer job | Sales teams who need Leads, Opportunities, and Tasks, plus bulk and scheduled sends |
Where Salesforce wins: if your agents already work Cases in the Service Console and you own the Messaging license, the native Enhanced channel is less moving parts than anything you can assemble. It is the right answer for a lot of support orgs, and we would rather tell you that than sell you a migration you do not need.
How to connect WhatsApp to Salesforce through the Cloud API
Six steps from a bare Meta Business account to WhatsApp threads on the Contact record.
Create the WhatsApp Business Account
Set up a Meta Business Account and a WhatsApp Business Account, then verify the business. Verification is what moves you off the starting messaging tier of 250 unique customers per 24 hours.
Register a dedicated number
Use a number that can receive a call or SMS and is not already active on a personal WhatsApp or the WhatsApp Business app. Once it is registered to the API it leaves the app, so never use the number on someone's phone.
Collect the credentials
Meta issues a phone number ID and an access token. Store the token in a Salesforce Named Credential rather than hardcoding it in an Apex class, and plan for rotation.
Expose an endpoint Salesforce owns
Meta needs an HTTPS callback. A public Apex REST service on a Force.com Site handles both the GET verification challenge and the POST message events. If WaBulkSend holds the Meta webhook, it forwards replies and statuses to your endpoint as signed events instead, and your endpoint still writes them to Salesforce.
Match the number to a record
Look up the inbound wa_id against Lead and Contact phone fields, create the Lead if it is new, then write the message to the Activity timeline and publish a Platform Event so Flow can react.
Send back through templates
Outbound business-initiated messages must use a template pre-approved by Meta. Fire them from Flow on a stage change, and write the delivered or read receipt back to the record when the status callback arrives.
What syncs to which Salesforce object
The Cloud API webhook delivers these events. Each maps cleanly onto something Salesforce already understands.
| WhatsApp event | Salesforce object | What happens |
|---|---|---|
| First inbound message from an unknown number | Lead | Create the Lead, set LeadSource to WhatsApp, assign an owner |
| Inbound message from a known number | Contact and Activity | Log the message on the timeline against the matched Contact |
| Support question | Case | Open a Case and route it through Omni-Channel to a queue |
| Reply during an open deal | Opportunity | Log to the Opportunity timeline, optionally advance the stage |
| Delivery status: sent, delivered, read, failed | Custom message object or Task | Update the send record, alert or retry on failure |
| No reply after a set interval | Task and Flow | Create a follow-up Task, cancel it automatically when the customer answers |
Four things that go wrong at go-live
Moving to WhatsApp-First in Marketing Cloud destroys what you built. Salesforce documents this in blunt terms: 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, the number, the templates, and the journeys. Plan it as a migration project, not a toggle.
Your existing WhatsApp number probably cannot be reused. A number already registered on WhatsApp cannot simply be pointed at the API. Once a number is registered to the Cloud API it stops working in the WhatsApp Business app entirely. Whichever path you choose, budget for a fresh, dedicated business number and tell the team before the store number goes dark.
Standard channels are on the way out. Salesforce is retiring Standard WhatsApp Messaging Channels in favour of Enhanced channels. If a consultant or an old tutorial has you configuring a Standard channel, stop. You are building on something with an end date.
Templates gate every outbound message. You cannot start a conversation with a free-form message. Business-initiated sends require a template that Meta has already approved, and rejections are common on first submission. Get the templates approved before the sprint that depends on them, not during it. Our guide to WhatsApp message templates covers what gets rejected and why.
What Salesforce WhatsApp integration costs
Two bills, from two companies. Salesforce charges for the licence: its pricing page lists Contact Center Digital, the Service Cloud add-on that carries WhatsApp, at $75 per user per month billed annually, and Marketing Cloud Next lists two-way WhatsApp on Advanced Edition at $3,250 per org per month. Usage is paid in Salesforce Message Credits, 4.94 per US utility template, at a credit price set in your Order Form. The per-agent math is in our Salesforce Digital Engagement pricing guide, and the Journey Builder side in Marketing Cloud WhatsApp pricing.
Meta charges separately, for messages. Since July 1, 2025 billing is per message, and you are only charged when a template message is delivered. The rate depends on the template category (marketing, utility, or authentication) and the recipient's country. Non-template messages were free for every business from November 1, 2024 until September 30, 2026; since October 1, 2026 the first 1,000 a month per business number are free. From October 1, 2026 Meta bills them at the utility rate for the destination country.
That structure is why the Cloud API route is often cheaper for sales teams. You are already paying Meta per delivered template either way. What you avoid is a second per-seat licence on top, for agents whose actual job is closing deals rather than working Cases. See the full Meta breakdown on our WhatsApp Business API pricing page.
What US Salesforce teams can actually send
This matters more than any licence question, and it is missing from almost every Salesforce WhatsApp tutorial. Meta paused delivery of marketing category template messages to US phone numbers on April 1, 2025, and as of July 2026 no resume date has been announced. If your plan was a Journey Builder campaign blasting promotions to a US list, it will not deliver, no matter how the Salesforce side is configured.
What does deliver to US numbers: utility templates, so order confirmations, shipping updates, appointment reminders, quotes, and renewal notices. Authentication templates. And any free-form message you send inside the 24-hour customer service window that opens when a customer messages you first, which is free up to 1,000 replies per business number each month.
Design the Salesforce integration around that reality. 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. Tie utility templates to real record events: an Opportunity moving to Closed Won, a shipment record updating, an appointment being booked. That is a WhatsApp integration that works in the US today rather than one waiting on a policy change.
Frequently asked questions
Does Salesforce have WhatsApp integration?
Yes. Service Cloud offers a native Enhanced WhatsApp Channel through the Messaging add-on, which links to a WhatsApp Business Account created during setup. Marketing Cloud Engagement has a separate WhatsApp-First Business Messaging SKU used inside Journey Builder. You can also connect WhatsApp to any Salesforce object through the Meta Cloud API and a webhook.
How does Salesforce integrate with WhatsApp?
Through a WhatsApp Business Account behind the WhatsApp Business Platform. For the Enhanced channel, Salesforce walks you through creating the WABA during channel setup and inbound messages become Cases routed by Omni-Channel. For a custom integration, Meta posts message events to an HTTPS endpoint you own, and Apex or Flow writes them to Leads, Contacts, Cases, or Opportunities.
Can Salesforce send WhatsApp messages?
Yes, with one important rule. Business-initiated outbound messages must use a message template that Meta approved in advance. Free-form messages can only be sent inside the 24-hour customer service window that opens after a customer messages you. Salesforce can trigger both from Flow, Journey Builder, or an Apex call to the Cloud API.
What is the Enhanced WhatsApp Channel in Salesforce?
It is the current native WhatsApp channel in Salesforce Messaging, replacing the Standard WhatsApp Messaging Channels that are being retired. Each enhanced channel links to one WhatsApp Business Account, requires the Messaging licence, and delivers inbound WhatsApp conversations into the Service Console where they can be converted to Cases and routed.
Do I need a WhatsApp Business Account for Salesforce?
Yes, always. Every path to WhatsApp runs through a WhatsApp Business Account on the WhatsApp Business Platform. The Enhanced channel setup creates one for you and links it to your phone number. The free WhatsApp Business app has no public API and cannot be connected to Salesforce at all.
How much does Salesforce WhatsApp integration cost?
There are two bills. Salesforce lists Contact Center Digital, the Service Cloud add-on that includes WhatsApp, at $75 per user per month billed annually, and two-way WhatsApp on Marketing Cloud Next Advanced Edition at $3,250 per org per month. Messages are paid in Salesforce Message Credits, 4.94 credits per US utility template and 30.87 per marketing template, at a credit price set in your Order Form. Inbound messages use no credits. Meta has charged for service messages since October 1, 2026.
Can I import my old WhatsApp chats into Salesforce?
No. Integrations start logging from the moment the connection goes live. Historical WhatsApp threads that lived on a phone or in the WhatsApp Business app do not import into Salesforce. Export anything you need to keep before you register the number to the API, because the number stops working in the app afterwards.
Can I send WhatsApp marketing campaigns to US customers from Salesforce?
Not at present. Meta does not currently deliver marketing template messages to WhatsApp users with United States phone numbers, a pause that began on April 1, 2025 with no announced resume date. Utility templates such as order and appointment updates, authentication templates, and replies inside the 24-hour service window all deliver normally.
Salesforce, Service Cloud, and Marketing Cloud are trademarks of Salesforce, Inc. WaBulkSend is not affiliated with, endorsed by, or sponsored by Salesforce.
Run the WhatsApp sends, log them in Salesforce your way
Bulk and scheduled template sends on your own Cloud API number, with replies and delivery statuses forwarded as signed webhooks to your endpoint, where your Apex or Flow logs them on the record. There is no native Salesforce app and no inbox; the record sync is code you own. The demo gives you 25 messages on your own number, one time, no card required.
Start sending