How to integrate WhatsApp with Salesforce Service Cloud for omnichannel support

Having WhatsApp, email, phone, chat and social media does not make a company omnichannel.

Omnichannel support starts when a person can switch channels without explaining, all over again, who they are, what they bought, what they already asked or what problem is still open. The goal is continuity for the customer and context for whoever is helping them, not piling every message onto a single screen.

Salesforce Service Cloud, which Salesforce now presents as Agentforce Service, can be the foundation for centralizing conversations, cases and teams. The technology on its own does not decide how to recognize a customer, who should handle them, what data the agent needs to see, or what service level the operation can sustain. That comes down to the design decisions you make before connecting the first channel.

The difference between multichannel and omnichannel

A multichannel operation offers several ways to get in touch: WhatsApp, phone, email, web form, chat or social. Each channel tends to keep its own conversations, rules, teams and data.

Someone might open an inquiry on WhatsApp, send details by email and then call to complain. If each interaction lands with a different person and no shared history, the company has several channels and the customer still gets a fragmented experience.

Omnichannel wraps those channels around the customer. The agent does not need to see "everything", they need the context that resolves the case in front of them.

A fast reply does not fix a broken experience. If the customer repeats their case, gets bounced between people or has to write again the next day, what is failing is the context and the operational design.

1. How to recognize the same customer

The first challenge is knowing it is the same person when they message on WhatsApp, call, fill in a form, or email from a different address.

Salesforce can organize your customer records and messaging conversations. When your sources are fragmented, you may also need identity-resolution capabilities in Data 360 (formerly Data Cloud), which links identities and source records instead of forcing them into a single master record. The point is practical: give the agent the right context at the moment they have to decide something.

2. How to run WhatsApp as a support channel

WhatsApp comes with a different expectation of immediacy than email or a form. Treat it as one more inbox or as a broadcast channel with no rules and the experience degrades fast.

To run WhatsApp alongside Salesforce Service Cloud, you need to decide how you will manage the official channel (Enhanced WhatsApp, connected to a WhatsApp Business account from Meta with a verified number), customer consent, the templates for business-initiated messages, the service window, and your team's capacity to reply in time.

One thing worth spelling out: having Service Cloud does not mean WhatsApp is included or set up. Whether the channel is available depends on your licenses, your messaging capabilities (for example, Digital Engagement) and the plan you contract.

Meta charges per delivered message based on the category and the recipient's country. When the customer starts the conversation, a 24-hour service window opens: within it, free service messages and utility templates sent in reply may carry no Meta charge, while marketing and authentication messages are still billable. Outside that window, you have to use approved templates to reopen or start a conversation. On top of that, Salesforce licenses, capabilities and messaging credits (Message Credits) may apply, depending on the solution you contract.

3. How to route each conversation

An order question, a high-value quote, a complaint, a technical support request and a routine FAQ should not travel the same path. Routing should weigh the reason for contact, the priority, the type and value of the customer, the skill required, the language or business unit, the team's availability, and your service hours and fallback rules.

Salesforce Enhanced Omni-Channel sends messaging sessions to agents or queues by capacity, priority, skills and the rules you define. Bots, flows and other automations can take part before a handoff or during the conversation. The platform makes routing possible; your organization decides which priorities are right and what SLA it can actually meet.

4. Where to automate, and when a person should step in

Bots and AI can take on repetitive work: answering FAQs, checking an order status, collecting initial details, classifying a request or guiding a simple action.

Their value is in reliably handling what is predictable and handing over the right context when a person has to step in. Keeping the customer away from an agent is not the point.

Before you automate, decide which inquiries are genuinely repetitive and low-complexity, what the bot can look up or ask for, which situations need a human, when a conversation should be transferred, what context the agent inherits, and how you will confirm the automation actually solved the problem.

Agentforce and other AI capabilities can power this model always on a foundation of well-defined processes, data, permissions and escalation rules.

5. Which systems the agent needs to reach

A conversation rarely holds everything needed to close a case. The agent may need to see orders, payments, shipping, inventory, warranties, contracts, purchase history or the status of a request.

That data usually lives across Service Cloud, Sales Cloud, ecommerce, ERP, OMS, logistics, payment platforms and other apps. Connecting it is what decides whether a person can resolve the contact or has to jump between tools, ask for more details and hand the case off. It is core to the project, not a later add-on.

The goal is narrow: surface the data that lets the agent make the next right decision, in the conversation.

6. How you will measure the result

An omnichannel project should not get a pass just because first response time dropped or the number of conversations went up. What also matters is whether the person actually solved their problem, whether they had to come back, whether they were transferred, whether the automation genuinely helped, and how much it cost to resolve or convert the conversation.

First response time is useful, but on its own it can mislead: replying in seconds is worth nothing if the customer has to explain everything again, or comes back the next day because no one fixed the issue.

What to sort out before you implement

Before you start an implementation or add WhatsApp support, it is worth answering:

-How many contacts arrive today per channel, and at what times?

-What identifiers let you recognize the same customer, account, order or case?

-What information has to be on hand to resolve the priority contacts?

-Which inquiries can an automation resolve, and which need a person?

-What priorities, skills and hours should drive routing?

-How will WhatsApp consent be captured and managed?

-Which conversations are service, which are transactional, and which are commercial?

-What is the most your operation can sustain each month across messaging, technology and team?

-Which metrics will decide whether the project continues, gets adjusted or scales?

If these questions do not have answers yet, the first move is not to switch a channel on it is to design the operation that will hold it up. A partner that opens with "we'll connect the channels," without a word about identity, consent, cost or metrics, is selling you multichannel. In GoCode's Salesforce implementation service in Chile we start from these decisions the financial ones included before connecting the first channel.

Connecting channels is a technical step. Designing an operation that can actually resolve is what determines the return on the investment. When several of these decisions go wrong, the project usually ends in a later recovery more expensive than getting the design right the first time.\