Incident and Chat Translation Configuration Using Systran Translation Service — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Incident and Chat Translation Configuration Using Systran Translation Service

edited Aug 26, 2025 1:46PM in Communication Channels

Oracle B2C Service offers translation capabilities in the Incident threads and Chat modules of the Agent Browser UI. Both features require a language detection External Object (XO) endpoint and a language translation External Object (XO) endpoint. Refer to Answer ID 12891 for Incident threads and Answer ID 12842 for Chat for further details. This article explains how the language detection and translation endpoints can be configured using Systran Translation Service.

1. Configuration Steps in B2C Service

1.1 Extension Configuration

The language translation functionality in Oracle B2C Service product is expecting the language translate and detect requests and responses in the formats OCI Language Translation Service APIs are behaving. So, in case of using non-OCI Language Translation services, a small customisation is needed to transform the requests and responses before passing over via the external objects connection.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!