WACrew

Guide

How to integrate WhatsApp with Salesforce, the heavy and the light way

Two ways to integrate WhatsApp with Salesforce. The official channel uses the WhatsApp Business Platform; the light way keeps chats on your own number and has an AI agent log context in Salesforce through its hosted MCP servers or the API.

Updated 2 min read
On this page
  1. The heavy way: WhatsApp as a Salesforce channel
  2. The light way: an agent between your number and the CRM
  3. What to ask the agent
  4. Limits
  5. Questions

There are two very different ways to integrate WhatsApp with Salesforce, and picking the wrong one costs months. The heavy way puts WhatsApp inside Salesforce as a service channel. The light way keeps WhatsApp where it is and teaches the CRM what was said.

Checked on November 16, 2026.

The heavy way: WhatsApp as a Salesforce channel

Salesforce offers WhatsApp as a messaging channel on the WhatsApp Business Platform. You get routing, agents answering inside Salesforce and reporting, with a Business account approved through Meta and Meta's message rates on top of Salesforce licensing. It fits contact centers with many agents and strict process.

The light way: an agent between your number and the CRM

For a small team, a consultancy or an account manager who already serves clients on their own number:

  • WACrew links to that number, keeps the history on your server with voice notes transcribed, and exposes it through an MCP server and an API v1.
  • Salesforce Hosted MCP Servers (developer guide) let an MCP client work with Salesforce data through OAuth. Salesforce states they are meant for customers with Flex Credits and that usage may be billed; check availability for your org edition.
  • Without the hosted MCP, the agent can use the Salesforce REST API, or n8n can write with its Salesforce node.

What to ask the agent

Read the Acme group from the last two weeks, voice notes included. In Salesforce, add a
note to the Acme account with decisions and open requests, and list the opportunities
that changed so I can update them.

Limits

  • No real-time mirror: the agent acts when asked (or when the WACrew plantao skill wakes it on a new message).
  • Writes follow the permissions of the Salesforce user behind the OAuth login. Use a user with the smallest set that works.
  • Compliance teams that need every WhatsApp message stored in Salesforce should go the heavy way. The light way stores summaries.

Questions

Does the light way need the WhatsApp Business API? No. WACrew links to your existing number as a device.

Can Salesforce users reply to WhatsApp from Salesforce? Not in the light way. Replies go out from the WACrew panel or from the agent, after approval.

Is this suitable for a large support team? Usually not. Many agents on one number with SLAs and routing is what the official channel is built for.

Where is the data? The chat history stays on your WACrew server; Salesforce gets what the agent writes; the model sees what it reads during the session.