Salesforce WhatsApp Integration: The Complete 2026 Guide

Your customers are already on WhatsApp. All two billion of them, roughly. So the real question was never whether to show up there. It’s whether your Salesforce team can do it without babysitting a second app all day.

Salesforce WhatsApp integration connects your org to WhatsApp Business, so messages and context sit right there on the record, where reps already work anyway. Some teams get this running in a week. Others stall for months, stuck on template approval or blindsided by a 24 hour messaging window nobody bothered to mention. Nobody warns you about that window until you hit it.

This guide walks through the routes available, what to line up before you start, and the handful of factors that decide whether your setup runs clean or turns into a mess.

Can you use WhatsApp inside Salesforce?

The clear answer is yes.

There can be 3 ways to help you with this. Salesforce Digital Engagement. A native WhatsApp for Salesforce.AppExchange app built for messaging. Or a direct build against the WhatsApp Business API, with your own developers owning it end-to-end. 

All three land you in roughly the same place: a two-way WhatsApp channel wired into Leads, Contacts, and Cases. Where they split apart is what happens after that connection exists. Does the channel just send messages? Or does it think? Is it a native app like 360 SMS with AI built in that turns WhatsApp into something more than a channel, helping you text smarter and drive better outcomes?

How do the WhatsApp Integration Routes Compare?

Pick blind, and you’ll be rebuilding this in six months. Here’s what actually separates the three.

Route	Setup Effort	Who Owns It	Channel Breadth	Cost Model	Marketing Cloud Support
Salesforce Digital Engagement	Moderate	Salesforce admin/team	WhatsApp plus other Digital Engagement channels	Salesforce licensing + Meta conversation fees	Limited, mostly Service Cloud
Native AppExchange app (e.g., 360 SMS App)	Low	Admin, no dev team	SMS, WhatsApp, and 13 more in one app	App license + Meta conversation fees	Available
Direct Business API build	High	Internal dev team or agency	WhatsApp only, unless you build further	Dev cost + hosting + Meta fees	Requires custom middleware

 

If you’re already deep in Service Cloud and don’t need much past WhatsApp, Digital Engagement is fine. A direct API build hands you total control. And total ownership of every bug, every Meta policy shift, every 2 am maintenance call that comes with it. 

The AppExchange route sits in the middle. Worth being specific about why 360 SMS App tends to win this comparison for team messaging at real volume: the AI layer isn’t SMS-only. Smart replies, template scoring, drip suggestions, all of it runs on WhatsApp the same way it runs on SMS, because it’s built at the channel-agnostic level. Not bolted onto one number type as an afterthought.

Still weighing which AppExchange tool actually fits your team? Comparing WhatsApp apps lays the options side by side.

What you need before you start

Nobody mentions this part until you’re already stuck in it.

Before you touch Salesforce, get the Meta side sorted first. You’ll need a Meta Business portfolio, a phone number that can actually receive an SMS or voice verification code, and a display name that fits Meta’s guidelines. Sounds simple. It rarely is.

Here’s where people get tripped up.

• Your phone number: This is the big one. Already registered with regular WhatsApp? You’ll need to remove it, deregister it, before it can work with the WhatsApp Business Platform. Skip this step and the setup just stalls on you..
• Your display name: It needs to clearly relate to your business and follow WhatsApp’s naming and business policy requirements.
• Your business details: Keep your legal business name, website, address, and phone details consistent across your Meta business portfolio and website. This can make Business Verification smoother.
• Your Meta verification: Business Verification isn’t necessarily the first step, but completing it is important if you want the business display name to appear properly across WhatsApp conversations and to move beyond the initial setup limitations.
• Your timeline: Don’t assume every approval happens instantly. Meta’s verification and review steps can take time, so it’s better to start them before you’re ready to configure Salesforce.

Get the Meta-side pieces moving first, then tackle the Salesforce configuration. That way, you’re not halfway through the setup only to discover that the number or business details still need attention.

Also, if you’re using and prioritizing WhatsApp in Marketing Cloud over other Salesforce clouds, 360 SMS experts can help accommodate your specific requirements. 

How WhatsApp templates work

Most guides skip this part. It’s the one that can make or break your campaign timeline.

When you message a customer outside the 24-hour customer service window, you generally need an approved WhatsApp template. Inside that window, you can use free-form messages as part of the ongoing customer conversation.

Meta currently groups templates into three categories:

• Marketing: Promotions, offers, announcements, and broader customer outreach.
• Utility: Transactional or customer-requested updates, such as order updates, appointment reminders, and account notifications.
• Authentication: Authentication messages such as OTPs, account verification, and login codes.

Placeholders fill in the details. For example, {{1}} could hold a customer’s first name and {{2}} an order number, with your CRM or integration supplying those values when the message is sent.

The category matters. A template should match its actual purpose and content. Meta can reject a template during review or reclassify it later if its content doesn’t fit the category you’ve selected.

Approval also isn’t always instant, so don’t leave templates until the day you plan to launch a campaign.

This is where a native AppExchange app can help. With 360 SMS, Template Quality Score gives you an additional check before submission, while Rephrase & Polish Content can help improve the message itself. The goal is simple: catch avoidable content and formatting issues before you send the template to Meta for review.

For teams running WhatsApp campaigns from Salesforce, that extra check can save a lot of back-and-forth during setup.

For your convenience, 360 SMS can also provide pre-made WhatsApp templates and handle the WhatsApp Business API approval process for you within 4 weeks, helping you get ready to send without navigating Meta’s requirements alone. 

The 24-hour window and what it means for your workflows

Here’s the rule that quietly governs everything else. Once a customer messages you, there’s a 24-hour customer service window to reply with anything; no template required. Close that window, and you’re back to templates, full stop.

This reshapes how you plan follow-ups. An agent replying at hour 23 can write whatever they want. Same agent, same conversation, hour 25, needs an approved template or the free-form message won’t go through. Sales teams get burned by this constantly. Send a casual “just checking in” two days after a lead went quiet, and it won’t go through because nobody built for the window closing in the first place.

The fix is boring but it works. Build automation that flags a conversation before the window closes, then queue the right template ahead of time. Skip this, and teams end up staring at a pile of undelivered messages with no obvious reason why. Someone eventually cracks open Meta’s docs and finds the answer three weeks too late.

Consent, opt-out and number quality

Meta isn’t just watching what you send. It’s watching how people react to it.

Every WhatsApp Business number carries a quality rating. That rating can affect your messaging limits and capabilities. Too many blocks or reports, and Meta can reduce how many new conversations you can start. Keep it up long enough, and the number can face restrictions.

Consent works differently here than on other channels, because customers should opt in before you message them first. Honoring opt-outs isn’t a nice-to-have. It’s what keeps the quality rating from tanking. 

This is where 360 SMS App’s AI compliance monitoring actually earns its place on WhatsApp, not just SMS. It reads intent, not keywords. “Please stop bothering me” gets caught the same way a flat “STOP” does, and compliance risk gets flagged in a live conversation instead of after the damage lands. Keyword matching alone misses too much, and on a channel where reputation can affect your ability to message, that gap costs money.

Treat number quality like sender reputation on email. Because functionally, that’s what it is.

What does it cost?

Two costs stack here. Confuse them, and the budget takes the hit.

Meta’s pricing model shifted on July 1, 2025. Replies inside the 24-hour customer service window are free, with no Meta charge for service messages during that window. What costs money is template messages, the ones you send outside that window, and Meta bills those per delivered message rather than per conversation, with rates set by template category and country. Then there’s the platform cost, either a Digital Engagement license, an AppExchange subscription, or the dev and hosting spend a custom build racks up over time. 

No exact figures here. Meta’s per-message rates move on their own schedule, and stale numbers help nobody. What matters is understanding this two-layer structure: service replies are free, templates are billed per message, plus your platform cost on top, before committing. That way, finance isn’t blindsided three months in, wondering where the extra line item came from.

Want a current quote based on your actual message volume? Connect with the 360 SMS App team.

What teams actually use it for

A lead fills out a form, Salesforce fires a WhatsApp message, and the rep gets a live conversation instead of a cold callback three hours later. Reps working WhatsApp threads inside the 360 SMS app get AI-suggested replies pulled straight from the conversation itself, not a generic script. Edit before sending, or send it as suggested. Support teams turn incoming WhatsApp messages straight into Cases, thread and all, nothing lost in the handoff. Marketing runs filtered, personalized broadcasts through Campaigns and watches responses land back in the CRM without anyone touching a second dashboard.

That’s the short version. For the deeper breakdown by use case, see WhatsApp use cases for sales and support.

Wrapping Up

WhatsApp inside Salesforce isn’t the hard part. It rarely is. The friction lives in Meta’s approval queues, in a 24-hour window nobody flags until it costs someone a follow-up, in a quality rating that can affect how many conversations you can start in a day.

Get the setup right once. Pick a route that actually matches your team’s technical bandwidth. The rest holds together on its own after that. Your reps are already in Salesforce. Your customers are already on WhatsApp. Closing that gap isn’t really a leap; it’s just a decision somebody has to make.

Need help choosing the right WhatsApp setup for Salesforce? 

Talk to the 360 SMS experts.