WhatsApp Business Calling in Salesforce

WhatsApp Business Calling lets verified businesses make and receive voice calls over the WhatsApp network using their official WhatsApp Business number. WorkDial is a Salesforce-native CTI platform that handles those calls as native Salesforce records: every WhatsApp voice call is a Voice Call record with routing, disposition, and reporting that match every other call in the CRM.

In much of EMEA, LATAM, and APAC, a customer’s first instinct is to tap the call button inside WhatsApp rather than dial a phone number. WhatsApp voice is a default business channel in those markets, not a fallback. The question for a Salesforce team is no longer whether to answer those calls. It is whether each one becomes data your CRM owns or a conversation that happens somewhere else.

What is WhatsApp Business Calling?

WhatsApp Business Calling is voice calling over the WhatsApp network through the WhatsApp Business API, placed and received on a verified WhatsApp Business number. Unlike a personal WhatsApp account, it supports multiple agents, verified business profiles, and call management through approved platforms. The customer experiences a familiar call inside WhatsApp; the business experiences a voice channel it can operate at scale.

For years that capability lived outside Salesforce. Calls happened on mobile devices or in a separate dashboard, disconnected from the records they related to. A rep might log “called via WhatsApp” as a manual Task, or log nothing. Manual logging leaves gaps in the activity record and costs rep time, and it means managers cannot answer a basic question: how many customer calls came through WhatsApp last week versus the phone?

Where does the WhatsApp call data live?

Call data lives in Salesforce as native objects. With WorkDial, a WhatsApp voice call writes a Voice Call record as it happens, with the channel marked as WhatsApp voice, direction, start and end time, duration, owner, and the related Lead, Contact, or Case. Dispositions and any AI artifacts (transcripts, sentiment, summaries) write to native Salesforce objects too, not synced in from a vendor database after the fact.

The telephony itself runs on your own Twilio account (bring your own account), billed at carrier cost with no markup. Twilio carries the WhatsApp voice transport and stores the audio recording, so the recording stays in infrastructure you control. The honest split is this: the call data lives natively in Salesforce, and the carrier transport and recording storage live in your own Twilio. That is the architectural difference, and it is the heart of the native versus integrated CTI question.

Other tools connect to Salesforce. WorkDial runs inside it. If the tool is supposed to manage your Salesforce communication, why does your communication data live somewhere else?

How does WhatsApp calling work inside Salesforce?

A WhatsApp voice call behaves like any other call on a native Salesforce CTI platform. Here is an inbound support call, end to end:

1. The customer taps call on your WhatsApp Business profile. The call arrives through Twilio, which carries WhatsApp voice.
2. The CTI adapter creates a Voice Call record immediately, with channel set to WhatsApp voice and status set to ringing, capturing the caller’s WhatsApp identity.
3. Salesforce looks up the caller against Contact, Lead, or Person Account and the most relevant open Case.
4. Omni-Channel routes the call using queue membership, skills, business hours, and agent presence. No external routing engine is involved.
5. The softphone opens as a Lightning component showing caller details, the related Case, and call controls (answer, hold, transfer) plus a place for disposition and notes.
6. On call end, the same Voice Call record is updated with duration, outcome, and the recording reference.

Outbound runs the same pattern in reverse. From a Lead, Contact, or Case the agent clicks to call over WhatsApp, the component creates an outbound Voice Call record linked to the current record, and Salesforce enforces business rules first. Consent checks (for example via ContactPointConsent) and quiet-hours guardrails run in Salesforce Flow before the call connects. At no point does the agent leave Salesforce to manage the call.

How is WhatsApp voice routed alongside phone calls?

WhatsApp voice enters the same Omni-Channel routing fabric as every other voice channel. Because the calls share one Voice Call object, you build queues such as “Tier 1 Support, voice (all channels)” and skills for product area, language, and region that apply across phone and WhatsApp alike. Salesforce makes one routing decision for all of it.

That avoids a failure mode common to split setups: one system routes phone calls, another routes WhatsApp calls, and agents sit idle in one queue while calls overflow in the other. The table below contrasts the two architectures, not any named product.

What workflows open up with native WhatsApp voice?

Once WhatsApp voice calls are native Voice Call records, the rest of your Salesforce automation applies without rework. A customer calls about an existing ticket and the matching Case opens automatically; after the call the agent updates the Case and the Voice Call from one screen. A dropped call triggers a Flow that creates a callback Task. Voice Call records carry language and region, so Omni-Channel routing sends future calls from the same customer to a matching agent, and reporting shows where WhatsApp demand comes from without a separate BI tool.

The AI side follows the same rule. Transcripts, sentiment, and summaries land on native objects, so AI call analysis in Salesforce covers WhatsApp voice and phone calls together rather than treating WhatsApp as a channel your analytics cannot see. For the full picture of placing and receiving WhatsApp voice from records, see WhatsApp calling in Salesforce, the product surface this post sits beneath.

Compliance and audit with WhatsApp voice

Voice carries sensitive information, so where the evidence lives matters. With WorkDial, recordings and metadata are referenced from the Voice Call record, access is governed by permission sets and field-level security like any other object, and retention rules can be set by region or business unit. Consent checks can run before a call connects: a Flow reads ContactPointConsent, and if consent is missing or revoked the call is blocked or redirected while the attempt is still logged for audit. Legal and security teams care less about which network carried the audio and more about where the record lives. Here that answer is Salesforce, with the audio in your own Twilio.

Messaging alongside voice

WorkDial covers WhatsApp voice. Text on WhatsApp is a separate job handled by ValueText, the Salesforce-native messaging platform from the same team, which covers WhatsApp and SMS messaging inside Salesforce. WorkDial is buyable on its own for voice; you do not need ValueText to make WhatsApp calls from Salesforce. Run together, WorkDial and ValueText form the complete Salesforce-native communication stack, voice plus messaging, at a 20% bundle discount. Pricing for both, including the free Professional trial, is on the pricing page.

Treat this as your reference design

If you accept that Salesforce should own the call data and that a WhatsApp voice call should be a native Voice Call record, the only open question is which tool matches that pattern. WorkDial was built to it: a Lightning softphone on Open CTI and the Salesforce Voice APIs, Twilio for carrier and WhatsApp transport on your own account, Omni-Channel for routing, and every record native in your org.

See it run on a real org in a WorkDial demo. If you would rather try it yourself first, start a free trial.

Written by Nikhil Palliboina, Content Writer, WorkDial. WorkDial is built by the team behind ValueText, the Salesforce-native messaging platform, rated 4.97 stars across 100+ AppExchange reviews.