How to Create Salesforce Cases from WhatsApp Messages
Customers increasingly use WhatsApp to report damaged orders, request refunds, ask technical questions, send screenshots, and follow up on open issues. The conversation may begin in WhatsApp, but the service process still needs to happen in Salesforce.
WatBox connects WhatsApp with Salesforce so an inbound message can create or update a Case, attach the conversation to the right customer, route the work to an agent, and let that agent reply through WhatsApp from Salesforce.
At a glance: WhatsApp message arrives, WatBox identifies the customer, Salesforce creates or updates the Case, assignment rules route it, and the agent responds from the Case record.
How WhatsApp Case Management Works in Salesforce
- A customer sends a message to the business WhatsApp number.
- WatBox receives the inbound event and customer phone number.
- Salesforce searches for an existing Contact, Person Account, Lead, or active Case.
- WatBox creates a new Case or links the message to the appropriate existing Case.
- Salesforce assignment rules, queues, Flow, or Omni-Channel route the Case.
- An agent opens the Case and replies through WhatsApp without leaving Salesforce.
- Inbound and outbound messages remain available as part of the Salesforce conversation history.
How Can I Create Salesforce Cases from WhatsApp Messages?
WatBox can be configured to create a Salesforce Case whenever a qualifying inbound WhatsApp message arrives. The configuration determines which messages open a Case, how customer records are matched, and what initial Case values are populated.
1. Define the Case Creation Trigger
A Case can be created for every new service conversation or only when the message meets specific criteria. For example, a keyword such as "support," a selected WhatsApp menu option, an AI-classified support intent, or a message sent to a dedicated support number can trigger Case creation.
2. Match the Customer by Phone Number
WatBox uses the WhatsApp phone number to search Salesforce. If a matching Contact, Person Account, or Lead is found, the new Case can be linked to that record. For a new customer, the organization can define whether to create a Contact, Lead, Person Account, or only a Case.
3. Map WhatsApp Data to Case Fields
The first message can populate the Case Subject and Description. Additional values can include Origin = WhatsApp, Status = New, Priority, language, WhatsApp number, campaign source, product, region, and custom fields.
4. Route the Case
After creation, standard Salesforce automation can assign the Case by product, language, geography, customer tier, support skill, or queue. Omni-Channel can then present the work to an available agent.
How Can I Add a WhatsApp Message to an Existing Case?
Not every message should create a new Case. If the customer is replying about an open issue, WatBox can append the message to the existing Case conversation instead.
Common matching strategies include:
- Active conversation: Link the message to the open Case already associated with the WhatsApp session.
- Customer phone number: Find the customer's recent open Case and attach the new message.
- Case reference: Parse a Case number included in the message or template reply.
- Menu selection: Let the customer choose an existing issue from an automated WhatsApp flow.
- Custom business rules: Match by product, order number, account, or another Salesforce field.
Incoming images and documents can also be stored in Salesforce Files and linked to the Case. See our guide to WhatsApp document management in Salesforce for file-handling examples.
How Can Salesforce Cases Send Messages in WhatsApp?
Agents can open a Salesforce Case, view the WhatsApp conversation, and compose a reply through WatBox. The message is delivered to the customer's WhatsApp number while the outbound response remains associated with the Case.
Agents can typically use the Case to:
- Send free-form replies during an active WhatsApp service window.
- Send approved WhatsApp templates when required by WhatsApp messaging rules.
- Share PDFs, images, invoices, instructions, and other supported files.
- Use predefined responses for common support questions.
- Trigger automated status updates from Salesforce Flow.
The customer receives a normal WhatsApp message. The agent stays in the Salesforce Service Console, and the organization retains a unified record of the service interaction.
Automate WhatsApp Cases with Salesforce Flow
Once the conversation is represented as a Salesforce Case, existing Salesforce automation becomes available. Organizations can use Flow, assignment rules, escalation rules, approvals, and notifications without building a separate support process outside Salesforce.
- Instant acknowledgement: Send a Case number and expected response time.
- Priority detection: Mark urgent messages based on keywords or AI-classified intent.
- Queue assignment: Route billing, technical, sales, or language-specific inquiries.
- Status notifications: Inform customers when the Case moves to In Progress, Waiting, or Closed.
- SLA escalation: Alert supervisors when first response or resolution targets are at risk.
- Post-resolution survey: Send a CSAT request through WhatsApp after Case closure.
Recommended Salesforce Case Data Model
A clean data model makes WhatsApp Cases easier to route and report on. The exact fields depend on the organization, but a practical starting point includes:
- Case Origin = WhatsApp
- Contact, Account, Person Account, or Lead lookup
- Customer WhatsApp phone number
- WhatsApp Business number
- Conversation or session identifier
- First inbound message timestamp
- First response timestamp
- Language, product, region, and support category
- Current queue, owner, status, and priority
Implementation Checklist
- Connect the approved WhatsApp Business number to WatBox.
- Choose which inbound messages should create a Case.
- Define Contact, Lead, Person Account, and Case matching rules.
- Map WhatsApp data to Salesforce Case fields.
- Configure duplicate prevention and open-Case matching.
- Set assignment rules, queues, skills, and Omni-Channel routing.
- Create acknowledgement and status-update templates.
- Configure agent permissions and Salesforce Files access.
- Test new customers, known customers, open Cases, attachments, and out-of-window replies.
- Build reports for WhatsApp Case volume, response time, resolution time, and SLA compliance.
For a broader operational view of queues and SLAs, read Salesforce Service Cloud + WhatsApp: Cases, Queues, and SLAs.
Common Use Cases
- Retail: A customer reports a damaged delivery and sends a photo.
- Financial services: A customer asks about an application and submits a supporting document.
- Healthcare: A patient requests help with an appointment or insurance question.
- Education: A student asks about admission status or uploads a missing record.
- Travel: A traveler reports an itinerary problem and receives updates through WhatsApp.
- B2B support: A customer reports a product issue that is routed to a specialist queue.
Benefits of Connecting WhatsApp with Salesforce Cases
- No missed support requests: WhatsApp inquiries enter the formal Case process.
- Complete customer context: Agents see the customer, history, Case, messages, and attachments together.
- Faster response: Queues and Omni-Channel route work immediately.
- Consistent automation: Flow and escalation rules work across WhatsApp Cases.
- Better reporting: WhatsApp volume and performance appear in Salesforce reports.
- Improved governance: Conversations remain visible to authorized teams in Salesforce.
Frequently Asked Questions
How can I create Salesforce Cases from WhatsApp messages?
WatBox can be configured to create a Salesforce Case when a new inbound WhatsApp message arrives. The message, customer phone number, channel, and routing information can be mapped to the Case and related customer record.
How can I add a WhatsApp message to a Salesforce Case?
WatBox can associate inbound and outbound WhatsApp messages with an existing Salesforce Case using the customer phone number, active conversation, Case reference, or configured business rules.
How can WhatsApp create Cases in Salesforce?
An inbound WhatsApp event is received by WatBox, matched to a Salesforce customer record, and used to create a Case. Salesforce assignment rules, queues, Omni-Channel, and Flows can then route and automate the Case.
How can Salesforce Cases send messages in WhatsApp?
Agents can compose a message from the Salesforce Case through WatBox. The reply is sent to the customer's WhatsApp number and stored with the Case conversation history.
Can WhatsApp Cases use Salesforce queues and Omni-Channel?
Yes. Once the WhatsApp inquiry is represented as a Salesforce Case, standard Salesforce queues, assignment rules, skills-based routing, and Omni-Channel can be used according to the organization's configuration.
Can files received through WhatsApp be linked to a Salesforce Case?
Yes. WatBox can store supported WhatsApp attachments in Salesforce Files and link them to the appropriate Case and customer record.
Conclusion
WhatsApp can become a fully managed Salesforce support channel when every inbound inquiry is connected to the right Case, customer, queue, automation, and agent.
With WatBox, businesses can create Salesforce Cases from WhatsApp messages, add new messages and attachments to existing Cases, and send WhatsApp replies directly from Salesforce. The result is faster service, better visibility, and a complete customer support history in one platform.
