The right choice when
- Your customers are in markets where WhatsApp is the main channel.
- Service updates by email go unread.
- You need rules Salesforce's own messaging set-up does not give you, or it is not on your edition.
Integration · Salesforce + WhatsApp
Salesforce messages on WhatsApp. Written back to the record.
Appointment reminders, case updates and renewal notices sent on WhatsApp from Salesforce, with each message and reply saved against the contact, so the record stays complete.
- Salesforce
A case changes, a renewal nears or an appointment is booked.
- Connector
Sends the approved template and logs it as an activity.
- WhatsApp
The customer gets the message; the reply returns to Salesforce.
The connected app has only the access it needs.
01 / Is this the one
Is this the connection you need?
It suits a Salesforce team whose customers prefer WhatsApp.
Look elsewhere when
- Salesforce's own WhatsApp channel is on your edition and does what you need.
- You want bulk marketing messages. WhatsApp limits and charges for those.
- Your Salesforce edition has no API access.
02 / What the work covers
What the work covers.
One or two message types to start, logged as activities.
- 01
Triggers and wording
Which records and changes send which template.
- 02
Salesforce access
A connected app with scoped OAuth access, built on your sandbox first.
- 03
WhatsApp number and templates
The business number and the templates Meta must approve.
- 04
Logging and handover
Messages and replies saved as activities. Code, accounts and documentation handed over.
03 / Limits and risks
Where it can go wrong.
WhatsApp sets the rules for messages you start
A message the business sends first must use a template Meta has approved, and Meta charges for most of them. Replies within 24 hours of the customer's last message are free-form.
Salesforce's plan decides what is possible
API access, call limits and some data depend on the Salesforce plan you are on. We check yours before quoting, so the limit is found on the first call and not after launch.
Sandbox first
Changes are built and tested in a Salesforce sandbox before production, which needs your admin's time.
04 / What we can show
The same idea, as our own product.
ZeroDelay.si connects business software to WhatsApp, Telegram and the web, so a team asks and gets answers, and staff send updates that wait for approval. Its Salesforce connection is built and tested by our team. FocusPulse, our market-news product, already delivers its briefings on Telegram.
What this does not show
A client project. ZeroDelay.si is in early access, and we have no published client case study of this integration.
05 / What to do next
Price it or talk it through.
The first step is a free scoping call about your Salesforce set-up and the messages you need. A written estimate follows.
01
Estimate the cost
02A price range for your build in four steps.
Chatbots and bots
03Answers in a conversation, on your channels.
Google Calendar to WhatsApp
04Appointment reminders that cut no-shows.
Tally to WhatsApp
05Sales, dues and stock from Tally, on WhatsApp.
All integrations
Every connection we build.
A little clarity
Before connecting Salesforce to WhatsApp.
Can we see it working?
Yes. This connection is built and tested by our team, and we can demo it for you on a free call before you decide anything.
Which Salesforce editions does this work with?
Editions that include API access, which are Enterprise and above, or Professional with API access added. We check yours first.
Do you work with our Salesforce admin?
Yes. Your admin keeps control of the org; we build in a sandbox and hand the change over for them to deploy.
Is there not an app for this already?
Sometimes there is, and if a vendor's own app or a no-code tool does what you need, use it: it is cheaper. A built connection earns its place when the rules are yours, such as which records go, who sees what, what happens when the two systems disagree, or when the volume makes per-task pricing expensive.
What does it cost?
It depends on how many message types and objects are involved. First releases at NSDBytes start from $5,000. The project cost estimator gives a range, and a fixed quote follows a free scoping call. Charges from the services themselves, such as WhatsApp messages, API plans and hosting, are billed by those providers and are separate.
Who owns the connection once it is built?
You do. The code, the server it runs on and the accounts with each provider are yours once the final invoice is paid. We can run and maintain it afterwards if you want, but you are never locked in.
Start wherever you are
Bring the messages your customers miss.
We'll show you what can move to WhatsApp and how it stays on the record.
Want certainty before you commit? Start with a scoping project, $500