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.