Salesforce Marketing Cloud + Zapify: Cheaper WhatsApp, with AI and Omnichannel Support

The Salesforce Marketing Cloud + Zapify integration lets you trigger WhatsApp from Journey Builder through Zapify, cutting the cost of delivery and keeping the conversation going with AI and human support.

Journey Builder keeps orchestrating the journey — deciding who enters, when, and why. Zapify delivers the WhatsApp message at a lower cost and keeps the conversation going afterwards, with AI and human agents. In short: Salesforce orchestrates. Zapify delivers cheaper — and does more after delivery.

Why pay 6.6x more to deliver the same message?

The same WhatsApp marketing message, triggered from Journey Builder, costs 0.6531 USD (about 0.5597 EUR) through Salesforce Message Credits — or 0.0846 EUR through Zapify’s Custom Activity. 6.6 times more, to deliver exactly the same message, at list price on both sides.

Salesforce publishes the official Message Credits rate card for WhatsApp (effective from 1 May 2026): a WhatsApp marketing message to the United Kingdom costs 65.31 credits, and credits start at 10 USD per 1,000 — 65.31 × (10 USD / 1,000) = 0.6531 USD per message. Converted at the European Central Bank’s EUR/USD reference rate (1.1669, on 26/08/2026), that’s 0.5597 EUR.

At Zapify, the cost of Campaigns & API sends (the rate applied to the Salesforce integration’s triggers) starts at 0.032 EUR. On top of that comes Meta’s own cost for the marketing template — published in Meta’s rate card for the WhatsApp Business Platform, which for the United Kingdom is 0.0526 EUR. In total: 0.032 + 0.0526 = 0.0846 EUR per message, Meta’s cost already included. Just as with Salesforce, there’s room for volume negotiation on both sides — but at list price, Zapify saves roughly 85% per message.

And it’s not just cheaper delivery: the same price includes the omnichannel inbox, the AI assistant, human agents and per-contact history — alongside Instagram, Facebook Messenger, webchat, voice and RCS.

What Zapify adds after delivery

Once the message goes out, this is where Zapify adds the rest: the customer’s reply lands in a real omnichannel inbox — queue, agent assignment, full history — alongside the company’s WhatsApp, Instagram and Facebook Messenger, webchat and RCS conversations. The same AI assistant that handles those channels replies, clarifies, or hands off to a human agent with the full history — the same Human-in-the-Loop logic that already exists on any Zapify channel.

Journey Builder still decides who enters the journey and why — that doesn’t change. What changes is what happens next: instead of the conversation ending at the delivery report, it keeps going, with AI and people, for as long as it lasts, whichever channel the customer chooses to reply on.

The “WhatsApp via Zapify” Custom Activity

Zapify makes this integration available through the “Salesforce Marketing Cloud” app in its App catalogue: once configured, Zapify generates the credentials and URLs you need to register a Custom Activity — “WhatsApp via Zapify” — directly in your Journey Builder. Once registered on the Salesforce side, the activity becomes available to drag into any journey, alongside Email, SMS or Push: map the Data Extension fields to the approved template’s variables, and every contact reaching that step gets the message through the company’s own WhatsApp Business Platform — not through Salesforce Message Credits.

Note: today the Custom Activity already triggers both WhatsApp and RCS.

Each send is also aggregated as a campaign in Zapify, with the same delivery, read and reply reporting that already exists for any WhatsApp campaign.

Connecting Journey Builder to Zapify

1. In Marketing Cloud: create an “Installed Package” of type API Integration – Server-to-Server (Setup → Apps → Installed Packages) and get the subdomain, client ID and client secret.
2. In Zapify: install the “Salesforce Marketing Cloud” app from the App catalogue, paste those three credentials and test the connection.
3. Zapify returns an account-specific Base URL and a token — paste it into the Custom Activity configuration on the Salesforce side.
4. Back in Journey Builder: drag “WhatsApp via Zapify” into the journey, pick the approved template and map the fields.

No custom code, no separate integration file.

Where this fits into a journey you’ve already built

Five common scenarios where Journey Builder already triggers — and Zapify delivers cheaper and keeps the conversation going:

• Abandoned cart — the reminder arrives on WhatsApp at a lower cost, and a question about size or delivery time gets resolved on the spot by AI, without leaving the conversation.
• Lead recovery — the journey qualifies and segments; Zapify re-engages over WhatsApp and a human agent takes over the moment the lead shows real buying intent.
• Customer reactivation — the reactivation campaign goes out cheaper, and a positive reply turns into a booking or a sale without switching channels.
• Events — the invite and the reminder go out through the journey; last-minute confirmations and questions stay in the same WhatsApp conversation.
• Post-sale — the journey triggers the follow-up; a support request gets resolved by AI or escalated to an agent, without opening a separate ticket.

Does this replace Salesforce Marketing Cloud?

No, and that’s not the point. Journey Builder remains the decision engine — segmentation, data, journey logic, everything already built around Marketing Cloud still holds. What Zapify replaces is just the last stretch: instead of spending Message Credits just to deliver the message, that delivery now comes with an inbox, AI and per-contact history built in — without switching Journey Builder, without switching strategy.

Frequently asked questions

Do I need to write any code to connect Journey Builder to Zapify? No. Just install the “Salesforce Marketing Cloud” app from Zapify’s App catalogue, exchange credentials once with Marketing Cloud, and the “WhatsApp via Zapify” Custom Activity becomes available to drag into any journey.

Does the Custom Activity replace Salesforce Message Credits? It replaces them for the WhatsApp channel: the message is delivered through the company’s own WhatsApp Business Platform, connected to Zapify, and billed at Zapify’s per-message price (Zapify’s fee + Meta’s template cost) — not through Salesforce’s Message Credits.

Do customer replies come back to Marketing Cloud? No. Journey Builder sends the message; from there, the conversation lives in Zapify’s omnichannel inbox — with AI, per-contact history and escalation to human agents — and doesn’t return to Marketing Cloud.

Does the Custom Activity already trigger channels other than WhatsApp? Yes — today it already triggers both WhatsApp and RCS. Instagram and Facebook Messenger don’t belong in this comparison: they’re reply channels, not trigger channels — that’s not a Zapify limitation, it’s platform policy.

Do I need to switch marketing platforms to use this? No. Marketing Cloud still decides who enters a journey and why; Zapify only steps in for the conversation part — delivery and reply — that Marketing Cloud was never designed to manage.

Already using Salesforce Marketing Cloud? Compare what you’re paying per message. Talk to our team and book a demo to see the “WhatsApp via Zapify” Custom Activity running on your account.