Search for existing answers to your product and support questions.
Familiarize yourself with our support site and learn best practices in working with our team.
Manage Service Requests, View and update service requests submitted by you and others in your organization.
Submit a new issue to our technical support team.
Oracle B2C Service insights from our Technical Support team subject matter experts
Browse resources to assist you in launching your implementation and ensure a successful go-live.
Access your OCI account.
Find product documentation for supported versions of B2C and documentation libraries for related service solutions.
You will have the tools to improve your customers' experience when you learn about all the things our products can do.
Find links for API documentation, Custom Processes, Customer Portal, and Agent Browser UI Extensibility Framework.
Explore how accelerators are designed to demonstrate how an integration scenario could be built using the public integration and extension capabilities of the Oracle B2C Service.
Prepare for a successful transition by reviewing upcoming release changes and enhancements.
Explore webinars, events, and feature kits to learn about B2C Service features, functionality, and best practices from the technical experts.
Oracle MyLearn offers a portfolio of free and paid subscription-based learning resources to help you gain valuable skills, accelerate cloud adoption, increase productivity, and transform your business.
Empower your team with the skills to implement, configure, manage, and use your applications with Customer Experience Cloud Training.
Our goal is to facilitate a friendly, supportive environment where members can easily collaborate with each other on solutions and best practices.
Ask and answer questions specific to B2C.
This is an exciting resource intended to help with your Oracle Service Cloud Analytics.
Share product improvement ideas and enhancement requests with Oracle Development, while collaborating with other Oracle customers and partners.
Update your phone number, email notification preferences, and severity 1 and severity 2 contact preferences.
View the contact managers within your organization.
Find contact information of the Technical Account Manager (TAM) and Client Success Manager (CSM) for your organization.
What are the configuration settings that control Chat Presence Management?
Environment
Chat, Configuration Settings
Resolution
Presence management ensures that chat participants are notified when either the agent or the customer experiences communication difficulties with the chat service.
The configuration settings that play an important role in how Chat presence is managed are:
A Typical No Disconnect Chat
ABSENT_INTERVAL, USER_ABSENT_RETRY_COUNT and AGENT_ABSENT_RETRY_COUNT
ABSENT_INTERVAL and the *RETRY_COUNT configurations determine when an End-User or Agent gets marked Absent and subsequently Disconnected when the chat server pings them and there is no response. For example, when the console loses connectivity or a computer shuts down. The pinging from the chat server will suddenly receive no response. Chats that were ongoing when this happens get RE-ROUTED to the queue. These are VISIBLE.
Example ABSENT_INTERVAL Scenario ABSENT_INTERVAL: 30 seconds AGENT_ABSENT_RETRY_COUNT: 2 9:07:15 Chat server pings, Agent is available. 9:07:31 Agent's computer crashes. 9:07:45 Chat server pings, no response. Retry 1. Agent marked Absent. 9:08:15 (30 seconds later), still no response. Retry 2. 9:08:45 (30 seconds later), still no response. Agent marked Disconnected.
CS_IDLE_TIMEOUT
CS_IDLE_TIMEOUT is by default set to 10 minutes, and a minimum of 5 minutes. It should only be modified in extremely limited circumstances as it has a large, sweeping impact. This setting determines when a chat gets disconnected due to inactivity. This is when the End User and the Agent are not typing; no activity at all is happening. They're both IDLE.
What really is the difference between the ABSENT_INTERVAL and CS_IDLE_TIMEOUT?
ABSENT_INVERVAL is a period of time where the chat server pings the end user or the agent and there is no response. This will happen when maybe the console shut down unexpectedly or the end user lost connectivity. The CS_IDLE_TIMEOUT looks at activity. Has there been any activity between the Chat Agent and the End User? This is where the CS_IDLE_TIMEOUT comes into the picture.