Messaging for In-App
Messaging for In-App is the Salesforce Service Cloud feature that lets customers exchange messages with support agents inside the customer''s own mobile app, using a Salesforce-supplied SDK.
Definition
Messaging for In-App is the Salesforce Service Cloud feature that lets customers exchange messages with support agents inside the customer''s own mobile app, using a Salesforce-supplied SDK. Customers tap a Chat-with-us button in the app; the SDK opens a chat window; messages flow to Salesforce, where they appear in the Service Console for an agent to respond. The conversation stays inside the customer''s app the entire time, providing a seamless support experience without forcing the customer to leave for a web browser or email.
Messaging for In-App is part of the broader Salesforce Messaging product family that also includes Messaging for Web (the same capability for desktop websites), Messaging for SMS, and Messaging for WhatsApp. All four products run on the same Service Cloud foundation: messages route through Omni-Channel to the right agent, transcripts persist on the Messaging Session standard object, and Einstein Bots can handle the initial conversation before escalating to a human. Modern customer-service strategies often start with In-App and Web Messaging because they capture intent at the moment the customer is engaged with the product.
How Messaging for In-App fits into Salesforce Service Cloud
The Salesforce SDK
Salesforce ships native iOS and Android SDKs for Messaging for In-App. App developers add the SDK to their mobile app, configure it with the Salesforce org connection details, and place the entry-point UI (typically a Chat button or floating launcher) where customers naturally find it. The SDK handles the message transport, the chat-window rendering, and the integration with Salesforce-side agent routing.
Routing through Omni-Channel
Customer-initiated messages enter the Omni-Channel routing engine the same way Chat, Email, Case, and Voice work items do. Omni-Channel matches the conversation to the right agent based on skills, capacity, and presence. The agent receives the message in the Service Console with full customer context (account, prior cases, conversation history). The unified routing is the main reason to use Salesforce Messaging instead of standalone chat tools.
Einstein Bot pre-triage
Most In-App Messaging implementations start the conversation with an Einstein Bot. The bot greets the customer, asks the reason for contact, attempts simple self-service (status lookup, password reset, FAQ), and escalates to a human agent when needed. The bot deflects 30-60 percent of conversations in mature deployments, dramatically improving cost-per-contact.
Messaging Session object
Each Messaging conversation produces a Messaging Session standard object record holding the conversation metadata: customer identifier, start time, end time, agent assigned, channel (In-App, Web, SMS, WhatsApp). The individual messages live on Conversation Entry records linked to the Session. Reports on Messaging Session surface conversation volume, average handle time, deflection rate, and customer-satisfaction signals.
Identity and context passing
The SDK can pass authenticated user context to Salesforce. If the customer is logged into the mobile app, the SDK forwards the user identifier so Salesforce can look up the customer''s Contact, prior cases, and account history. The agent sees full context the moment the message lands; no questions about who is calling.
Async vs. real-time conversations
Messaging for In-App supports both real-time conversations (agent and customer messaging in active back-and-forth) and async conversations (the customer sends a message, closes the app, returns hours later to the response). The conversation persists; the customer sees the full thread when they reopen the app. This async pattern is the difference between Messaging and traditional Live Agent chat.
Push notifications
When an agent replies to an async conversation, the SDK fires a push notification to the customer''s phone. The customer sees the notification, taps it, and re-enters the conversation. The push-notification integration is what makes async messaging work; without it, customers would miss agent replies.
Roll out Messaging for In-App in a mobile app
The rollout is a coordinated project between Salesforce admins and the mobile app development team. Plan multi-week effort for the SDK integration plus the Salesforce-side configuration.
- Confirm licensing
Messaging for In-App is licensed separately. Confirm contract terms with the Salesforce account team.
- Configure Messaging in Salesforce Setup
Setup, Messaging, configure the deployment for In-App. Set up Omni-Channel routing, agent skills, and the Service Console layout.
- Build the Einstein Bot if needed
Design the bot conversation: greeting, intent recognition, self-service actions, escalation rules. Test the bot thoroughly before exposing to customers.
- Integrate the SDK in the mobile app
App developers add the iOS and Android SDKs. Configure with the Salesforce org details and place the entry-point UI.
- Wire push notifications
Configure push notification delivery so customers get notified of agent replies when the app is closed.
- Pilot with a customer cohort
Launch to a small group of customers first. Measure deflection rate, customer satisfaction, and agent feedback. Expand once baselines exist.
- Messaging for In-App requires SDK integration in the mobile app. Coordinate with the mobile dev team early; this is not a Salesforce-only configuration.
- Push notifications need careful design. Misfiring notifications damage trust faster than missing them.
- Einstein Bot quality is the main driver of deflection rate. A poorly-trained bot frustrates customers and increases escalation volume.
- Messaging licensing scales with conversation volume. Budget carefully; viral spikes can exceed the contract.
Trust & references
Cross-checked against the following references.
- Messaging for In-AppSalesforce Help
- Salesforce Messaging OverviewSalesforce 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 for In-App?
Q2. What's the value of conversation persistence?
Q3. Who benefits from Messaging for In-App?
Discussion
Loading discussion…