Messaging
Messaging in Salesforce refers to the suite of Service Cloud features for handling asynchronous customer conversations across SMS, WhatsApp, Facebook Messenger, Apple Messages for Business, Google Business Messages, and web messaging widgets.
Definition
Messaging in Salesforce refers to the suite of Service Cloud features for handling asynchronous customer conversations across SMS, WhatsApp, Facebook Messenger, Apple Messages for Business, Google Business Messages, and web messaging widgets. It is the modern evolution beyond Live Chat (which is real-time only) and email-to-case (which lacks the conversational pattern). Messaging fits the way customers actually expect to interact with companies in 2026: send a message from a channel they already use, get a response when convenient, continue the conversation across hours or days without losing context.
Messaging in Salesforce runs through several integrated products. Messaging for In-App and Web provides embedded chat widgets in mobile apps and websites with conversational continuity. Messaging for SMS handles inbound and outbound text messages. Messaging for Social handles WhatsApp Business, Facebook Messenger, Instagram Direct, and similar consumer messaging platforms. Each channel routes through Omni-Channel for assignment to the right agent, integrates with Einstein Bots for Tier 1 automation, and surfaces in the Service Console as the agent work surface. Salesforce Messaging is licensed separately from base Service Cloud, with consumption-based pricing for outbound messages on most channels.
How Salesforce Messaging handles modern customer conversations
Asynchronous versus real-time conversation patterns
Live Chat is real-time: the customer expects an immediate response and the agent is locked into the session until it ends. Messaging is asynchronous: the conversation can pause for minutes or days while the customer goes about their life, then resume when convenient. The asynchronous pattern matches how customers actually use messaging apps. Agents handle multiple concurrent Messaging conversations because the response latency is more relaxed than chat. The model fundamentally improves agent productivity versus equivalent chat capacity.
Supported channels and the unified inbox
Salesforce Messaging supports many channels through a unified architecture. Web messaging through Embedded Messaging widgets on customer websites. Mobile in-app messaging through Embedded Service for iOS and Android. SMS through Salesforce Messaging for SMS. WhatsApp Business through the Meta-integrated channel. Facebook Messenger, Instagram Direct, Apple Messages for Business, Google Business Messages each have their own channel configuration. The Service Console agent UX is uniform across channels; agents see one conversation surface regardless of the customer''s channel.
Conversation routing through Omni-Channel
All Messaging conversations flow through Omni-Channel for routing. The routing engine considers agent availability, skills, capacity, and presence to assign new Messaging conversations to the right agent. Routing rules can match conversation language, customer tier, or specific keywords. Same engine handles Cases, Chat, Voice, and Messaging consistently. This unified routing is the difference between Salesforce''s multi-channel architecture and stitching together separate point solutions.
Bot integration: Einstein Bots and Agentforce
Most Messaging deployments use bot integration for Tier 1 automation. Einstein Bot or Agentforce agent handles the initial conversation, gathers context, attempts resolution. When the bot reaches its limit, it hands off to a human agent through Omni-Channel with the conversation history. Modern deployments use Agentforce for richer LLM-driven responses; established deployments still use Einstein Bots for predictable structured flows. The bot layer is what makes Messaging scalable; without it, every conversation requires human attention.
Templates, structured messages, and rich content
Each Messaging channel supports different content types. WhatsApp supports templates with images and buttons. Apple Messages for Business supports rich interactive forms. SMS is plain text plus images. Embedded web/in-app messaging supports the richest interactive UX with custom components. Service Console surfaces channel-specific composition tools so agents send the right content type for each channel. Pre-approved templates (especially for WhatsApp, which requires Meta approval for outbound templates) speed agent productivity.
24-hour windows and re-engagement rules
Some channels (WhatsApp specifically) enforce 24-hour windows: agents can respond freely within 24 hours of the customer''s last message, but proactive outreach after 24 hours requires pre-approved templates. Apple Messages for Business has similar constraints. These rules protect customers from spam but constrain the agent workflow. The platform handles the rules automatically; agents see warnings or template requirements when the window has expired.
Reporting, conversation analytics, and CSAT
Messaging produces rich operational metrics: conversations per channel, conversations per agent, average response time, average handle time, transfer rate, customer satisfaction (CSAT) score from post-conversation surveys. The reporting integrates with Service Cloud standard reports and dashboards. Conversation Mining can extract patterns from large numbers of conversations for quality assurance and process improvement. Build the operational dashboard early because Messaging metrics drive the contact center decisions about staffing, training, and automation.
How to set up Salesforce Messaging
Setting up Messaging is channel-by-channel work. Each channel has its own credentials, configuration, and approval process (especially WhatsApp). Plan the rollout by channel based on customer demand. Start with one channel, get the agent workflow right, then expand. Big-bang multi-channel rollouts produce overwhelming complexity.
- Identify which channels customers actually use
Don''t enable every channel just because Salesforce supports it. Survey customers, review existing support volumes, identify which channels would meaningfully improve experience or capacity. Start with the highest-volume channel.
- Provision Messaging in Service Cloud
Setup > Messaging > Enable. Configure the base Messaging settings. Provision phone numbers for SMS, register WhatsApp Business account, set up Apple Messages for Business, depending on chosen channels.
- Configure each channel separately
Each channel has its own setup: SMS needs a Twilio or LINK account, WhatsApp needs Meta Business verification, Apple Messages needs Apple Business Register registration. Plan time for the external approvals.
- Build the Omni-Channel routing configuration
Define how Messaging conversations route. Skill-based routing for language, product, or tier. Queue-based routing for team assignment. Configure agent capacity for concurrent Messaging conversations.
- Configure Einstein Bot or Agentforce for Tier 1
Build the bot or agent that handles initial conversations. Define the topics it covers, the hand-off criteria, the integration with knowledge base. The bot layer is what makes Messaging scalable.
- Build templates for outbound and follow-up
For channels with 24-hour windows (WhatsApp, Apple), build pre-approved templates for proactive outreach. Submit for channel-specific approval where required. Plan template management as ongoing work.
- Configure the Service Console for agents
Customize the Service Console layout for Messaging conversations. Add chat panels, customer context, related cases, knowledge sidebar. Configure macros and quick text for common responses.
- Train agents and roll out per channel
Messaging conversation patterns differ from email and chat. Agents need training on concurrent conversation handling, template usage, hand-off etiquette, and CSAT-driving practices. Roll out one channel at a time.
SMS, WhatsApp, Facebook Messenger, Apple Messages, Web/In-App Embedded. Each has different configuration and approval requirements.
Einstein Bot or Agentforce agent for Tier 1 automation. Foundation of scalable Messaging operations.
Skill-based, queue-based, or hybrid routing for conversation assignment. Same engine handles all Messaging channels.
- WhatsApp Business requires Meta verification and pre-approved templates for outbound messages. Plan the approval process; templates can take days to approve and templates that look fine to humans get rejected for subtle reasons.
- 24-hour conversation windows on consumer messaging channels constrain proactive outreach. Agents need to understand the rules and the platform handles enforcement automatically.
- Messaging conversations are asynchronous; agents handle multiple concurrent threads. The mental model differs from real-time chat or voice; agent training on this difference is essential.
- Bot hand-off configuration matters. Aggressive escalation defeats the bot purpose; over-restrictive hand-off frustrates customers. Tune the hand-off criteria with real conversation logs.
- Per-message consumption pricing applies to many channels (SMS, WhatsApp). Monitor volume to avoid surprise overages; high-volume marketing-style outbound on these channels gets expensive fast.
Trust & references
Cross-checked against the following references.
- Messaging DocumentationSalesforce Help
- Messaging ChannelsSalesforce Help
Straight from the source - Salesforce's reference material on Messaging.
- Set Up MessagingSalesforce Help
- WhatsApp Messaging SetupSalesforce Help
- Embedded MessagingSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Messaging in Service Cloud?
Q2. What's a key characteristic of messaging conversations?
Q3. What pairs well with messaging?
Discussion
Loading discussion…