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.
Some of our end-user updates to incidents are included as a file attachment to the incident instead of an update to the incident thread.
Environment:
Incident, Incoming email, Service Mailboxes Oracle B2C Service
Resolution:
If an email exceeds the Maximum Description Size value, the email is appended to the incident as a file attachment and a small thread entry refers agents to the attached file. This reduces the possibility of long emails being cut in half, which may leave malformed HTML in the attachment. To allow the majority of these emails to be added as incident threads instead of being added as attachments, you must increase the Maximum Description Size value. The maximum value allowed for this field is 1,048,576. The default is 250,000.
The Maximum Description Size value is configured individually for each mailbox that is configured in your site. Therefore, if you have multiple mailboxes configured, you must update the Maximum Description Size for each mailbox.
To modify the Maximum Description Size, use the steps below:
For additional information, refer to the 'Editing Oracle-managed Service Mailboxes' section in the Online Help User Guide documentation. To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.
Determining the appropriate value to use depends on the configuration of your site, the nature of your business and the emails you receive from your end-users. In general, setting this value somewhere between 25000 and 50000 should correct most of the cases where an attachment is appended rather than the incident thread being updated.
In each case when an email is attached as text file there is a note inserted into the thread of the incident similar to the following:
"=============== text File Attachment ============== Attachment 1.txt, 6032 bytes, added to incident"
The size of the email is listed in this information. You can use these values to determine the value of your Maximum Description Size configuration.