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:
Outlook Integration, February 2009 and later
Issue:
The Outlook Integration creates an incident from a contact's email, but after this email is forwarded internally by the support team, the Outlook Integration doesn't find the contact's incident anymore, in order to append the new internal emails from the support team.
Resolution:
In order for the Outlook Integration to identify the contact and its open incidents, you will need to add the contact in the "Cc" field of the email and make sure it stays there for the duration of the email exchange. As long as the contact is in the "Cc" field, you can use the Outlook Integration at any moment to add the emails to his or her incident's thread.
Cause:
The Outlook Integration detects the contacts used in the "To", "From" and "Cc" fields of the email. It then checks if these contacts have any open incidents in the application and offers the option to append the content of the email to either one of those incidents, or to create a new one.
Initially, when a new email is received from a contact, the Outlook Integration correctly identifies it in the database since the contact is in the "To" field of the email. A new incident is created for this contact and the support team forwards the email internally to other teams in order to solve the customer's issue. These internal emails are relevant for the investigation and the team wants to append them to the contact's incident, but when trying to do so from the Outlook Integration, it doesn't detect the contact, or its existing incidents.
This happens because the contact was removed from the email header. When the initial email was received, the contact was in the "To" field, but it was subsequently removed when the support team forwarded the email internally. This is why the internal emails cannot be appended to the contact's incident.