The Conversation Is Happening Outside Your CRM.
Your customers already have a favourite way to talk to you, and it is not email. It is WhatsApp, the app they open dozens of times a day and read within minutes. Yet in most companies the customer record lives in Salesforce while the conversation lives on somebody’s phone. Reps switch screens, copy numbers and paste screenshots into notes. The moment a chat ends, its context disappears from the CRM, and the next person who picks up that customer starts from zero.
WhatsForce Puts The Conversation Inside Salesforce.
WhatsForce is two-way WhatsApp messaging built natively for Salesforce. It connects Contacts to the Meta WhatsApp Cloud API, so every message sent and received lives right next to the customer data it belongs to. Agents get a full chat inbox in the App Launcher, with recent conversations, Contact search and a familiar chat window. They also get a WhatsApp tab on every Contact record, beside Related and Details. Both screens share one engine, so a conversation shows up everywhere it should.
Everything A Real Conversation Needs.
Agents send free-form text whenever the customer has written in the last 24 hours, and approved templates at any time to start or restart a chat. Photos, videos, audio and documents travel both ways, and incoming files land automatically in the Contact’s Files. Ticks show exactly where each message stands: one grey for sent, two for delivered and two blue for read. When something fails, a warning icon explains why. Nobody has to leave Salesforce to know what happened.
How A Message Travels In Seconds.
When a customer writes, Meta sends a webhook to a secure Salesforce Site. An Apex REST service validates the request, matches the sender to a Contact by phone number, saves the message and downloads any media in the background. Replies take the reverse path. The React interface calls an Apex API, which sends the message through the Cloud API and records the result. Delivery and read updates flow back the same way, and an open chat refreshes every couple of seconds.
Security Is Built In From The Start.
The webhook checks a verify token during setup and validates the signature of every incoming request once an app secret is set. Access tokens and secrets live only inside the Salesforce org, never in source code. Users need a dedicated permission set before they can send a message, and the public site user gets only the access it needs to receive webhooks. A messaging tool that touches customer data has to earn trust, and WhatsForce was designed that way from day one.
Pure React Inside A Salesforce World.
The entire interface is written in React and TypeScript, with no Lightning Web Components or Aura anywhere. Record pages only accept certain component types, so WhatsForce uses a thin Visualforce container whose only job is to load a React build from a static resource. Users see a seamless native tab while the code stays modern, testable and shared. One codebase produces both the full inbox app and the compact Contact tab, so every improvement lands in both places at once.
Why Every Customer Team Gains From It.
Customers get answers on the channel they prefer, and agents reply without switching tools. Sales, service and support see the same history on the same record, so a new agent can read the whole story in seconds instead of asking the customer to repeat it. Because every message is standard Salesforce data, it can feed reports, flows and automation. AI suggested replies, template campaigns and conversation analytics become natural next steps on the same foundation.
Your customers already live on WhatsApp and now your CRM does too.
*For more details follow these URLs - *
https://debajyoti-ghosh.web.app/hall-of-builds/whatsforce
https://youtu.be/2hgko9VGHMM?si=Z4j5y96msKAlzx65

