Configure a timeout that moves abandoned messaging sessions to an inactive state when
customers leave a conversation by closing their browser or tab, navigating away from the page, or
losing their connection.
Enhanced In-App Chat and Enhanced Web Chat channels
This article doesn’t apply to:
Enhanced WhatsApp, Standard and Enhanced Facebook Messenger, Standard and Enhanced
SMS, Enhanced Apple Messages for Business, Enhanced LINE, and Bring Your Own Channel
User Permissions Needed
To set up this feature:
Customize Application
AND
Modify Metadata Through Metadata API
Functions
To modify permission sets and profiles:
Manage Profiles and Permission Sets
Considerations and Limitations
This feature applies only to conversations with service reps. Sessions that include bots or
Automated Service Agents (ASAs) aren’t moved to an inactive state while those participants are
present.
Because this feature is event-based, the timeout typically takes an additional 1 to 2
minutes to process. For example, if the timeout is set to 10 minutes, the session can become
inactive between 10 and 12 minutes after inactivity.
When a customer abandons a chat that's already accepted by a service rep, the session
becomes inactive after the timeout. The chat transcript becomes read-only, and the service rep
can't send messages. A system message indicates that the session is inactive.
On mobile web and Mobile SDK clients, if a customer locks their device or moves the app or
browser to the background, the app disconnects from the server. The system considers the chat
abandoned, which triggers the timeout period and makes the session inactive when the timer
ends.
Turn On Abandoned Chats
From Setup, in the Quick Find box, enter Messaging Settings, and
then select Messaging Settings.
To edit the channel you want to work with, click the arrow next to the channel name, and
then select Edit.
On the Enhanced Chat settings page, in the Abandoned Chats section, select
Automatically remove abandoned chats.
For Minutes to Timeout, enter between 2 and 30 minutes to wait before changing the session
to an inactive state.
Save your changes.
In Embedded Service Deployment Settings, click Publish to apply the
changes.
Hjalp denne artikkelen med å løse problemet ditt?
La oss få vite det slik at vi kan forbedre!
Laster
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.