You can connect WhatsApp to Salesforce in two ways. Salesforce has its own WhatsApp channels, in Messaging settings for Service Cloud and in Marketing Cloud Engagement, or you can run WhatsApp in a helpdesk that reads and writes Salesforce records. The native route puts chats inside Salesforce, and the helpdesk route keeps Salesforce as the record system behind a separate inbox and AI agent.
Route 1: Salesforce's own WhatsApp channels
The facts in this section come from Salesforce Help articles on WhatsApp channels and on Digital Engagement, summarised on 11 November 2026. Licensing and menus change between Salesforce releases, so confirm each point on Salesforce's own pages before you commit.
What you need
Salesforce messaging licences. Salesforce's help says to confirm that you have bought Digital Engagement, or the add-on that applies to your edition, before using WhatsApp Business messaging. With some add-ons, message credits must be purchased before a channel can be created.
A Meta Business Manager account, called a business portfolio today. WhatsApp ties your number and your WhatsApp Business account to it.
A phone number you own, with a valid country and area code, able to receive a text or a voice call. SMS short codes are not allowed, and Salesforce says its own Digital Engagement numbers are SMS-only, so you bring your own number. A number already used with another business service provider can be migrated.
Permissions in Salesforce to configure messaging, which in practice means an administrator.
Steps in outline
In Setup, open Messaging Settings and choose New Channel, then WhatsApp, then the Enhanced option.
Log in with your Facebook credentials, then create or select a Meta business account and a WhatsApp Business account.
Verify the phone number.
Set up message templates, which WhatsApp must approve before you can use them.
Route the channel to your agents and activate it.
Rules to plan around
Create the WhatsApp Business account inside Salesforce's setup flow. Check Salesforce's current help page before you reuse a WhatsApp Business account that was created elsewhere.
One WhatsApp Business account connects to one Salesforce org. A sandbox and a production org count as two, so a test setup needs its own WhatsApp Business account.
If you do not activate the channel within 14 days of creating it, Salesforce says you must verify your number with WhatsApp again.
Marketing Cloud Engagement and Service Cloud channels use separate WhatsApp Business accounts.
Route 2: a WhatsApp helpdesk connected to Salesforce
With this route, WhatsApp runs in a helpdesk, and Salesforce stays the place customer records live. The helpdesk handles the inbox, assignment and AI, and talks to Salesforce for data.
In Volty, the Salesforce connection works like this.
Volty reads the customer's account, contract and open cases in Salesforce before it replies.
It can log new leads and cases from the conversation once an admin allows it. The tool switches decide what it may read and change, and an admin sets each one.
It sees what the user who signed in can see. In a customer conversation Volty looks up only the customer the conversation has verified.
The same agent answers on WhatsApp, Instagram, Messenger, web chat and email, so Salesforce is kept current from every one of those channels.
How the two routes compare
| Factor | Salesforce native channel | Helpdesk plus Salesforce |
|---|---|---|
| Where agents work | Inside Salesforce | In the helpdesk inbox, with Salesforce data shown or used by the AI |
| Licensing | Salesforce messaging licences and add-ons | The helpdesk plan, plus whatever Salesforce edition you already have |
| Setup effort | Admin work in Setup, Meta verification | Connect WhatsApp, then connect Salesforce |
| Other channels | Salesforce has its own channels for each | One inbox for WhatsApp, Messenger, Instagram, web chat and email |
| Best for | Teams who run service entirely in Salesforce | Teams who want a lighter inbox and AI beside Salesforce |
What to decide before you build
The object that represents a WhatsApp customer. A contact, a lead, or a person account? Pick one and match on phone number.
When a conversation becomes a case. Every message, or only those that match a rule?
Who owns the follow-up, and how the owner is set when a lead is created from a chat.
Which fields an AI agent may change. Salesforce records often hold contract and finance data, so start with read access and add writes one tool at a time.
How templates are named and approved, since WhatsApp must approve each one.
Use cases worth building first
Case status on request
A customer writes "Where is my case 00123?" The agent finds the verified customer in Salesforce, reads the open case and replies with its status and next step. The agent answers a common question that would otherwise reach a person, and Salesforce stays untouched because it was only read.
Lead capture from a first message
A new number asks about pricing. The agent collects name, company and need in two or three questions, then logs a lead with the conversation attached, once an admin has allowed writes. Sales opens a lead that already carries the context.
Account-aware replies
For an existing customer, the agent can look at the account and contract before it answers a renewal or entitlement question, so it does not give an answer that contradicts the contract.
Handover with context
When the question needs a person, the owner named in Salesforce receives the thread, with a summary of what the customer asked.
Mistakes that make integrations fail
Turning on write access for everything on day one. Start with reading, review a week of conversations and then enable one write at a time.
Matching on names. Two customers share a name far more often than they share a phone number.
Skipping the sandbox. A change to routing or fields should be tried in a sandbox first, remembering that it needs its own WhatsApp Business account.
Forgetting the human route. Every automated flow needs a clear way to reach a person.
Leaving templates until the end. Approval takes time, so submit them early.
Not training staff on the handover. People need to know what the agent already asked, so they do not ask it again.
The WhatsApp rules that apply in both routes
Salesforce and every helpdesk are bound by Meta's rules. After a customer's last message a business has 24 hours to send free-form replies, and after that it needs an approved template. Messages you start need an opt-in, and Meta charges for template messages by category and country. The details are in the 24-hour rule guide and the pricing guide.
Check it works before it is live
Send a test message from a known customer's number and confirm the right Salesforce record is found.
Send one from an unknown number and confirm the lead or case behaves as you decided.
Ask the AI a question that depends on a case status and compare its answer with Salesforce.
Try to make the AI reveal another customer's record. It should not, and if it does, tighten access before launch.
Salesforce and WhatsApp in Volty
If you already run Salesforce and want a WhatsApp inbox and AI agent beside it, see Volty's Salesforce integration and the WhatsApp AI agent. Plans start with a free 7-day trial, and the pricing page lists current prices, which can change.
Frequently asked questions
Does Salesforce support WhatsApp natively?
Yes. Salesforce offers a WhatsApp channel in its Messaging settings for service teams, and a separate WhatsApp messaging option in Marketing Cloud Engagement. They use separate WhatsApp Business accounts, so plan which one each team needs.
What do I need before connecting WhatsApp to Salesforce?
According to Salesforce Help, a Meta Business Manager account, a phone number you own that can receive a text or a call, the right Salesforce licence for messaging, and the Configure Messaging permission. Check the current requirements on Salesforce's own help pages before you start.
Can one WhatsApp Business account connect to two Salesforce orgs?
Salesforce Help says a single WhatsApp Business account cannot be associated with more than one Salesforce org, and that a sandbox and a production org count as two. Create separate accounts for each environment you need.
Can I connect WhatsApp to Salesforce without the native channel?
Yes. A WhatsApp helpdesk can read and write Salesforce records once an admin signs in to Salesforce to connect it. Volty reads a customer's account, contract and open cases before replying and logs new leads and cases from the conversation when an admin allows it.
Do WhatsApp's 24-hour rules still apply with Salesforce?
Yes. They are Meta's rules, so they apply to any tool you use. After a customer's last message you have 24 hours for free-form replies, and after that you need an approved template message.










