Integrations

WhatsApp Salesforce integration: every conversation logged in your CRM

Vinícius Molina

October 2, 2026

6 min

Sailer AI's WhatsApp Salesforce integration connects your company number and each rep's own number to Meta's official API and logs every message and reply in Salesforce, using the book of accounts from Salesforce itself. AI agents and reps look up accounts and opportunities and create activities without leaving WhatsApp.

If your sales operation already runs on Salesforce, the question isn't which CRM to use. It's how to get what happens on WhatsApp into Salesforce without relying on reps to remember to log it. This article shows how Sailer AI does that, what syncs, how it worked at Arco Educação, and when Salesforce's own native channel is the better choice.

How to integrate WhatsApp with Salesforce and log conversations automatically

There are three ways to connect WhatsApp to Salesforce:

Salesforce's native channel. WhatsApp is set up as a Messaging channel in Agentforce Service (formerly Service Cloud), with Omni-Channel routing. It is designed for service teams working in the service console.
AppExchange apps. Third-party connectors that bring messages into Salesforce records, with varying scope and depth.
A sales layer on top of Salesforce. This is what Sailer does: it runs sales conversations on WhatsApp, with AI agents and reps, and writes the results into Salesforce.

With Sailer, automatic logging works like this:

Your company number and each rep's number connect to the official WhatsApp API. With coexistence, reps keep using the same number in the app.
Sailer reads the contact, account, opportunity and account owner from Salesforce.
Every message sent and every reply received is logged in Salesforce. The summary becomes a note, the agreed fields are filled in and next steps become activities.
Salesforce can also trigger Sailer: a CRM event fires a WhatsApp send through a documented inbound endpoint, with authentication and duplicate protection.

What syncs between WhatsApp and Salesforce

Data	Direction	How it's used
Contact, account and opportunity	Salesforce → Sailer	Context for the AI agent or rep before replying
Book of accounts (account owner)	Salesforce → Sailer	Decides which number each message goes out from and who receives the conversation
Campaign segmentation	Salesforce → Sailer	The list is built in Salesforce; each message goes out from the owning rep's number
Outreach and reply	Sailer → Salesforce	Who was contacted, when, and whether they replied
Fields and notes	Sailer → Salesforce	Data collected in the chat and a summary for whoever picks up the customer next
Activities	Sailer → Salesforce	Visits, meetings and next steps agreed on WhatsApp
Opportunity stage	Sailer → Salesforce	Updated as the conversation progresses, under rules you define
Event-triggered sends	Salesforce → Sailer	A CRM event triggers a template or campaign

Which objects and fields go into each row is agreed per project. An AI agent only edits what it has been allowed to edit.

In practice: Arco Educação

Arco Educação serves around 12,000 schools in Brazil and runs its sales operation on Salesforce. Sailer was deployed on three fronts, all tied to the same CRM.

Consultants on their own numbers (Sailer Fleet). Before, each message to schools took about 3 minutes, copying and pasting school by school, with no record of who replied. With Sailer, each consultant's book of accounts comes from Salesforce, campaigns are segmented in Salesforce, and each message goes out from the owning consultant's number. Salesforce logs the outreach and the reply. Results, according to Arco:

a pilot with 11 consultants, growing to 125 of 135 in two months;
16,500 messages sent from consultants' own numbers, reaching more than 8,000 schools;
a 26% reply rate, a number that was not measured before;
825 hours saved, roughly R$43,000 in two months.

Bettania, Bett Brasil's copilot. For the 600 salespeople at Bett Brasil, Sailer built an AI copilot on WhatsApp. A rep would ask for a briefing on a school coming to the booth, and she pulled the information from Salesforce and put the summary together. After the meeting, the rep asked her to create the follow-up visit, and she logged the activity in Salesforce.

AI SDR. For outbound prospecting to schools, Arco also used a Sailer AI SDR and reached +1,100% schools worked per SDR per month. Details are in the Arco Educação case.

What implementation looks like

Object and field map. With your Salesforce admin, we define what Sailer reads, what it writes and which field defines each account's owner.
Salesforce connection. The admin authorizes Sailer's access with the agreed permissions and, if you want event-triggered sends, configures the call to Sailer's endpoint.
Numbers on official WhatsApp. The brand's number and reps' numbers through coexistence, with each rep's book of accounts synced. See Sailer Fleet.
Playbook, agents and templates. Handoff rules between AI and people, Meta-approved templates and campaign eligibility filters.
Sandbox. About two weeks of simulation, checking what lands in Salesforce before any real customer.
Go-live. A typical implementation takes about five weeks from kickoff.

Sailer or Salesforce's native WhatsApp channel?

According to Salesforce's documentation, checked in October 2026, WhatsApp is configured as a Messaging channel in Agentforce Service, with templates, Omni-Channel routing and the option to connect an Agentforce agent to the channel. Activation requires Messaging licenses. Marketing Cloud also supports WhatsApp for marketing journeys.

If what you need is...	Best fit
Customer service in the Salesforce console, with a central number and Messaging licenses already in place	Salesforce native channel
Everything from a single vendor, including the AI agent	Native channel with Agentforce
Selling from each rep's own number, with Salesforce account ownership and governance	Sailer on top of Salesforce
Campaigns segmented in Salesforce, sent from the number of whoever owns the account	Sailer on top of Salesforce
AI agents trained on your sales playbook, with handoff to the rep	Sailer on top of Salesforce
Scoring 100% of conversations, human and AI, against the playbook	Sailer (Compass)

The two can run side by side on different numbers. A given WhatsApp number can only be connected to one integration at a time, so decide which platform handles each number.

Frequently asked questions

How do I log WhatsApp conversations in Salesforce automatically?

Connect your numbers to the official WhatsApp API through a platform integrated with Salesforce. With Sailer, every message and reply is logged in Salesforce, the summary becomes a note, the agreed fields are filled in and next steps become activities. Reps don't type anything after the conversation.

Do I need to replace Salesforce to use Sailer?

No. Salesforce stays the source of truth: accounts, opportunities, account ownership, reports and automations stay where they are. Sailer reads the context it needs, runs the WhatsApp conversations and writes the results back. At Arco Educação, campaigns are segmented in Salesforce itself and the record flows back to it.

Does it work with each rep's own WhatsApp number?

Yes. Through coexistence between the WhatsApp Business app and the official API, each rep keeps their own number and chats. Each rep's book of accounts comes from Salesforce, and campaigns go out from the owner's number to their own customers. At Arco, 125 of 135 consultants were onboarded in two months.

Does Sailer replace Agentforce or Salesforce's WhatsApp channel?

Not necessarily. The native channel serves service operations in the Salesforce console well. Sailer is built for sales: reps' numbers under governance, AI agents trained on your sales playbook and analysis of every conversation. Since a number can only be connected to one integration at a time, each number needs one owner.

How long does a WhatsApp Salesforce integration take?

A typical implementation takes about five weeks from kickoff to go-live, with about two weeks of sandbox simulation. What speeds it up most is involving a Salesforce admin early, a map of the objects and fields Sailer may read and write, and the field that defines who owns each account.