Salesforce's new Agentforce WhatsApp agent, Casey, went live on September 11. It now handles customer service over voice, SMS, WhatsApp, and web chat, the first time Salesforce has shipped a native, generally-available WhatsApp agent instead of leaving that integration to a partner. If you run your business on Salesforce, this is worth a look this week. If you don't, and most businesses we build for don't, it changes nothing about how you'd set up WhatsApp automation right now.
What Is Salesforce's Agentforce WhatsApp Agent?#
Salesforce introduced seven Agentforce agents on September 11, covering sales, support, e-commerce, HR/IT, and supply-chain tasks. The customer-facing ones:
- Casey: customer service over voice, SMS, WhatsApp, and chat (live now)
- Piper: greets and routes inbound leads (live now)
- Carter: e-commerce shopping assistant with in-chat checkout (live now)
- Fin: complex support workflows, built on the $3.6B Fin AI acquisition (live now)
- Hunter: outbound sales agent (pilot now, GA in November)
Salesforce describes the underlying tech as a "long-horizon runtime": agents that hold context and keep working toward a goal across days or weeks, not just one session.
Does This Affect Your WhatsApp Chatbot?#
Only if you already pay for Salesforce. Casey plugs into Customer 360, so it needs your orders, cases, and customer records already living inside Salesforce's data model.
If you're running WhatsApp through a standalone Business API number, which describes most of the small and mid-sized businesses we work with across the GCC, Europe, USA, Canada, and Indian SMB market, this launch touches nothing you've already built. Salesforce didn't publish pricing for any of the seven agents. That usually means it's priced for accounts already deep in the ecosystem, not a line item a ten-person business adds on a whim.
It's a different story from Meta putting its own AI agent, Muse, directly inside WhatsApp back in September, because Muse reaches any WhatsApp user. Casey only reaches Salesforce customers.
The Trade-Offs Nobody's Advertising#
The real upside: Salesforce customers get a WhatsApp agent with shared memory across tickets, orders, and past conversations, built and maintained by the vendor. That's genuinely more than most first builds attempt.
The catch is lock-in. Casey only works inside Customer 360. Switch CRMs later and you're rebuilding the entire conversation layer, not exporting a chat log.
Salesforce also cited customer results in the announcement: one company resolving "50% of chat inquiries" autonomously, another's pipeline "60% built" by Hunter. Those are the vendor's own customer quotes, reported in SiliconANGLE's coverage and Salesforce's release alike, not independently audited figures. Treat them like any launch-day case study. Promising. Unverified. Worth asking to see reproduced before you believe it applies to you.
How We're Handling It#
We build WhatsApp and chat automation for small businesses across the GCC, Europe, USA, Canada, and Indian SMBs, and this launch didn't move our stack. We reviewed Casey's architecture the day it shipped. It confirmed what we expected: a Salesforce feature, not a general-purpose WhatsApp product.
For a financial-services client this year, we built the comms stack the other way around: MyOperator for IVR, AiSensy on WhatsApp, and a self-hosted n8n layer routing everything into one shared inbox. All of it runs off a single business number, with role-based access for the staff who need it. No CRM seat required. No migration risk if the client switches tools later.
I'll admit my first read of the announcement was that this finally puts real pressure on smaller automation builds. It doesn't, not for the businesses we serve. It competes with the WhatsApp add-ons already bundled inside CRMs a company is paying for regardless, which is a narrower fight than it sounds.
That's still the WhatsApp lead-response build we're recommending this week to anyone asking whether they need "the Salesforce thing" to compete. It's also worth remembering WhatsApp's own per-message pricing changes on October 1 apply no matter which agent answers the message.
What I'd Tell a Client Asking About This#
If you already run Salesforce and your support team is drowning, pilot Casey. It's a real feature, and shared context across channels is worth testing inside a contract you're already paying for.
If you don't run Salesforce, don't buy it to get WhatsApp automation. A dedicated build on the WhatsApp Business API costs a fraction of a Salesforce seat, and it doesn't require re-platforming your CRM to use it. Start smaller. Add the CRM later if you actually need one.
If you're weighing a Salesforce-style build against something leaner for your own WhatsApp number, send me what you're running and I'll give you a straight answer. Two minutes, no pitch. [cal.com/webepex/growth-review]
