Salesforce And WhatsApp Integration: The Complete Orchestration Guide

It is 9:47 on a Tuesday night. A buyer named Rohan taps a Click-to-WhatsApp ad, opens a chat, and types one line. "Is the financing still available on the sedan?" Nadia, an inside sales rep, answers in ninety seconds. Rohan asks two more questions, then goes quiet. Warm lead, live intent, real money on the line.

The next morning, Nadia opens Salesforce. Rohan is there. A name, a phone number, a form-fill from the ad. The Salesforce WhatsApp integration did exactly what it promised. It logged the message and stamped the record.

But the thread is cold. The urgency is gone. Nobody followed up at 9:52 because nothing told Salesforce to. The moment that could have closed died in the gap between a chat window and a CRM field. That gap is the whole story.

What is the Salesforce WhatsApp integration?

The Salesforce WhatsApp integration connects WhatsApp Business messaging to Salesforce so agents and marketers can send and receive WhatsApp messages inside Service Cloud and Marketing Cloud, log them on CRM records, and run template-based journeys. It works through Digital Engagement, Marketing Cloud, or the Meta WhatsApp Business Platform via a Business Solution Provider.

That definition is accurate. It is also where most teams stop reading and start assuming. The assumption is that a logged message equals a living conversation. It does not.

Whichever path you take, the plumbing underneath is the same. You need a WhatsApp Business Account verified by Meta, a dedicated phone number, and pre-approved message templates for any outbound message you send outside a live reply window. Approval is not instant. Account verification commonly runs three to five business days, and new numbers add a few more, so a WhatsApp launch is a project, not a checkbox. Knowing this up front is half the battle.

What the native integration does well

Let us be fair before we get honest. Salesforce built a serious WhatsApp capability, and for large parts of the job it works.

• Two-way service conversations. With Digital Engagement, agents handle WhatsApp threads inside the Service Console, with routing, agent assignment, and queue rules. Support runs where support already lives.
• Template-driven marketing. Marketing Cloud sends outbound WhatsApp templates through Journey Builder, so reminders, offers, and transactional updates fire on a schedule alongside email and SMS.
• Unified Conversations. Since its general availability in April 2024, Unified Conversations for WhatsApp lets marketing and service share a single WhatsApp number and thread, with handoffs powered by Salesforce Data Cloud.
• Everything on the record. Messages attach to the contact, the case, and the campaign, so the history is auditable and reportable.
• AI inside the console. Salesforce layers its own assistants over WhatsApp for Service Cloud, so agents get suggested replies and summaries without leaving the record. For teams standardizing on one AI vendor, that consolidation is real value.

If your WhatsApp use is support tickets and scheduled campaigns, and you already live deep inside the Salesforce clouds, the native route earns its keep. Credit where it is due.

Log every message on the record.

Where the native integration stops

Here is the quiet failure. The native integration syncs messages and form-fills into Salesforce. A synced field records what happened. It cannot act on what is happening.

Call it The Form-Fill Fallacy. A form-fill is a snapshot of a lead at one instant. It carries a name and a number. It does not carry the intent Rohan showed at 9:47, the urgency in his second question, or the fact that the thread is still open and warm at 9:53. Sync moves data. It does not move context.

Now stretch that across channels. Rohan chatted on WhatsApp, opened an email two days later, and clicked back to the site the following week. Native tooling treats each of those as a separate event on a profile. The live conversational state, what he wants and how badly he wants it right now, never travels with him. That break has a name too. The Handoff Cliff. Context walks up to the edge of one system and falls off before it reaches the next.

Unified Conversations helps here, and it should get credit. But it leans on Data Cloud to assemble a unified profile, which is another paid layer, and a profile is a summary of the past. It is not the same thing as a running conversation that can trigger the next action the second intent spikes. Attribution feels the same strain. When a WhatsApp-sourced deal takes longer than a week to close, the ad platform quietly undercounts it, and the credit for that conversation evaporates.

There is a second wall most teams meet late. WhatsApp only lets you message freely inside a window. When a customer writes to you, a service window opens and you can reply openly for a day. Once that window closes, every proactive message has to be a pre-approved template. That is fine for a scheduled reminder. It is a problem when a lead goes quiet for two hours and the natural next move is a warm, specific nudge that no template quite covers. The native tools respect the window. They do not help you win the race inside it. Call that gap The Golden-Window Gap, and understand that scheduled journeys were built for calendars, not for the ninety seconds when a buyer is still leaning in.

Carry the context, not only the contact record.

The three ways to connect Salesforce and WhatsApp

There is no single "WhatsApp button" in Salesforce. There are three architectures, and choosing well starts with seeing them clearly.

Path one: the native route

Digital Engagement plus Marketing Cloud, wired straight into Salesforce. You buy the add-ons, connect a Meta-approved WhatsApp Business Account, and message from inside the clouds you already own. Best when support and scheduled campaigns are the whole job and IT wants everything under one vendor. The trade is cost and rigidity. Every capability is a license, and real-time cross-channel logic is not the design goal.

Path two: a BSP on the Meta WhatsApp Business Platform

A Business Solution Provider sits on Meta's WhatsApp Business Platform, handles WABA onboarding and template approvals, and offers a prebuilt Salesforce connector. Setup is faster and lighter, often live in days rather than a quarter, and you gain channel features the native route lacks. Most BSPs also give you a visual builder, campaign tooling, and sometimes a bundled chatbot, which is why smaller teams reach for them first. The trade is twofold. The BSP owns the conversation surface, so your live thread lives in their inbox rather than in Salesforce. And the CRM connection is still a sync. Messages flow into Salesforce as records after the fact, not as live state a workflow can reason over in the moment. You also pay a per-message markup on top of Meta's base rate, which is easy to miss when you compare sticker prices.

Path three: an orchestration layer on top

A coordination layer sits above both Salesforce and WhatsApp, keeps one continuous thread of context per person, and triggers actions the instant intent changes. It does not replace the CRM or the messaging channel. It connects them, remembers across them, and acts between them. This is the path built for the 9:47 problem, and we will come back to it.

A comparison of the three connection paths

Pricing below is a third-party estimate as of 2026 and depends on your vendor, region, and message mix. Meta moved to per-delivered-message pricing on 1 July 2025, split across marketing, utility, authentication, and service categories, with service-window replies free.

Read across the "context continuity" row slowly. Record-level and sync-level both describe storage. Only one row describes memory that moves.

When you need an orchestration layer on top

Some teams do not have a messaging problem. They have a coordination problem wearing a messaging costume. Their WhatsApp works, their Salesforce works, and revenue still leaks in the seams between them.

Meet Priya, a RevOps lead at a mid-market lender. Her CTWA ads perform. Her reps are quick. But a third of qualified WhatsApp chats stall because the follow-up depends on a human noticing a record change and acting inside the golden window. Priya does not need another inbox. She needs the conversation to remember itself as it crosses from WhatsApp to Salesforce to email, and she needs an action to fire the moment intent spikes.

That is what an orchestration layer does. Zigment sits on top of Salesforce and WhatsApp as a Conversational Revenue Orchestration Platform, powered by its Conversation Graph, a single stateful timeline per person that holds clicks, chats, forms, and calls along with the intent, urgency, and sentiment behind them. Workflows react to meaning, not to a stale field. When Rohan asks about financing at 9:47, the layer already knows the ad he came from, replies in context, and triggers the next best action before the thread goes cold. It is the difference between orchestrating and merely automating.

The results follow the coordination, not the channel. Teams see around 40% higher conversions on inbound demand when context stops breaking at the handoff. Bajaj runs context-preserving handoffs across more than twenty countries on this model, so a conversation that starts on WhatsApp does not restart from zero when it reaches a human or a system in another market. This is also how you revive a dead lead by moving it from email back into a live WhatsApp thread without losing the plot, and how you unify a channel like WhatsApp with the rest of your CRM and support stack instead of stapling it on.

Act on intent, not aftermath.

How do you choose the right path?

Start with one question. What has to survive the handoff?

Choose the native route if your WhatsApp job is support cases and scheduled campaigns, you are already committed to Digital Engagement and Data Cloud, and you value single-vendor consolidation over real-time cross-channel logic.

Choose a BSP if you need WhatsApp live quickly and cheaply, want richer channel features, and can accept that the CRM connection stays a sync rather than a shared brain.

Add an orchestration layer if context has to travel across Salesforce, WhatsApp, and email, if the money is won or lost inside a golden follow-up window, and if you want the next best action to fire on intent rather than on a batch schedule. This is not a rip-and-replace. It is a coordination brain on the stack you already own.

Many teams end up running two of these at once. They keep native Digital Engagement for support cases, and they add a coordination layer for the revenue conversations where speed and context decide the outcome. The paths are not mutually exclusive. The mistake is assuming one architecture has to do every job.

For most support teams, the native integration is enough. For a growing number of revenue teams, the honest answer is a layer that keeps the conversation whole.

The bottom line

The native Salesforce WhatsApp integration is good at recording conversations. It was never designed to keep one alive as it moves across your systems. That is a different job with a different name, and the name is Conversational Revenue Orchestration.

Rohan was not a lost lead. He was a won deal that no system was awake to catch. The question is not whether Salesforce and WhatsApp can talk. They can. The question is whether the conversation between them remembers anything at 9:52, when the deal is still on the table.

See how an orchestration layer fits on your Salesforce and WhatsApp stack. Keep the conversation alive.