Experience Lion CRM — The King of WhatsApp CRM 7 Days Free Limited Access
→ Request Access

Salesforce WhatsApp Integration: Complete Setup Guide (2026)

Connect WhatsApp to Salesforce in 2026: the four routes, the Digital Engagement licence trap, real costs, setup steps, and the whitelabel option.

A sales director opens a Salesforce dashboard and sees that the team logged forty-one activities last week. She knows for a fact they spoke to several hundred customers, because she sat next to them while they did it. The conversations happened on WhatsApp, on personal phones, and Salesforce recorded none of it. The pipeline she is reporting to the board is not the business. It is the fraction of the business that happened to touch a system nobody wants to type into twice.

That gap is what a Salesforce WhatsApp integration is meant to close. Done properly, WhatsApp becomes a first-class channel: messages land on the contact and case records, agents reply from the console, Flow can send approved templates automatically, and reporting finally counts the channel your customers actually use. Done badly, you buy a licence add-on you did not budget for, connect a number you cannot later migrate, and the team goes back to their own phones within a month.

This guide covers what the integration really is, the four routes available to you, the licence question that decides most budgets, the migration trap that catches teams who set up WhatsApp early, what the whole thing costs in 2026, and how agencies package this work under their own brand instead of billing it once.

In this guide

What a Salesforce WhatsApp integration actually means

The phrase covers three different jobs, and most of the wasted money in this area comes from buying for one and expecting all three.

The first is agent messaging. WhatsApp conversations arrive in the Service Cloud console, several agents can work one business number, and every message is attached to the right contact or case. This is what most teams picture when they ask for the integration, and it is what Salesforce’s native channel is built to do.

The second is automation. Flow sends an approved WhatsApp template when something happens in Salesforce, so a new lead gets an instant reply, a case status change tells the customer without an agent typing it, and an appointment reminder goes out on its own. This is where the hours come back.

The third is marketing and attribution. Campaigns go out over WhatsApp, engagement is recorded against the customer, and you can finally see which conversations turned into revenue. On Salesforce this sits in a different product from the service side, which is exactly why the routes below matter.

A full setup gives you all three. A shortcut usually gives you the first, and the gap becomes visible about two months later when somebody asks why none of it is automated.

The four ways to connect WhatsApp to Salesforce

There are four honest routes. The right one depends on which Salesforce products you own and how central chat is to how you sell and support.

Route one: the native Service Cloud WhatsApp channel. Salesforce connects a WhatsApp Business Account directly to Messaging in Service Cloud. Agents work the conversations in the console alongside cases. This is the cleanest route because there is no third vendor to pay or debug. The catch is the licence requirement, which is the next section and is the single biggest cost in most projects.

Route two: Unified Conversations for WhatsApp. Announced by Salesforce and Meta in 2024 and now generally available, this puts marketing and service conversations on one WhatsApp number and one shared customer profile, powered by Data Cloud. A marketing message and a support reply live in the same thread rather than in two disconnected systems. It is the strongest native option if you run both Marketing Cloud and Service Cloud, and it carries a setup constraint that catches existing users out, covered below.

Route three: an AppExchange connector or third-party WhatsApp platform. You run a dedicated WhatsApp tool next to Salesforce and sync the two. The messaging platform handles broadcasts, chatbots, agent routing, and campaign reporting, and writes activity back to Salesforce records. This costs more in software but gives far stronger messaging features, and it works on Salesforce editions where the native channel is not available or not worth the add-on.

Route four: a custom build on the WhatsApp Business API. You take API access from a provider and move data between it and Salesforce yourself with Apex and platform events. This makes sense when you have genuinely unusual requirements and a developer already maintaining integrations. It rarely makes sense otherwise, because you have just taken on the upkeep of something two companies already maintain for you.

Most service teams should start at route one and move to route three when messaging outgrows a console inbox. Teams running both marketing and service on WhatsApp should look hard at route two. Agencies selling to clients usually end at route three or at the whitelabel option described later, because a branded product is a better business than a configured connector.

The licence question: Digital Engagement

This is the detail that derails more Salesforce WhatsApp projects than anything technical, so settle it before you plan a single sprint.

Native WhatsApp messaging in Salesforce is not part of a standard Service Cloud seat. It requires the Digital Engagement add-on, sold on top of Service Cloud, and at the time of writing Salesforce lists it at around 75 dollars per user per month on the eligible editions. Your agents also need a Service Cloud licence and work the conversations through the Service Cloud console. If somebody quoted you this project without that line in it, the quote is wrong, and it is usually wrong by more than the rest of the project combined.

Two follow-on details matter as much as the headline number.

The first is that the add-on is per user, so the cost scales with how many agents touch WhatsApp, not with how much you message. Ten agents is a very different budget from fifty, and it is worth deciding early whether every agent needs the channel or whether a smaller messaging team does.

The second is consumption. Digital Engagement includes a small monthly allowance of conversations per user, currently 25, and that allowance can be applied to SMS or WhatsApp. Beyond it, WhatsApp conversations are billed on a consumption model that follows Meta’s conversation-based pricing. The older arrangement where customer-initiated WhatsApp conversations were effectively unlimited under the SKU no longer applies, so any budget built on that assumption needs redoing.

Editions, list prices and allowances change, so verify against Salesforce’s current digital channels pricing page before you commit. The stable point is the shape of the rule: native WhatsApp on Salesforce is a paid per-user add-on with a consumption component on top, and if that maths does not work for your team size, routes three and four exist precisely for that reason.

This is also the moment for the honest comparison. If WhatsApp is the main way your team sells, paying a per-agent add-on so that chat becomes one tab inside a CRM can be worse value than putting a chat-first tool at the centre and letting Salesforce do what it is genuinely excellent at, which is everything after the conversation. Teams weighing that trade-off usually find it clearer after reading WhatsApp CRM vs WhatsApp Business API, which separates the raw channel from the software that makes it usable.

Enhanced vs Unified messaging, and the migration trap

If you already have WhatsApp running on Salesforce, read this section before you plan anything else, because it will change your project plan.

Salesforce has two generations of WhatsApp channel. The earlier one, usually called Enhanced messaging, is the service-only channel. The newer one, Unified Messaging, is what powers Unified Conversations for WhatsApp and lets marketing and service share a number, a thread and a customer profile through Data Cloud.

The trap is that an existing WhatsApp number on the older channel cannot simply be upgraded to Unified Messaging. The two are architected differently, so moving across is a new channel setup rather than a switch you flip. In practice that means re-doing the connection, re-establishing templates and routing, and planning for the change rather than treating it as a maintenance task.

There are two sensible responses. If you are setting up WhatsApp on Salesforce for the first time and you know marketing will want the channel too, look at Unified Messaging now rather than doing this twice. If you already run the service-only channel and marketing does not need WhatsApp yet, there is no urgency, but scope the migration honestly when the request arrives instead of promising a quick change.

Unified Messaging also brings a Data Cloud dependency. You connect the WhatsApp Business Account and number, then deploy data kits and streams so segments can be targeted and engagement captured. That is not a difficult step, but it is a step, and it needs somebody who knows your Data Cloud setup.

Before you start: what you need ready

Gather these before touching a setting. Every one of them has stalled a rollout mid-way.

A Meta Business account, verified. You need a Meta Business account with business verification complete or under way. Verification asks for documents proving the business is real and approval is not instant. Start it first, because everything else waits on it.

A phone number that is free. The number you connect cannot be active on the normal WhatsApp app or the WhatsApp Business app. If your business number is already in use there, you must remove it first, and the chat history on that device is lost when you do. Many teams take a fresh number and move customers across gradually.

The right licences and permissions. Confirm the Digital Engagement question above, confirm your Service Cloud edition is eligible, and make sure whoever does the setup has admin rights in both Salesforce and Meta Business. Half-finished setups are usually a permissions problem, not a technical one.

Clean phone numbers in Salesforce. The channel matches incoming numbers to records as text. If your data has a mix of spaces, dashes, missing country codes and leading zeros, matching will fail on a large share of your contacts and agents will see strangers instead of customers. Standardise to one international format before you go live, not after.

A short list of message templates. Decide the first three or four messages you want to send outside a live conversation, because those need Meta approval before they work. A new lead acknowledgement, an appointment reminder, and a case or order status update cover most of what teams actually need on day one.

Setting up the native Salesforce WhatsApp channel

The order below is the one that avoids rework. Salesforce moves its setup screens between releases, so treat these as steps rather than a click script, and check the current Salesforce Help article for exact navigation.

Step one: prepare Meta. Log into Meta Business, confirm the business account exists and verification is under way, and check the number you plan to use is free of both WhatsApp apps. Doing this first prevents the most common failure, which is getting several screens into Salesforce Setup and finding the number unavailable.

Step two: turn on Messaging and pick your channel generation. In Salesforce Setup, enable Messaging, then decide between the service-only channel and Unified Messaging using the previous section. Decide this now. It is expensive to change later.

Step three: connect the WhatsApp Business Account and number. Run the Meta login and permission flow, choose the number, complete verification, and set the display name customers will see. Use the business name people recognise, not an internal label, because this is what appears on their phone.

Step four: route the conversations. Configure the messaging channel, queues, omni-channel routing and agent capacity, and set your working hours. Unassigned WhatsApp conversations are the fastest way to lose a team that was told this would be an improvement. Routing is not a finishing touch, it is the setting that decides whether the pilot feels better or worse than a phone.

Step five: create and submit templates. Build the messages you listed and submit them for approval. Approval usually takes anywhere from minutes to a day. Write them as specific, useful messages rather than promotional filler, because vague marketing copy is the most common rejection reason.

Step six: test properly. Message the business number from a phone that is not a team phone. Confirm the conversation lands in the right queue, the contact is matched or created correctly, an outgoing reply arrives, and the whole exchange is visible on the record. Then repeat with a number already in Salesforce, which is the test that exposes phone-format problems while they are still cheap.

Step seven: go live with one team first. Point one queue or one campaign at the channel for a week before moving everyone. Problems found by three people are cheap. The same problems found by thirty become the reason a project gets quietly abandoned.

Automating WhatsApp with Flow

Once conversations are landing, automation is where the payback is, and one rule governs all of it.

WhatsApp allows free-form replies only for a limited period after the customer’s last message, commonly twenty-four hours. Inside that window you can send normal messages. Outside it, you can only send a template Meta approved in advance. Every automation you design has to respect this, and it is the single thing that catches teams out when their first Flow silently fails.

The automations worth building first are simple ones. An instant acknowledgement when a web-to-lead form is submitted tends to produce the biggest measurable lift, because it lands while the person is still interested rather than three hours later. An appointment or demo reminder cuts no-shows, usually the easiest number to move in the whole business. A case status update removes an entire category of incoming questions your agents currently answer by hand.

Two design habits stop this going wrong. Send WhatsApp from a Flow only when the message is genuinely useful to the person receiving it, because WhatsApp is a personal channel and people block businesses far faster than they unsubscribe from email. And always leave a human path, so that a reply to an automated message reaches a person quickly instead of sitting in a queue nobody watches.

What the integration costs in 2026

There are three separate bills and most plans account for one.

Salesforce licensing. The Digital Engagement add-on per user, on top of the Service Cloud seats your agents already need, plus a Data Cloud dependency if you go the Unified Messaging route. On a large service team this is comfortably the biggest line in the project, and because it is per user it grows with headcount rather than with usage.

Meta’s messaging charges. Meta bills business-initiated conversations by country and by category, with marketing messages costing more than utility ones. Conversations the customer starts, and your replies inside the open window, are treated far more cheaply. Salesforce’s included per-user allowance offsets a small part of this, and everything beyond it is consumption. Meta has revised this model more than once, so check the current rate card for the countries you message rather than trusting a figure from any blog post, this one included.

Setup and change time. The line everyone forgets and the one that actually decides whether it works. Verification, number migration, template writing and approval, phone-number cleanup, Flow building, routing design, and persuading a sales team to change where they type all take real hours. Budget them honestly.

The consistent pattern across rollouts is that Meta’s messaging spend comes in lower than people fear, while licensing and setup effort come in higher than people plan. Build the budget in that shape.

If that per-agent maths is what is stopping the project, it is worth pricing the alternative properly before you shelve the idea. Lion CRM’s pricing is built around per-licence costs rather than a per-seat CRM add-on, which is a materially different curve once a messaging team passes about ten people.

What the native Salesforce WhatsApp integration cannot do

The native channel is good at what it is designed for. It is worth being explicit about where it stops, because these gaps are why teams add a second tool later.

Large broadcast campaigns from the service side. The service channel is built around agent conversations, one thread at a time. Sending a segmented campaign to thousands of contacts with delivery reporting, retry handling and per-segment results is a different job. Unified Conversations closes part of this if you own Marketing Cloud. If you do not, a dedicated platform is the realistic answer.

Chatbots and deep self-service routing. Automated qualification flows, menu-driven self-service and rule-based routing across shifts and languages usually need building or buying. If you want a bot to handle the first three questions before a human joins, expect to add a tool or a substantial project.

A chat-first way of working. The console is a case console. Teams who live in chat all day tend to want a pipeline they can see and drag conversations through, and that visual, chat-first workflow is not the shape of a service console. This is a genuine adoption risk rather than a feature checkbox, and it is the most common reason a technically successful setup ends up unused.

Your own branding. Everything the client sees says Salesforce. For an agency that is a commercial problem, which is the next section.

None of these are reasons to avoid the native channel. They are reasons to know which category you are in before you buy, so you buy once rather than twice.

The whitelabel route: selling this setup to clients

If you are a consultancy, an implementation partner or an agency, there is a business decision underneath the technical one, and it is worth considerably more than the setup fee.

Configuring a client’s Salesforce WhatsApp channel is a project. You scope it, you deliver it, you invoice once, and the client now owns something that runs without you. It is honest work and it pays honestly, and then it ends.

Selling a branded WhatsApp CRM is a product. The client works in a platform carrying your name and your logo, they pay every month, and you keep the margin between what the platform costs you and what you charge them. The setup work is similar. The revenue recurs instead of stopping, and it compounds with every client you add.

The two are not in conflict, and the useful question is where the client’s work genuinely happens. If Salesforce is truly the centre of the business, with service, pipeline and reporting all living there, then connecting WhatsApp to it is the right recommendation and you should make it. If the sales team spends its day in chat and Salesforce is mostly a system of record, a branded chat-first platform will get used every day while a console channel quietly gets abandoned. In that case the branded route serves the client better as well as you.

For agencies taking that route, the practical requirements are the ones that decide whether the business scales: your own domain and logo throughout, the ability to create and manage client accounts yourself without asking a vendor, per-licence pricing you control, and a support path that never exposes the platform behind your brand. Lion CRM’s whitelabel programme is built around exactly that shape, starting at a minimum of ten licences with the reseller admin panel needed to run client accounts under your own brand.

Common problems and how to fix them

The number will not connect. Almost always because it is still active on the WhatsApp or WhatsApp Business app. Remove it there first, accept that the on-device history goes with it, then retry. The second most common cause is Meta business verification that has not finished.

Messages arrive but do not attach to the right record. This is a phone-format problem, not a settings problem. Matching happens on the number as text, so a leading zero, a missing country code or stray spaces will stop it finding a contact a human can see is the same person. Standardise the database to one international format and retest.

Templates keep getting rejected. Rejections usually come from vague promotional wording, variables without surrounding context, or a category that does not match the content. Rewrite the message as something specific and genuinely useful, make the variables obviously meaningful, and resubmit. Copying the tone of a transactional email works far better than copying the tone of an ad.

Flows are not sending WhatsApp messages. Check the messaging window first, because a Flow trying to send free-form text outside the open window fails by design. If it is an approved template and it still fails, confirm the template is active, the channel is the one the Flow references, and the sending user has the Digital Engagement licence.

We cannot move our number to Unified Messaging. You cannot, not as an upgrade. The channels are architected differently and moving across is a new setup. Plan it as a small project rather than a configuration change.

The team is not using it. Nothing here is technical. Either routing is wrong so conversations do not reach the right person, or the tool does not match how the team works. Watch someone use it for an hour. The answer is usually obvious inside ten minutes and is almost never the one raised in the meeting.

A 14-day rollout plan

Days 1 to 3: preparation. Start Meta business verification, confirm the Digital Engagement licences and your Service Cloud edition, decide between the service-only channel and Unified Messaging, free up or choose the phone number, and begin the phone-number cleanup in Salesforce. Verification and data cleanup run in the background, so starting them on day one takes them off the critical path.

Days 4 to 6: connection. Enable Messaging, connect and verify the number, set the display name, and configure queues, omni-channel routing, agent capacity and working hours. Do not skip routing.

Days 7 to 9: templates and testing. Write and submit the first three or four templates. While they are in review, test the inbound path hard, from outside numbers and from numbers already in Salesforce. Fix the matching problems this uncovers before anybody else sees them.

Days 10 to 12: pilot. One queue, one campaign, real customers. Watch what happens rather than asking for feedback in a meeting. Build the first Flow, usually the instant reply to a form submission, and confirm replies to it reach a human quickly.

Days 13 to 14: rollout and measure. Extend to the rest of the team with a short written guide covering the three things they must do differently. Record your starting numbers now, because first response time and reply rate are what you will be judged on in a month, and nobody remembers what they were beforehand.

Frequently asked questions

Does Salesforce have a native WhatsApp integration?
Yes. Salesforce supports WhatsApp natively through Messaging in Service Cloud, and through Unified Conversations for WhatsApp, which shares one number and one customer profile across marketing and service. The qualifier that matters is licensing: native WhatsApp needs the Digital Engagement add-on on top of Service Cloud rather than being included in a standard seat. Confirm your edition and licences against Salesforce’s current pricing page before scoping any project around it.

What licence do I need for WhatsApp in Salesforce?
Your agents need a Service Cloud licence and the Digital Engagement add-on, listed at around 75 dollars per user per month at the time of writing on eligible editions. Because it is per user, the cost scales with how many agents touch the channel rather than with message volume. If you go the Unified Messaging route there is also a Data Cloud dependency for the data kits and streams that make segmentation and engagement tracking work.

How much does a Salesforce WhatsApp integration cost?
Plan for three bills. Salesforce licensing, which is the per-user Digital Engagement add-on and is usually the largest line. Meta’s conversation charges, which vary by country and message category, offset slightly by the small allowance included per user. And setup time, the line most often left out, covering verification, number migration, template approval, phone-number cleanup and Flow building. Messaging spend usually lands lower than teams expect while licensing and setup land higher.

Can I upgrade my existing Salesforce WhatsApp number to Unified Messaging?
No, not as an upgrade. Unified Messaging is architected differently from the standalone service channel, so moving across is a new channel setup rather than a switch. In practice that means redoing the connection, templates and routing. If you are setting WhatsApp up for the first time and you expect marketing to want the channel eventually, choose Unified Messaging now so you do not do the work twice.

Can Salesforce Flow send WhatsApp messages automatically?
Yes, within WhatsApp’s rules and on the right licences. Outside the roughly twenty-four hour window after a customer’s last message you can only send a template Meta approved in advance, so every automation must be designed around that window. The highest-value ones to build first are an instant reply to a form submission, an appointment reminder, and a case or order status update.

Should I connect WhatsApp to a client’s Salesforce or sell them my own branded CRM?
It depends on where the client’s work actually happens, and either can be right. If Salesforce is genuinely the centre of the business, a connector is the honest recommendation and you should make it. If the sales team lives in chat all day, a branded chat-first platform will get used while a console channel gets abandoned. For an agency the branded route is also the better business, because a setup fee is earned once while a monthly per-licence margin keeps paying. Agencies comparing platforms to resell usually start with the whitelabel WhatsApp CRM comparison for India.

Become a Reseller