WhatsApp Messaging
WhatsApp Messaging in Salesforce is the Service Cloud Messaging channel that lets agents communicate with customers through WhatsApp Business directly from the Service Console.
Definition
WhatsApp Messaging in Salesforce is the Service Cloud Messaging channel that lets agents communicate with customers through WhatsApp Business directly from the Service Console. Each conversation is stored as a Messaging Session record in Salesforce, with the full message history, media attachments, and conversation context tied to the customer Contact or Person Account record. Agents work the same WhatsApp conversations they would in any other messaging channel, with the same Omni-Channel routing, the same Macros, and the same Service Console layout.
WhatsApp is the most-used messaging app in much of the world (especially Europe, India, Brazil, and most of Latin America and Southeast Asia), and Salesforce WhatsApp Messaging integration is the supported way to serve customers who reach out through that channel. The integration uses WhatsApp official Business API, which enforces the messaging policies and templated outreach restrictions that the platform requires for legitimate business use.
How WhatsApp Messaging works inside Salesforce Service Cloud
How WhatsApp Messaging fits into Service Cloud
WhatsApp Messaging is one channel in the Service Cloud Messaging product, alongside SMS, Facebook Messenger, Apple Messages for Business, and the in-app messaging channel. Each channel uses the same underlying Messaging Session data model: a session represents a conversation, the session links to the customer Contact, and each message inside the session is a Messaging Component (or Messaging End User Object). The Service Console agent experience is consistent across channels: an agent assigned a WhatsApp conversation sees the same chat-style interface they would for SMS or in-app. Omni-Channel routes incoming WhatsApp messages based on skill, language, region, and the configured routing model. Macros let agents send templated responses, status changes, and field updates in a single click.
WhatsApp Business API and the messaging policies
Salesforce WhatsApp integration uses the WhatsApp Business Platform API (the Meta-managed business API). This is the only official, supported way to send business messages on WhatsApp. The API enforces strict messaging policies. Outbound messages outside the customer 24-hour window since their last inbound message require pre-approved Message Templates registered with Meta. Templates are non-marketing by default; marketing templates require additional approval. The platform also enforces a quality rating per phone number; low quality (high block rates) reduces the daily message limit and can lead to phone number suspension. The policies exist to prevent WhatsApp from becoming a spam channel; respect them or lose access.
Message Templates and the 24-hour window
WhatsApp Business has a critical concept called the 24-hour customer service window. When a customer sends a message to your business, you have 24 hours to respond with free-form text. Outside that window, you can only send pre-approved Message Templates. Templates are submitted to Meta for review and categorized as Marketing, Utility, or Authentication. Approval takes minutes to days depending on category and content. Templates support variables (the customer name, the order number, the appointment time) that get filled in at send time. Mature WhatsApp implementations build a small library of templates for common notifications (order confirmation, shipping update, appointment reminder, support ticket update) and use them outside the 24-hour window. Free-form text only inside the window.
Phone number provisioning and the verified business profile
Each WhatsApp Business deployment uses one or more phone numbers registered with Meta. Salesforce supports provisioning phone numbers through the Business Manager configuration. Each number has a Business Profile (business name, logo, description, website, contact info) that customers see when they initiate a chat. Verified Business profiles get a green checkmark; verification requires Meta-approved business documentation and brand-protection criteria. The phone number sees a quality rating based on customer feedback (block rate, report rate, response rate); high quality earns higher daily message limits, low quality earns restrictions. Mature WhatsApp implementations monitor the quality rating per number weekly and respond fast to any drop.
Rich media, interactive messages, and the WhatsApp feature set
WhatsApp Messaging supports more than text. Agents can send and receive images, videos, documents (PDF, DOCX), location pins, and contact cards. Interactive messages include quick reply buttons, list messages, call-to-action buttons, and product catalogs (for businesses with WhatsApp Catalog). The Salesforce integration renders these as rich Messaging Components inside the Service Console, so agents can compose interactive messages without leaving the Salesforce UI. Customers receive them as native WhatsApp interactive elements. Mature service teams use interactive messages to deflect routine queries: quick reply buttons for FAQs, list messages for menu-style triage, product catalogs for sales-led WhatsApp commerce. The interactive feature set is where WhatsApp Messaging differentiates from older SMS-based support.
Pricing, conversation categories, and the economic model
WhatsApp Business charges per conversation, not per message. A conversation is a 24-hour window starting from the first message in either direction. Each conversation is categorized as Marketing, Utility, Authentication, or Service, with different rates per region. Inbound service conversations initiated by the customer are typically free or low-cost. Outbound marketing conversations are the most expensive. The economic model rewards customer-initiated conversations over business-initiated ones, which aligns with WhatsApp anti-spam policies. Salesforce passes through the WhatsApp rates plus a platform fee. Budget for the conversation volume explicitly at deployment time; surprise WhatsApp bills are a common complaint from orgs that did not plan for the model. The pricing is publicly documented but easy to overlook during the initial integration scoping.
Setting up WhatsApp Messaging in Salesforce Service Cloud
Standing up WhatsApp Messaging in Salesforce is a coordinated activity between the Salesforce admin, the WhatsApp Business Manager admin, and the service operations team. The four-step routine covers: provision the phone number with Meta, configure the channel in Salesforce Setup, build the Message Template library, and roll out the channel to agents. Each step has dependencies on the previous one, and skipping any of them leaves a half-working integration. Plan four to six weeks for the full setup including template approvals and operational training.
- Provision the phone number with Meta
Through Meta Business Manager, register the phone number that will be used for WhatsApp Business. Submit business documentation for verification (recommended for trust marks). Configure the Business Profile: business name, logo, description, address, contact info. Wait for Meta approval, which can take hours to days depending on documentation. Once approved, the phone number is provisioned and ready to receive a webhook configuration. Document the approved number and the verification status; future template submissions reference both.
- Configure the WhatsApp channel in Salesforce Setup
Open Setup, search Messaging Channels. Click New Channel, pick WhatsApp Business as the channel type, and authenticate the connection with your Meta Business Manager credentials. Map the provisioned phone number to the channel. Configure routing: Omni-Channel queue, skills required, language detection. Configure default Messaging Templates that will fire on common triggers (auto-reply for after-hours, welcome message for new conversations). Save the channel and test by sending a WhatsApp message to the provisioned number; the inbound message should arrive in the Service Console for an assigned agent.
- Build the Message Template library
Identify the common outbound scenarios you need outside the 24-hour customer service window: order confirmation, shipping update, appointment reminder, password reset, support ticket update, billing notification. For each scenario, draft a template with variables for the dynamic data. Submit each template to Meta for approval through the WhatsApp Business Platform API or Business Manager UI. Categorize each as Marketing, Utility, or Authentication. Approval takes minutes to days. Once approved, the template is available in Salesforce to fire from Flow or Apex automation. Document each template purpose, variables, and approval status in the channel runbook.
- Roll out to agents and operationalize the channel
Train service agents on the WhatsApp channel: how it appears in the Service Console, how to use Macros for templated responses, when to use free-form text (inside 24-hour window) versus Message Templates (outside the window), how to handle media attachments. Roll out to a pilot group of agents for two weeks, capture feedback, and adjust the Console layout and Macro library. Expand to the full team after the pilot. Monitor the channel-level metrics (response time, conversation volume, quality rating) weekly during the first month. Adjust routing and template usage based on what the metrics show.
- The 24-hour customer service window is strict. Outside the window, only pre-approved Message Templates can be sent. Free-form outbound messages outside the window are blocked by the WhatsApp Business Platform.
- Message Template approval is per template and can take days. Plan the template library upfront, submit them in batches, and do not assume same-day approval for templates submitted close to launch.
- Quality Rating drops fast and recovers slow. One bad outreach campaign can suspend the phone number; recovery takes weeks of low-volume good-quality traffic. Treat the quality rating as a production-critical metric.
- WhatsApp Business charges per conversation, not per message. Budget for the conversation volume at deployment; outbound marketing conversations are the most expensive category and add up fast at scale.
- Phone numbers used for WhatsApp Business cannot be used for personal WhatsApp on the same device. Provisioning an existing personal-use number forces it off the personal app, which sometimes surprises business owners.
Trust & references
Straight from the source - Salesforce's reference material on WhatsApp Messaging.
- WhatsApp Messaging in SalesforceSalesforce Help
- Messaging Session OverviewSalesforce Help
- WhatsApp Business Platform Cloud APIMeta for Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is WhatsApp Messaging in Salesforce?
Q2. Where do conversations appear?
Q3. Why is WhatsApp important?
Discussion
Loading discussion…