Salesforce Digital Engagement is a $75/user/month Service Cloud add-on that unifies WhatsApp, SMS, Messenger and chat into one console with omnichannel routing and CRM context. It now pairs with Agentforce and Einstein Bots to automate first-line support across every channel a customer uses, with Salesforce Consulting helping businesses align these capabilities with their service operations.
Salesforce Digital Engagement is a Service Cloud add-on that brings WhatsApp, SMS, Facebook Messenger and chat into a single agent console, so support teams stop juggling separate apps for every channel a customer happens to use. What sets it apart from a basic unified inbox is the data model underneath, supported by Salesforce Consulting for effective implementation.
Every incoming message creates a MessagingSession record, tied to a MessagingChannel for the endpoint and a MessagingEndUser for that customer. Related sessions group into a Conversation object, though most reporting still happens against MessagingSession directly.
That’s the foundation. Here’s what else is worth knowing before setting anything up:
Key Takeaways
- Digital Engagement is sold as an add on to Service Cloud Enterprise or Unlimited licenses.
- It covers SMS, WhatsApp, Facebook Messenger, Apple Messages for Business, LINE and Bring Your Own Channel integrations.
- Each license includes 25 Einstein Bot conversations per user per month, free.
- Omnichannel routing, a unified workspace and full customer context are the three pillars that separate this from juggling separate apps.
- Consent rules, KPIs and strategy matter just as much as the technology itself.
How Salesforce Digital Engagement Manages Customer Conversations
When a customer messages on any connected channel, Salesforce Digital Engagement routes it through Omni-Channel based on agent skill, presence and workload. Four components do most of the work:
- Omni-Channel routing: Evaluates agent skill, presence status and workload before assigning a session, using either a queue-based routing configuration or an Omni-Channel Flow with a Route Work element.
- Unified workspace: Renders every channel inside the same Service Console page using the Conversation or Enhanced Conversation component, so agents never open a separate tab for WhatsApp, SMS, or chat.
- Bot integration: Einstein Bots handle first contact through fixed conversational flows, included free at 25 conversations per user per month.
- Channel Menu: A component placed on an Experience Cloud site or public website listing every contact option, configured under Service Setup.
Routing is where most implementation time goes. Queue and routing configuration is simpler because work lands in a queue and goes to whichever agent matches configured priority. Omni-Channel Flows are more capable and required for routing to enhanced bots or applying conditional logic, like sending specific accounts to a named rep.
Salesforce Digital Engagement Channels
Every channel supported here comes with its own rules once it’s live. What’s available, how each one handles timing and which architecture tier it runs on all decide what you can build.
Supported Channels
Salesforce Digital Engagement brings a specific set of communication channels into the Service Cloud console, letting agents respond from one central place regardless of where the customer reached out. Supported channels include:
- SMS
- Facebook Messenger
- Apple Messages for Business
- LINE
- Bots
- Messaging for In-App and Web, the recommended replacement for Chat
Some of these require additional setup or partner integrations before they’re production ready, but depending on business needs, most orgs enable a mix of two or three.
Channel Behavior by Type
Each channel behaves differently depending on whether it’s asynchronous, real time, or automated, which determines how fast your team needs to respond:
| Channel Type | Examples | Availability Requirement | Notes |
| Asynchronous | SMS, WhatsApp, Facebook Messenger | Queued, agents respond when available | SMS and WhatsApp carry per message costs on top of licensing |
| Real time | Chat (retiring), Messaging for In-App and Web | Agents must be online with capacity | Embedded Chat can capture a case form if no one’s free |
| Automated | Einstein Bots, Agentforce agents | Always on | 25 bot conversations per user per month included free |
| Emerging | LINE, Apple Messages for Business, Bring Your Own Channel | Varies by integration | Often needs partner setup or extra configuration |
Enhanced vs Standard Architecture
Which architecture a channel runs on determines what’s possible and the deciding factor is AI compatibility:
| Capability | Standard Channel | Enhanced Channel |
| Bot type | Rule-based bots only | Rule-based bots and Agentforce agents |
| Outbound notifications | Template-based, via Message Notification flow action | Component-based, via Send Conversation Messages flow action |
| Session initiation | Start Conversation quick action | Send Message global action |
| Session statuses | Basic | Adds Inactive, Consent, Error |
| File attachments | Limited | Broader range, including larger files |
Confirm a channel is on the enhanced architecture before adding Agentforce to it. Upgrading isn’t automatic and usually needs a dedicated migration project.
Salesforce Digital Engagement Channel Menu
The Channel Menu is a component placed on an Experience Cloud site or public website that lists every contact option together, so customers pick whichever channel suits them. It’s configured under Service Setup alongside Embedded Service Deployments and it can’t coexist with an older Embedded Service Chat widget on the same site, so that legacy deployment needs removing or folding into the menu.
Consent and Opt-In Rules for Salesforce Digital Engagement
Consent requirements differ by channel. WhatsApp and Facebook Messenger generally assume implied consent once a customer messages first, since they initiated contact. Short Code SMS is the exception. Customers there must explicitly text a keyword like START or YES before you’re permitted to reply, a safeguard against spam complaints.
Messaging for In-App and Web offers the most granular control of the group. Under Messaging Settings in Setup, admins can:
- Require opt-in explicitly or skip it depending on how strict the channel needs to be.
- Write custom opt-in prompts shown to customers before the conversation starts.
- Configure keywords tied to specific actions, like opting out.
- Localize automated responses into multiple languages without custom development.
How Much Does Salesforce Digital Engagement Cost?
A license runs $75 per user per month, sold as an add on to Service Cloud Enterprise or Unlimited editions. Some Unlimited Edition bundles already include unlimited Messaging for In-App and Web plus those 25 free bot conversations per user.
SMS and WhatsApp aren’t fully covered by that flat fee. Both are paid channels on top of the license, so every message can carry its own small cost. If you’re planning high volume SMS campaigns, run the math with your account executive first.
Here’s the pricing details:
| Item | Included in $75/user/month? |
| Messaging for In-App and Web | Yes, unlimited on Unlimited Edition |
| 25 Einstein Bot conversations per user | Yes |
| SMS and WhatsApp message volume | No, billed separately |
| LINE, Apple Messages, Bring Your Own Channel | Setup often needs partner support |
Pricing also shifts by region and existing edition, so treat these figures as a starting point.
Automation and AI in Salesforce Digital Engagement
AI has moved from a nice-to-have to the main reason teams adopt Salesforce Digital Engagement and the platform now runs three distinct layers of automation:
- Einstein Bots: Run fixed conversational flows to greet customers, answer common questions and collect details before handing off to a live agent, so simple requests get resolved instantly instead of sitting in a queue. Every license includes 25 bot conversations per user per month, with templates provided to shorten setup.
- Agentforce: Reasons through requests using the Atlas Reasoning Engine instead of following a script, taking real actions against Salesforce data rather than just collecting information for a human to act on later. It escalates only when a request genuinely needs a person and it requires enhanced Messaging channels to run.
- Flow: Builds the connective tissue outside the AI layer. Custom routing logic, automatic case creation, record updates and follow-up actions triggered by what the customer said, keeping things running once bots and agents hand off structured data.
The newest addition, Agentforce Help Agent reached general availability across voice, web, portal and messaging channels. It connects to Salesforce Knowledge, ships with prepackaged actions for cases, orders and appointments and comes with a new billing model to match:
| Pricing Model | Structure | Best Fit |
| Pay-per-resolution | $2 per issue resolved autonomously; no charge on escalation or abandonment | Teams wanting cost tied to outcomes |
| Per conversation | $2 per conversation regardless of resolution | Predictable, high-touch use cases |
| Flex Credits | Roughly $0.10 per action, sold in blocks of 100,000 credits | Granular, mixed workloads |
| Per-user add-on | $125 to $150 per user per month | Heavy, consistent internal use |
Under pay-per-resolution, you only pay when Help Agent closes a conversation start to finish without a human touching it, tying cost directly to resolution volume.
Conclusion
If you’re running standard channels today, the highest leverage move is upgrading to enhanced Messaging before layering in Agentforce, since AI agents simply won’t run otherwise. Map your WhatsApp WABA setup and template approvals first, since Meta’s four-day review window is usually the longest lead time in any Salesforce Digital Engagement rollout.
Talk to your account executive about enhanced channel migration paths, then request a technical walkthrough of Omni-Channel Flow configuration for your specific routing logic.
FAQs
Can I use Digital Engagement without Service Cloud?
No. It’s sold strictly as an add-on to Service Cloud Enterprise or Unlimited editions, never as a standalone product.
Can one agent handle multiple channels at once in Salesforce Digital Engagement?
They can cover all of them at once. Everything shows up in the same console, so there’s no need to keep a separate app open for each channel while working.
Is Salesforce Digital Engagement available in all regions?
It changes by region. Which editions already include Digital Engagement and what it costs on top of that, both shift depending on where you’re buying, so it’s worth checking with an account executive rather than assuming your quote matches what a colleague in another country got.
What happens to a customer’s message in Salesforce Digital Engagement if no live agent is online?
The customer can submit a case form through Embedded Chat instead of being left without a response. That submission creates a case tied to the customer’s record automatically, so the request is captured and routed to an agent once one becomes available.
