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:
Incident Attributes
Resolution:
The Source field indicates how the incident was created, such as from the Ask a Question page or from an email submittal.
The Source field is located on the Details tab by default and cannot be set manually. The Source field is set based on how the incident is created. For example, incidents created from the Oracle B2C Service Console initially display No Value in the Source field. When the incident is saved and re-opened, the Source displays as CX Console - Incident Editor.
Note: When adding a customer entry to the incident thread, staff can indicate the source of that specific thread by setting the value in the header to be By Phone, By Fax, By Post, By Web Form, or By Email.
The Mailbox field allows you to associate each incident to a specific mailbox. The Mailbox field is located on the Details tab. By selecting a different mailbox when you edit an incident, you can override the default mailbox or the mailbox the incident was originally associated with. This means that future responses will be sent from the mailbox you select. Since different mailboxes can have different display names and different reply-to addresses, you can ensure that the incident is associated with the proper mailbox for the content of the incident.
Similarly, the Interface field allows you to specify the interface association of the incident. This allows agents to be logged into one interface but assign the incident to a different interface as necessary based on the source of the incident, i.e. a phone call or fax.
In most cases, these fields are used when creating a new incident from the administration consoles. When creating a new incident, the staff member can specify which source, mailbox and/or interface the incident is to be associated with. This allows a staff member to create an incident while logged in to one interface, and yet associate the incident to a mailbox used with a different interface or to a different interface entirely. This allows staff to be able to create incidents from incoming phone calls and remain logged in to a single interface while creating incidents across all interfaces as necessary.
You can modify the incident workspace to remove these fields.