Salesforce WhatsApp and SMS Integration: Options, Setup and Compliance

What a Salesforce WhatsApp and SMS integration does

Customers in the US read texts faster than email, and many international customers expect WhatsApp. An integration brings those conversations into Salesforce instead of leaving them on agents’ phones or in a separate inbox. A good setup gives you five things:

• Two-way conversations on the record. Agents read and reply in Salesforce, and the thread is linked to the Contact, Lead, Case or Opportunity.
• Routing. Incoming messages go to the right queue or agent, or to a bot first, like any other service channel.
• Automated notifications. Flows send appointment reminders, order updates, payment links or verification codes when a record changes.
• Campaigns. Marketers send segmented SMS or WhatsApp journeys to people who opted in.
• Consent tracking. Opt-ins and opt-outs are stored in Salesforce, so no one texts a customer who said STOP.

Service teams care most about routing and conversation history. Sales teams want one-to-one texting from the record. Marketing wants campaigns and consent. Decide which of these you need first, because they point to different products.

WhatsApp and SMS are not the same channel

Teams often plan them as one project. The rules behind them differ enough that you should treat them separately.

WhatsApp rules you can’t skip

According to Meta’s developer documentation, Meta moved from per-conversation to per-message pricing on July 1, 2025. You pay for delivered template messages, priced by category and by the recipient’s country calling code. Meta doesn’t charge for messages customers send you.

The customer service window opens when a customer messages or calls you and lasts 24 hours. Inside it you can send any reply. Outside it you can only send templates, which Meta reviews automatically; review can take up to 24 hours, and a template with poor customer feedback or low read rates can be paused.

Two changes took effect on October 1, 2026, according to Meta’s pricing page. Service replies are now free only up to 1,000 per business phone number per month, and utility templates sent inside an open window are now charged. If you answer high volumes of WhatsApp support chats, recheck your budget.

Meta also requires opt-in before you message anyone. The opt-in must name your business and make clear that the person agrees to receive messages, and Meta recommends explaining how to opt out of each kind of message. Meta’s policy also requires you to respect opt-out requests.

US SMS rules you can’t skip

• 10DLC registration. Standard 10-digit local numbers need a registered brand (your company) and campaign (your use case and sample messages). Twilio’s documentation says anyone sending application texts to the US over a 10DLC number must register, and Twilio blocks US-bound messages from unregistered 10DLC numbers.
• Toll-free and short codes. Toll-free numbers go through their own verification. Short codes handle the highest volumes but take the longest to get.
• Consent. Under FCC rules, automated texts that advertise or telemarket need the recipient’s prior express written consent. Store when, where and how each person agreed.
• Opt-out. FCC rules in force since April 11, 2025 treat replies such as “stop”, “quit”, “end”, “revoke”, “opt out”, “cancel” and “unsubscribe” as revocation, to be honored within a reasonable time of no more than 10 business days. A single confirmation text with no marketing is allowed.
• Rules are moving. In an order adopted September 30, 2026, the FCC let senders designate an exclusive opt-out method, such as a reply keyword, if they disclose it clearly, and let a revocation apply only to the category of informational messages it answered. A reply to a marketing text still revokes consent to all marketing messages from that sender, and the 10-business-day deadline stays. The order was published in the Federal Register on October 26, 2026 and takes effect November 25, 2026.

This is general information, not legal advice. Ask counsel to review your consent language and opt-out flow before you send at scale.

Three ways to connect WhatsApp and SMS to Salesforce

Native: Salesforce Messaging in Service Cloud

According to Salesforce’s pricing page, Service Cloud messaging covers SMS, WhatsApp, Facebook Messenger, Apple Messages for Business, LINE and Bring Your Own Channel, plus web and in-app chat (Enhanced Chat). Agents work these conversations in the Service Console. According to Salesforce Help, each agent needs a messaging permission set license: Messaging User, or Messaging Unlimited if you have Contact Center Digital. Enhanced Chat uses its own Enhanced Chat User license.

Salesforce’s US pricing page lists Contact Center Digital (called Agentforce Contact Center Digital in Salesforce Help) at $75 per user per month, billed annually, as of October 2026. It covers web and in-app chat plus messaging over SMS, WhatsApp and the other channels. The page’s footnotes say 25 inbound SMS or WhatsApp conversations are included in the Digital Engagement SKU, and that SMS and WhatsApp usage is priced on separate rate cards. Outbound WhatsApp messages need an approved template, and a customer reply turns them into a conversation.

Current setups use enhanced channels. Salesforce set upgrade deadlines for the older standard channels (July 30, 2025 for WhatsApp, February 14, 2026 for SMS and Facebook Messenger), and Trailhead warns that standard channels might stop working after them. If you still run one, Trailhead’s upgrade module applies: standard bots can’t be used in enhanced channels, so you clone them as enhanced bots or replace them with an Agentforce agent; WhatsApp numbers need two-step verification turned off; and WhatsApp templates must be copied or recreated in the business account linked to the new channel.

Native: Marketing Cloud for campaigns

For promotional journeys, Marketing Cloud Engagement covers SMS and WhatsApp alongside email and push. Salesforce’s US pricing page now sells it as Pro+, Corporate+ and Enterprise+ editions, from $2,000 per org per month billed annually as of October 2026; confirm with Salesforce which edition includes the mobile messaging you need. In Marketing Cloud Next, Trailhead says SMS, WhatsApp and RCS are paid add-ons to the Growth and Advanced editions, which the pricing page lists at $1,500 and $3,250 per org per month, billed annually. Trailhead also walks through 10DLC brand, campaign and code requests in Setup, and consent settings with explicit or double opt-in per number.

Partner packages

Many messaging vendors publish Salesforce packages on AppExchange. Twilio offers Twilio for Salesforce, a managed package for one-to-one SMS from records, an SMS inbox, bulk messages to campaign members and automated texts; Twilio’s documentation still labels it a public beta. Other CPaaS and texting vendors list WhatsApp and SMS packages too, some aimed at service teams, others at sales texting or marketing.

Partners make sense when you are on Sales Cloud without Service Cloud, want one bill for SMS and WhatsApp, or need features such as shared inboxes for sales reps. Ask each vendor where messages are stored, how opt-outs sync, and what happens to your data if you leave.

Custom: WhatsApp Cloud API or an SMS API

A custom build calls Meta’s WhatsApp Cloud API directly, or goes through a provider such as Twilio. Twilio lists its WhatsApp fee at $0.005 per message, inbound or outbound, as of October 2026, and says it passes Meta’s template fees through without adding its own fees on top. Your service receives webhooks, matches the phone number to a record, writes the message through the Salesforce API and sends replies back.

How messages flow between WhatsApp, SMS and Salesforce

What maps where

Decide consent ownership before setup. If marketing and service both text the same customer, one opt-out store must feed both, or someone will text a person who already said STOP.

How to set up WhatsApp and SMS in Service Cloud, step by step

These steps follow the most common path: enhanced channels in Service Cloud Messaging. Exact screens change between releases, so keep Salesforce’s current setup guide open alongside.

1. Confirm licenses and scopeCheck that your org has Messaging and the add-on that covers SMS and WhatsApp, and how many Messaging User licenses you need. Write down the use cases: service replies, notifications, or both.
2. Work in a sandbox firstBuild routing, bots and Flows in a sandbox. Number registration is real-world, so plan which numbers you will use for testing and which for production.
3. Create the WhatsApp channelIn Messaging Settings, start a new WhatsApp channel and follow the Meta sign-up flow. According to Trailhead, you create or select the Meta business account, WhatsApp Business Account and profile inside this flow; an account created outside it can’t be used with the Salesforce channel. Verify the number by text or voice call.
4. Get the SMS number and registrationPick the number type for your use case. For a US 10-digit long code, the brand is registered first, then the campaign, then the number. Trailhead’s US and Canada SMS module (written for Marketing Cloud Next) says brands often clear in minutes to a few days and campaigns usually take 5–12 working days, so start this early.
5. Set consent, opt-in and opt-outConfigure the opt-in, opt-out and help keywords and replies for each channel. Choose explicit or double opt-in where the product offers it. Make sure STOP and the other standard words work in every language you support.
6. Set up routing and the consoleRoute each channel through Omni-Channel to the right queue, bot or agent. Add the conversation component to the Service Console and assign the Messaging User permission set license to agents.
7. Create templates and FlowsSubmit WhatsApp templates for review (up to 24 hours) and pick the right category, since it sets the price. Build Flows that send them on record changes, with a consent check before each send.
8. Test real scenariosA new number, a known Contact, a number on two records, a reply after 24 hours, a STOP reply, a message with an image, an agent transfer. Check that each conversation lands on the right record.
9. Pilot, then roll outStart with one team and one use case for a week or two. Compare message counts in Salesforce with the provider’s logs, fix gaps, then add teams and campaigns.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Common pitfalls and how to fix them

• Unregistered or wrong-use-case numbers. Texts from an unregistered 10DLC number get blocked, and texts outside the registered use case get filtered. Fix: register before launch, and re-register when you add a new kind of message, such as marketing on a service number.
• One opt-out list per tool. A customer says STOP to a marketing text, then gets one from a sales rep’s app. Fix: keep consent in Salesforce as the single source, sync every tool from it, and check consent in each Flow before sending.
• Sending free-form WhatsApp messages too late. Agents try to follow up two days later and the message fails. Fix: give agents approved utility templates for follow-ups and show the window status in the console.
• Wrong template category. A promotional message filed as utility can be rejected at review or reclassified as marketing, and marketing costs more. Fix: keep promotions in marketing templates and make utility templates about a specific transaction.
• Numbers that don’t match. “(415) 555-0132” and “+14155550132” are different strings to a search. Fix: normalize phone fields to E.164 before go-live and standardize new entries with a Flow or validation rule.
• Duplicate contacts from unknown senders. Every new number creates a Lead or Contact, including spam. Fix: create records only after the conversation qualifies, or let the agent link the sender to an existing record.
• Sensitive data in threads. Customers send card numbers, health details or ID photos. Fix: tell customers what not to send, mask or restrict sensitive fields, and set retention rules for messages and attachments.
• Budget surprises. Service replies above 1,000 a month per WhatsApp number and in-window utility templates are charged since October 1, 2026. Fix: forecast message volumes per category and review Meta’s rate card each quarter, since Meta can change rates on quarter-start dates.

Go-live checklist

Tick what is already true. The result shows how ready you are to switch on texting for customers.

When a custom integration makes sense

Native channels and packages cover most teams. A custom build earns its cost in a few cases:

• You send high volumes and want to choose and switch providers on price and delivery rates.
• Messages must be created from, or written to, other systems too: an order platform, a booking system or your website. The Salesforce website integration guide covers how forms pass leads and consent into Salesforce.
• You need logic no package offers, such as messages tied to custom objects or one consent store shared with a marketing platform.
• Data rules require messages to stay in a specific system or region.

A typical build has a webhook service for inbound messages and delivery receipts, a consent and window check before every send, record matching, and writes through the Salesforce API with a dedicated integration user. Salesforce gives supported editions a limited number of free Integration User licenses. Add retries and monitoring so an outage doesn’t lose messages. If you want messages inside the native console, Salesforce’s Bring Your Own Channel lets a custom connector feed Service Cloud Messaging.

A simple one-way connector, such as Flow-triggered notifications through an SMS API, usually falls in the $2,000–10,000 range, and a two-way sync with consent and routing in $10,000–40,000. Plan 15–25% of the build cost a year for maintenance. For the details, see the guides to API integration cost and data integration cost, and the Salesforce integration guide for how messaging fits with your other connections. If phone calls are part of the same project, see Salesforce CTI integration; for support teams on another help desk, see Zendesk and Salesforce integration.

FAQ

Where Gilzor fits

Gilzor builds and maintains Salesforce integrations from Poland and Cyprus. Gilzor’s engineers can map how messages and consent should flow between WhatsApp, your SMS provider and Salesforce, build a custom connector when a package isn’t enough, and support it after launch. See Gilzor’s Salesforce integration services.