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.
Environment: Chat, Syndicated Conditional Chat Link widget Resolution:
The min_sessions_avail attribute represents the minimum number of open agent sessions that must be available in order for the link to be actionable. This trigger will be disabled if it is set to 0.
The wait_threshold on the other hand, represents the maximum wait time where the end-user should still be allowed to launch a chat. Again, the trigger is disabled if it is set to 0.
Important: Available sessions will always override wait threshold.
Additional information with regards to min_sessions_avail attribute can be found by reading Answer ID 6369: Chat unavailable when there are no agent sessions available
As for wait_threshold,when min_sessions_avail is disabled, this attribute comes into play. It verifies the average wait time of end-users for a given queue and if this time is lower than the value defined, the link will show as active. This average wait time is being calculated from the number of samples defined within the AVERAGE_WAIT_TIME_SAMPLES configuration setting. The average wait times are reset based on the following conditions:
IDLE_QUEUE_WAIT_TIME_RESET_SECONDS Specifies the amount of time in seconds of no queue activity, after which waiting info values will be reset. Minimum is 300. Default is 14400 seconds (4 hours). IDLE_QUEUE_WAIT_TIME_RESET_SECONDS configuration setting has passed and no chats have entered the queue, the average time value will be reset by submitting a chat that is routed to the queue in question. In other words, IDLE_QUEUE_WAIT_TIME_RESET_SECONDS represents the time interval and the 'submitted chat' represents the trigger.
IDLE_QUEUE_WAIT_TIME_RESET_SECONDS Specifies the amount of time in seconds of no queue activity, after which waiting info values will be reset. Minimum is 300. Default is 14400 seconds (4 hours).
IDLE_QUEUE_WAIT_TIME_RESET_SECONDS configuration setting has passed and no chats have entered the queue, the average time value will be reset by submitting a chat that is routed to the queue in question. In other words, IDLE_QUEUE_WAIT_TIME_RESET_SECONDS represents the time interval and the 'submitted chat' represents the trigger.
Note: The server will return a wait time of 0 when there are available agents/sessions. This is because the chat widget can be configured to not use sessions as an evaluator for widget availability, and needs to be able to show as available even if the current wait time is greater than the wait_threshold set in the widget. This note is added for clarity due to confusion that can arise from seeing a high wait time in chat reports but still seeing a chat widget with a lower wait_threshold show as available.