# Language Services The Language Services configurations determine which external translation and language detection engine Aisera uses across all conversations, knowledge ingestion, and ticket processing. These settings are configured in **Settings > Configuration > Language Services** and apply to the entire tenant. Configure only the credential fields that correspond to your selected provider. ## General ### Language Service Provider | **Type** | Dropdown | | ----------- | -------- | | **Default** | GOOGLE | Selects the external translation and language detection engine Aisera uses across all conversations, knowledge ingestion, and ticket processing. If the selected provider's credentials are missing or the provider returns an empty result, Aisera falls back to AWS Translate for that request. Select the provider that matches your organization's existing translation contract or infrastructure. {% hint style="warning" %} If you want fallback translation requests to route through your own AWS account, keep the **AWS ARN ROLE** and **AWS S3 Region** fields configured. If those fields are empty, Aisera routes fallback requests through its own platform-level AWS account instead. {% endhint %} {% hint style="info" %} **Azure Open AI** routes through Aisera's internal large language model (LLM) Gateway. No credentials are required in this panel when Azure Open AI is selected. {% endhint %} ### Language detection confidence threshold | **Type** | Decimal | | ----------- | ------- | | **Default** | 0.7 | Sets the minimum confidence score a language detection result must reach before Aisera accepts it as valid. Values are on a `0.0` to `1.0` scale, where the default of `0.7` means the provider must report at least 70% confidence before Aisera acts on a detected language. Aisera discards results below the threshold. If no results survive, Aisera falls back to the bot's configured default language for that request. Raise this value if Aisera is acting on incorrect detections for short or ambiguous messages. Lower it if valid non-English messages are consistently falling back to the bot's default language. ### Enable Language Detection in Ticket Ingestion | **Type** | Checkbox | | ----------- | -------- | | **Default** | Enabled | Controls whether Aisera automatically detects and records the language of incoming tickets at ingestion time. When enabled, Aisera analyzes each ticket's title and description, then stores the detected language on the ticket record. Aisera skips detection if the ticket already carries a language value from the source system. Keep this enabled when your environment ingests tickets in multiple languages and downstream features such as routing, analytics, or multilingual search depend on knowing each ticket's language. Disable it only if language detection at ingestion causes performance issues or if language data is already reliably provided by your ticketing system. {% hint style="info" %} Detection runs through Aisera's internal language classification service and is not affected by your **Language Service Provider** selection. {% endhint %} ## Language IO ### Language IO base URL | **Type** | Text field | | ------------ | ---------------------------------------------------- | | **Default** | `https://golinguist.com/linguistnow/resources` | | **Requires** | **Language Service Provider** set to **Language IO** | Sets the root endpoint Aisera uses for all Language IO translation and language detection requests. Override this if your Language IO deployment uses a private or regional endpoint. See also: , [Language IO password](#language-io-password) ### Language IO user name | **Type** | Text field | | ------------ | ---------------------------------------------------- | | **Default** | `AiseraAPI` | | **Requires** | **Language Service Provider** set to **Language IO** | The username credential used to authenticate with the Language IO API. See also: [Language IO base URL](#language-io-base-url), [Language IO password](#language-io-password) ### Language IO password | **Type** | Password field | | ------------ | ---------------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Language IO** | The password credential used to authenticate with the Language IO API. See also: [Language IO base URL](#language-io-base-url), [Language IO user name](#language-io-user-name) ## Language Weaver Both credential fields in this cluster must be configured together for the Language Weaver provider to function. ### Language Weaver Client Id | **Type** | Text field | | ------------ | -------------------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Language Weaver** | The client identifier used to authenticate Aisera with the Language Weaver translation service. See also: [Language Weaver Client Secret](#language-weaver-client-secret) ### Language Weaver Client Secret | **Type** | Password field | | ------------ | -------------------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Language Weaver** | The client secret used alongside the Client Id to authenticate Aisera with the Language Weaver translation service. See also: [Language Weaver Client Id](#language-weaver-client-id) ## Intento ### Intento API Key | **Type** | Password field | | ------------ | ------------------------------------------------ | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Intento** | The API key used to authenticate Aisera with the Intento translation and language detection service. It is the only credential Intento requires. ## AWS Configure these fields to route AWS translation and language detection requests through your organization's own AWS account. If left unconfigured, Aisera uses its own platform-level AWS account. ### AWS ARN ROLE | **Type** | Text field | | ----------- | ------------------------------------------- | | **Default** | `arn:aws:iam:::role/aisera-api` | The AWS Identity and Access Management (IAM) Role ARN Aisera assumes when routing translation and language detection requests through your organization's AWS account. Configure this to use your own AWS Translate service rather than Aisera's shared platform account. {% hint style="warning" %} If both **AWS ARN ROLE** and **AWS S3 Region** are configured, Aisera routes both primary AWS translation and fallback translation requests through your AWS account. If either field is left empty, Aisera uses its own platform-level AWS account for those requests. {% endhint %} ### AWS S3 Region | **Type** | Text field | | ----------- | ----------- | | **Default** | `us-west-2` | The AWS region Aisera targets when routing translation and language detection requests through your organization's AWS account. Configure this alongside **AWS ARN ROLE** to direct requests to your preferred region. {% hint style="warning" %} If both **AWS ARN ROLE** and **AWS S3 Region** are configured, Aisera routes both primary AWS translation and fallback translation requests through your AWS account. If either field is left empty, Aisera uses its own platform-level AWS account for those requests. {% endhint %} {% hint style="info" %} Use standard AWS region identifiers, for example `eu-west-1` or `ap-southeast-1`. {% endhint %} See also: [AWS ARN ROLE](#aws-arn-role) ## Azure ### Azure API Key | **Type** | Password field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **AZURE** | The API key Aisera uses to authenticate with Microsoft Azure Cognitive Services for language detection and translation. Azure requires only this single credential. ## Google ### Google API Key | **Type** | Password field | | ------------ | ----------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **GOOGLE** | The API key Aisera uses to authenticate with Google Cloud Translation for language detection and translation. Google requires only this single credential. ## GeoFluent Both credential fields in this cluster must be configured together for the GeoFluent provider to function. ### GeoFluent API Key | **Type** | Password field | | ------------ | -------------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **GeoFluent** | The API key Aisera uses to authenticate with GeoFluent for language detection and translation. See also: [GeoFluent Secret Key](#geofluent-secret-key) ### GeoFluent Secret Key | **Type** | Password field | | ------------ | -------------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **GeoFluent** | The secret key Aisera uses alongside the GeoFluent API Key to authenticate with GeoFluent for language detection and translation. See also: [GeoFluent API Key](#geofluent-api-key) ## Cisco Translation All five credential fields in this cluster must be configured together for the Cisco Translation provider to function. ### Cisco Translation Auth Client Id | **Type** | Password field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Cisco** | The OAuth client ID Aisera uses to obtain access tokens from Cisco's authentication service for translation and language detection. See also: [Cisco Translation Auth Client Secret](#cisco-translation-auth-client-secret), [Cisco Translation Access Token URL](#cisco-translation-access-token-url), [Cisco Translation Base URL](#cisco-translation-base-url), [Cisco Translation Client Id (Header)](#cisco-translation-client-id-header) ### Cisco Translation Auth Client Secret | **Type** | Password field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Cisco** | The OAuth client secret Aisera uses alongside the Cisco Translation Auth Client Id to obtain access tokens from Cisco's authentication service. See also: [Cisco Translation Auth Client Id](#cisco-translation-auth-client-id), [Cisco Translation Access Token URL](#cisco-translation-access-token-url), [Cisco Translation Base URL](#cisco-translation-base-url), [Cisco Translation Client Id (Header)](#cisco-translation-client-id-header) ### Cisco Translation Access Token URL | **Type** | Text field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Cisco** | The endpoint URL Aisera calls to obtain OAuth access tokens from Cisco's authentication service. Aisera uses these tokens to authenticate all subsequent translation and detection requests. See also: [Cisco Translation Auth Client Id](#cisco-translation-auth-client-id), [Cisco Translation Auth Client Secret](#cisco-translation-auth-client-secret), [Cisco Translation Base URL](#cisco-translation-base-url), [Cisco Translation Client Id (Header)](#cisco-translation-client-id-header) ### Cisco Translation Base URL | **Type** | Text field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Cisco** | The base endpoint URL Aisera uses to send all translation and detection requests to the Cisco Translation service. See also: [Cisco Translation Auth Client Id](#cisco-translation-auth-client-id), [Cisco Translation Auth Client Secret](#cisco-translation-auth-client-secret), [Cisco Translation Access Token URL](#cisco-translation-access-token-url), [Cisco Translation Client Id (Header)](#cisco-translation-client-id-header) ### Cisco Translation Client Id (Header) | **Type** | Text field | | ------------ | ---------------------------------------------- | | **Default** | Not configured | | **Requires** | **Language Service Provider** set to **Cisco** | A client identifier Aisera sends as an HTTP request header when communicating with the Cisco Translation service. See also: [Cisco Translation Auth Client Id](#cisco-translation-auth-client-id), [Cisco Translation Auth Client Secret](#cisco-translation-auth-client-secret), [Cisco Translation Access Token URL](#cisco-translation-access-token-url), [Cisco Translation Base URL](#cisco-translation-base-url), [Cisco Translation Client Id (Header)](#cisco-translation-client-id-header) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/language-services.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.