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.