What This Integration Does
This integration connects your WhatsApp Business account to Salesforce, logging every WhatsApp conversation against the correct contact, lead, or case record. Inbound messages from customers appear on the Salesforce timeline within seconds. Outbound template messages such as appointment confirmations, case updates, and payment reminders are triggered by Salesforce automation and delivered through WhatsApp with full delivery tracking. It is one of the communication and CRM integrations we build directly against the Salesforce API.
For businesses that use WhatsApp as a customer support channel, the integration creates a direct link between WhatsApp conversations and Salesforce cases. A customer sends a WhatsApp message about an issue, and the integration either attaches it to an existing open case or creates a new one. The support agent sees the full thread in Salesforce, responds from within the platform, and the reply is delivered via WhatsApp. The customer stays on WhatsApp. The agent stays in Salesforce, and the case record captures everything.
This is not Salesforce Digital Engagement, which requires Service Cloud licensing and locks you into Salesforce’s own messaging infrastructure. This is a custom integration that works with your existing WhatsApp Business API setup and any Salesforce edition, giving you flexibility over routing rules, template management, and conversation handling that the native product does not offer.
The Workflow
Inbound WhatsApp messages arrive via the WhatsApp Business API webhook. The integration receives the message, extracts the sender’s phone number, and searches Salesforce for a matching contact or lead. If a match is found, the message is logged as a custom activity on that record. If the message relates to an open case, determined by conversation context or an active thread, it is attached to the case as a case comment or feed item. If no match is found, the integration creates a new lead with the phone number and logs the message against it.
Outbound messages follow two paths. Automated templates are triggered by Salesforce Flow or Apex when a case status changes, an appointment approaches, or a payment is due. Manual replies are sent through a custom Lightning component on the case or contact page.
The 24-hour service window is enforced automatically, so agents are restricted to template messages once the window has closed. Delivery status updates (sent, delivered, read, failed) are written back to the Salesforce activity record with failure reasons for corrective action.
Before and After
Before: Customer WhatsApp messages arrive in a shared WhatsApp Business inbox that is disconnected from Salesforce. Support agents switch between WhatsApp and Salesforce to manage conversations, manually copying key details into case notes. When a customer references a previous WhatsApp conversation, the agent has to search the WhatsApp app to find it. Automated notifications such as case updates and appointment reminders are sent via email or a separate SMS tool because WhatsApp is not connected to the CRM workflow engine.
After: WhatsApp messages appear on the Salesforce contact and case timeline alongside emails, calls, and notes. Agents respond to WhatsApp messages from within Salesforce. Automated template messages are triggered by the same workflow rules that govern email notifications. The 24-hour session window is enforced automatically. Every WhatsApp interaction is searchable, reportable, and visible to anyone with access to the record.
Who Needs This
This integration is designed for organisations running Salesforce that use WhatsApp as a customer communication channel. It fits well when:
- Your support team handles customer issues through WhatsApp and needs those conversations linked to Salesforce cases rather than managed in a separate inbox
- Your sales team communicates with prospects on WhatsApp in markets where it is the preferred messaging platform, and needs that conversation history in the CRM
- Your operations team sends status updates, confirmations, or reminders that should be delivered via WhatsApp and triggered by Salesforce workflow rules
- Your compliance requirements mandate that all customer communications, including messaging apps, are logged centrally and auditable
Businesses operating in regions where WhatsApp is the dominant communication channel (Latin America, Southeast Asia, parts of Europe and Africa) benefit most, as WhatsApp often carries more customer interaction volume than email.
How We Build This
We start by mapping your WhatsApp communication patterns to Salesforce objects. Which Salesforce objects should WhatsApp messages be logged against? Inbound messages might route to a specific queue, follow a case assignment rule, or go directly to the record owner, and we work out which automated processes should trigger WhatsApp template messages.
The WhatsApp Business API setup is configured first, either connecting to your existing BSP or setting up API access if you are migrating from the standard app. Template messages are drafted, submitted for WhatsApp approval, and mapped to Salesforce automation triggers.
On the Salesforce side, we create custom activity types for WhatsApp messages, build Lightning components for manual messaging, and configure automation triggers. Phone number matching uses fuzzy logic to account for format variations such as country codes, leading zeros, and spaces.
Testing covers the full conversation lifecycle: inbound routing, case creation, agent reply, template delivery, session enforcement, and media handling. We test in a Salesforce sandbox with WhatsApp test numbers before connecting production.
Bring WhatsApp Conversations Into Salesforce
If your team juggles between WhatsApp and Salesforce to manage customer relationships, this integration puts the full conversation in one place. The same approach applies to other stacks, whether that is the WhatsApp and HubSpot integration or linking Salesforce to other tools through our Salesforce and Slack integration. Get in touch to discuss connecting WhatsApp to your Salesforce environment.
Written by
Alex
CEO
I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.