What is the most important tip for working with Messaging Settings?

Each channel needs its own provisioning. WhatsApp requires Business API account; Apple requires Apple Business Register; Facebook requires Page connection. Plan timing across teams.

AdministrationIntermediate

Messaging Settings

Q: Can a Salesforce admin configure Messaging Settings without writing code?

Messaging Settings is a declarative admin feature, meaning it can be configured through Salesforce's point-and-click interface without writing any code.

Q: What is the primary benefit of Messaging Settings for Salesforce administrators?

Messaging Settings is an administration feature that empowers admins to manage the Salesforce environment through declarative, point-and-click configuration.

Q: Why is understanding Messaging Settings important for Salesforce admins?

Administration features like Messaging Settings are fundamental to maintaining a healthy, secure, and efficient Salesforce org on an ongoing basis.

Messaging Settings is the Salesforce Setup page that controls the org-level configuration for Messaging for In-App and Web, the platform's customer messaging product.

Hear it

§ 01

Definition

Messaging Settings is the Salesforce Setup page that controls the org-level configuration for Messaging for In-App and Web, the platform's customer messaging product. The page consolidates the toggles and policies that govern messaging across channels: which channels are enabled (in-app, web, WhatsApp, Apple Messages for Business, Facebook Messenger), how messages route to agents, what bots handle which conversations, and how messaging interacts with the standard Salesforce data model (Cases, Contacts, Leads). The settings are the master control plane for any customer-messaging deployment.

Configuration involves coordination across multiple teams: Service Cloud admins for channel routing, integration teams for channel provisioning (WhatsApp Business API, Apple Business Register), bot designers for Einstein Bots integration, and compliance teams for message retention policies. Each Messaging Settings change should go through a defined release process because mis-configuration can take down customer-facing chat entirely or route conversations incorrectly. The page is straightforward when fully understood, but the interactions between settings, channels, and downstream automation make it deceptively complex to operate at scale.

§ 02

What Messaging Settings controls

Channel enablement

Each messaging channel has its own enablement toggle. Web Messaging and In-App Messaging are usually the starting point for most orgs. WhatsApp and Apple Messages for Business require additional provisioning with the respective platforms (WhatsApp Business API account, Apple Business Register). Facebook Messenger requires Facebook Page connection. The setup is per-channel, with channel-specific credentials and configuration.

Routing and agent assignment

Inbound messages route to agents through Omni-Channel or custom routing logic. Messaging Settings exposes the routing options: capacity-based, skills-based, or custom Apex. Configure the routing aligned with agent staffing and capability matrix. Misconfigured routing produces conversations stuck in queue or unassigned.

Einstein Bots integration

Einstein Bots handle initial customer interactions before routing to a human agent. Messaging Settings configures which bot handles which channel, when handoff to human occurs, and how the bot context transfers to the agent. Plan the bot handoff carefully; abrupt handoffs frustrate customers, and agents need context to continue effectively.

Message retention and storage

Messages are stored as MessagingSession and ConversationEntry records. Messaging Settings can configure retention policies (delete after N days, archive after M days) for compliance. GDPR and similar regulations require data minimization; configure retention aligned with regulatory and business needs.

Messaging Components library

The page hosts the Messaging Components library (Text, Buttons, List Picker, Time Picker, Form, etc.) used in rich messages. Configure components and their per-channel rendering here. The components are referenced by bots and agent quick actions.

Authentication for messaging

Some scenarios require authenticating the customer (account management, sensitive support). Messaging Settings includes options for authentication flows: customer-initiated identity verification, OAuth-based account linking, secure form submission. Configure based on the use case and regulatory environment.

Reporting and analytics integration

Messaging activity flows to standard Service Cloud reports through MessagingSession and ConversationEntry objects. Build reports on volume, response time, resolution rate. Messaging Settings does not directly produce reports but configures the data structures the reports query.

§ 03

Configure Messaging Settings end to end

Setting up Messaging Settings involves channel provisioning, routing configuration, bot integration, and ongoing management. The steps below cover a phased rollout.

Confirm Messaging is licensed
Messaging for In-App and Web requires Service Cloud and specific Messaging licensing. Confirm provisioning.
Provision channels with external platforms
For WhatsApp, Apple, Facebook: complete the platform-side onboarding. Get credentials and account IDs.
Open Messaging Settings
Setup > Messaging Settings. The page shows current configuration per channel.
Enable channels in Salesforce
For each channel, enable in Messaging Settings using the credentials from external provisioning.
Configure routing
Set routing logic: capacity-based, skills-based, or custom. Test routing with a small set of agents before going live.
Integrate Einstein Bots
Build the bot in Einstein Bot Builder. Configure handoff to human agents. Design context transfer carefully.
Set retention policies
Configure message retention aligned with GDPR and business requirements. Document the policy.

Key options

Web Messagingremember

Embedded chat on web pages. Standard starting point.

In-App Messagingremember

Mobile app embedded chat. Requires SDK integration.

WhatsApp Businessremember

WhatsApp channel through Business API account.

Apple Messages for Businessremember

Apple messaging through Apple Business Register.

Facebook Messengerremember

Facebook Page-connected messaging.

Gotchas

Each external channel needs separate provisioning. WhatsApp Business API approval can take weeks; plan accordingly.
Routing configuration is critical. Bad routing produces stuck or misrouted conversations; test thoroughly.
Bot-to-human handoff needs context transfer design. Without it, customers re-explain everything to the agent.
Retention policies need GDPR alignment. Default may exceed regulatory limits; review per region.
Messaging Components shared between bots and agents. Changes affect both surfaces; coordinate.

Was this entry helpful?

Help us write better definitions. Quick reactions or detailed edit suggestions.

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. Can a Salesforce admin configure Messaging Settings without writing code?

Q2. What is the primary benefit of Messaging Settings for Salesforce administrators?

Q3. Why is understanding Messaging Settings important for Salesforce admins?

Discussion

Loading…

Loading discussion…

Back to Dictionary