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.
Why does Chat include a generic email address for the customer?
Environment:
Chat - End-user Pages, Customer Portal
Resolution:
All chats should be launched with some information to identify whether the chat was launched by an existing or new contact. The fields that are available to do this are First Name, Last Name, and Email Address.
If a chat is launched without any of this information, the product will automatically designate the chat as having an email address of anonymous@anonymous.invalid. The value of this email address can be changed and it is stored in a message base named ANONYMOUS_AT_ANONYMOUS_INVALID_LBL.
In versions November 2009 and later, the Chat pages were redesigned so that they could be customized through Customer Portal. With these changes, new precautions should be made to ensure that contacts cannot launch a chat without required contact information.
The standard chat pages are located in WebDav in the app/chat directory. The page names are chat_launch and chat_landing. If you require login to launch a chat, you must ensure that the meta tag includes the login_required = true parameter on both of these pages. If this is only done on the chat_launch page, you will be able to access the chat_landing page directly without logging in and without filling out any required fields.
If you do access the app/chat/chat_landing page directly, they will likely create a chat that will be associated to the anonymous@anonymous.invalid contact record.
In versions May 2010 and later, additional functionality was added so that you can require specific contact fields to be provided when a chat is launched. If a field is missing, a message will be displayed stating: "One or more required contact fields are missing. Please review all fields and re-submit the chat request." The First Name, Last Name and/or Email Address fields can be set to required. This is done when calling the standard ChatServerConnect widget in the chat_landing page code. Simply set the appropriate parameters to true when calling the widget. The name of each parameter is: first_name_required, last_name_required, email_required.