ai contact center · published

Real-time translation in contact centers

Verified 2026-09-30 · 51 sources · tier 1–6

Also known as Translator Agent, chat message translation, real-time translation, transcript translation, voice-to-voice translation.

Contact center platforms handle real-time language translation through custom message-processing extensions, asynchronous post-interaction reviews, and emergent speech-to-speech architectures rather than universal built-in controls 303951. WarmTransfer's reading of the sources is that turnkey, vendor-managed real-time translation features remain absent from major native contact center suites for both voice and chat 16.

Amazon Connect

In Amazon Connect, message processing intercepts and modifies chat messages before they reach any participant 12. When enabled, every plaintext, markdown, and JSON chat message passes through the configured processor before delivery 8. AWS documentation names language translation via third-party services as a use case for custom message processor Lambdas, as translation is not offered as a built-in processing option alongside sensitive data redaction 30.

Chat architecture and Lambda lifecycle

A copy of each chat message is delivered to the custom processor Lambda, and if a valid response returns within the configured timeout, that response becomes the canonical form of the message 7. The returned content replaces the original message when published to chat participants 21. Amazon Connect honors the configured timeout between 3 seconds and 3 minutes 13.

The custom processor Lambda must return a status of PROCESSED, APPROVED, or REJECTED, providing processed content formatted as text/plain, text/markdown, or application/json 22. The delivered event carries a chatContent object containing content, contentType, participantId, displayName, participantRole, contactId, and initialContactId, but lacks a language field 9. Because the documented event carries participant role but no language, WarmTransfer's reading of the sources is that a translation Lambda must determine source and target languages independently via language detection or contact data lookups 14.

Message processing remains active for the full duration of the chat across transfers, but it does not retroactively process messages sent prior to activation 17. When both built-in redaction and a custom message processor are active, redaction output becomes the input for the custom processor 19. Processed chat messages replace originals in the Amazon S3 chat transcripts folder, while unprocessed original transcripts reside in a separate S3 folder with a path prefix starting with Unprocessed 23.

Configuration and failures

A custom processor Lambda must first be associated with the instance under the use case "Custom processor lambda" or through CreateIntegrationAssociation using an integration type of MESSAGE_PROCESSOR 20. Activation occurs either through the "Set recording, analytics and processing behavior" flow block using "Set message processor" for the "Chat" channel, or by calling the StartContactMediaProcessing API 1. The StartContactMediaProcessing and StopContactMediaProcessing APIs apply only to custom message processors; built-in redaction is configured exclusively via flow blocks 2.

If processing fails, administrator configuration controls whether the unprocessed message is delivered or suppressed 10. The StartContactMediaProcessing API FailureMode parameter accepts either DELIVER_UNPROCESSED_MESSAGE or DO_NOT_DELIVER_UNPROCESSED_MESSAGE 3. An AWS Contact Center blog post advises falling back to the original message if translation fails 5.

Multilingual capabilities and sample projects

Amazon Connect chat provides full Unicode support, allowing chat message content in any language 24. Quick responses for chat and email are available in English 18. As of 2026-09-30, the "Languages supported by Connect Customer features" documentation contains no section or table column for a translation feature 15.

When paired with Amazon Translate, 75 language entries are supported, counting regional variants such as French (Canada), Spanish (Mexico), Portuguese (Portugal), and Chinese (Traditional) separately 28. Amazon Translate may charge for automatic language detection when the source language is set to auto, but does not charge when source and target languages match 29. An AWS Contact Center blog post published on 20 July 2026 outlines a chat solution calling Amazon Translate bi-directionally, citing design targets of under 1 second of translation latency per message, a success rate above 99 percent, and a recommendation of 512 MB of Lambda memory 46.

For voice interactions, the aws-samples voice-to-voice translation project chains Amazon Transcribe, Amazon Polly, and Amazon Translate in both directions 26. The project repository README notes it is a sample not meant for production environments 26. It transcribes agent and customer audio locally from the agent's browser across 2 websocket connections to Amazon Transcribe, requiring verification of agent PC performance and network bandwidth 25. Furthermore, the sample project has not been tested with outbound calls, conferences, transfers, or cross-channel tasks like chat or email 27.

Genesys Cloud

Genesys Cloud provides on-demand transcript translation on the Interaction Details page when a transcription exists, requiring the Speech and Text Analytics > Translation > View permission 39. This service relies on AWS Translate, following the Amazon Translate supported languages list 40.

Genesys Cloud transcript translation is limited to 1,000 translations per organization per day 38.

Feature Dimension	Platform Rule
Daily Translation Limit	1,000 translations per organization per day 38
Text Coverage	Approximately the first 10,000 characters for digital interactions 36
Result Caching	Translated text is cached for up to 20 hours 35

When viewing a translated transcript, a label at the top of the panel indicates the source dialect and selected target dialect 37.

For live digital messaging, Genesys provides the Digital Messaging Translator, an MIT-licensed developer blueprint utilizing AWS Translate to translate messaging interactions in the agent's panel in real time, including canned responses 31. In the field, a July 2023 Genesys Community respondent noted that chat translation could be accomplished via the AppFoundry translation blueprint while characterizing voice translation as part of future AI plans 32.

Cisco Webex

Cisco announced Translator Agent for Webex Calling in a Webex Blog post updated 18 February 2026, describing real-time, bi-directional speech-to-speech translation preserving caller tone and emotion 51. Translator Agent was announced for launch across 10 languages: English, French, German, Hindi, Italian, Japanese, Korean, Mandarin, Portuguese, and Spanish 49. The announcement projected availability in the first half of 2026 for Webex Calling, with Webex Meetings and Webex Contact Center support to follow, stating no date for Contact Center 48.

A Webex Contact Center update on 18 June 2026 expanded AI Assistant support to 15 languages in General Availability and 13 in Controlled Availability for Real-time Transcripts, Summaries, Real-time Assist, Auto CSAT, and Wellness Breaks, though none of these features perform translation 44. In Webex Meetings and Webinars, real-time translation converts spoken dialogue into text captions across more than 120 caption languages with a paid Real-time translation add-on license 47. A meeting or webinar can display at most 15 unique caption languages concurrently 46.

Regulatory and Healthcare Review Standards

Under 45 CFR 92.201(c)(3), a covered healthcare entity using machine translation must have translations reviewed by a qualified human translator when text is critical to rights, benefits, or meaningful access for individuals with limited English proficiency 42. Human review is also mandated when accuracy is essential or when source text includes complex, technical, or non-literal terminology 42.

Applicability

Applies to: Amazon Web Services Amazon Connect, Amazon Web Services Amazon Translate, Genesys Cloud, Cisco Webex Calling, Cisco Webex Contact Center, Cisco Webex Meetings, and US HHS Section 1557 nondiscrimination rule. Deployments: multi-tenant and not-applicable. Sources checked 2026-09-30. Amazon Connect message processing is not available in the AWS GovCloud (US-West) Region 11. The documented input event format delivered to the Amazon Connect custom processor Lambda has no language field 9. Webex real-time caption translation requires the paid Real-time translation add-on license 47. The human review rules for machine translation under 45 CFR 92.201(c)(3) apply to covered health programs and activities in the United States 42.

What remains uncertain

The release date and documentation for Translator Agent in Webex Contact Center are not covered by the sources below. The shipped status, administrative setup, and licensing details for Translator Agent in Webex Calling are not covered by the sources below. Real-time translation on Webex Contact Center digital channels through Webex Connect or Webex Engage is not covered by the sources below. The measured accuracy of machine translation and speech translation in contact center environments is not covered by the sources below. End-to-end latency benchmarks of voice-to-voice translation on live calls are not covered by the sources below. Transparency obligations under the EU AI Act regarding AI translation and synthetic voices are not covered by the sources below. Whether Amazon Connect message processing covers SMS, WhatsApp, and Apple Messages contacts is not covered by the sources below. United States disclosure and consent requirements for AI-generated or AI-translated voice on calls are not covered by the sources below.

Sources

1
A custom message processor in Amazon Connect is activated either with the 'Set recording, analytics and processing behavior' flow block, using the action 'Set message processor' with channel 'Chat', or by calling the StartContactMediaProcessing API.
Enable in-flight sensitive data redaction and message processing · section 'Step 3: Activate your Lambda function', Option 1 and Option 2 · Checked 2026-09-30
2
The StartContactMediaProcessing and StopContactMediaProcessing APIs apply only to custom message processors; built-in redaction is configured exclusively through the flow block.
Enable in-flight sensitive data redaction and message processing · section 'Configure message processing', Note · Checked 2026-09-30
3
The StartContactMediaProcessing API's FailureMode parameter accepts DELIVER_UNPROCESSED_MESSAGE or DO_NOT_DELIVER_UNPROCESSED_MESSAGE.
StartContactMediaProcessing · section 'Request Body', parameter FailureMode, Valid Values · Checked 2026-09-30
4
An AWS Contact Center blog post dated 20 July 2026 describes a chat translation solution in which a custom processor Lambda on Amazon Connect message processing detects the customer's language and calls Amazon Translate in both directions.
Breaking Language Barriers: Real-Time Multilingual Support with Amazon Connect Chat Message Processing · solution overview / message flow description · Checked 2026-09-30
5
The AWS blog post on chat translation advises implementing a fallback to the original message if translation fails.
Breaking Language Barriers: Real-Time Multilingual Support with Amazon Connect Chat Message Processing · best practices section, 'Error Handling' · Checked 2026-09-30
6
The AWS blog post on chat translation states design targets of under one second of translation latency per message and a success rate above 99 percent, and recommends 512 MB of Lambda memory; these are stated targets, not published measurements.
Breaking Language Barriers: Real-Time Multilingual Support with Amazon Connect Chat Message Processing · best practices / performance guidance section · Checked 2026-09-30
7
A copy of each chat message is sent to the custom processor Lambda, and if a valid response is received within the timeout, the content of that response becomes the new canonical form of the message.
Enable in-flight sensitive data redaction and message processing · section 'Processing options', 'Custom message processors (through Lambda)' · Checked 2026-09-30
8
When message processing is enabled in Amazon Connect, every plaintext, markdown and JSON chat message passes through the configured processor before delivery to participants.
Enable in-flight sensitive data redaction and message processing · section 'How it works', first paragraph · Checked 2026-09-30
9
The input event delivered to the Amazon Connect custom processor Lambda carries a chatContent object with content, contentType, participantId, displayName, participantRole, contactId and initialContactId; the documented event format has no language field.
Enable in-flight sensitive data redaction and message processing · section 'Step 1: Create your Lambda function', input event code block · Checked 2026-09-30
10
If message processing fails in Amazon Connect, the administrator's configuration decides whether the original unprocessed message is delivered or suppressed.
Enable in-flight sensitive data redaction and message processing · section 'How it works', first paragraph; section 'Step 3: Activate your Lambda function', item 5 'Processing failure handling' · Checked 2026-09-30
11
Amazon Connect message processing is not available in the AWS GovCloud (US-West) Region.
Enable in-flight sensitive data redaction and message processing · section 'Important considerations', last bullet · Checked 2026-09-30
12
Amazon Connect message processing intercepts and modifies chat messages before they reach any participant.
Enable in-flight sensitive data redaction and message processing · introductory paragraph under the page title · Checked 2026-09-30
13
Amazon Connect honors the custom processor Lambda function's configured timeout, which must be between 3 seconds and 3 minutes.
Enable in-flight sensitive data redaction and message processing · section 'Step 1: Create your Lambda function', Note · Checked 2026-09-30
14
Because the documented processor event carries participant role but no language, a translation Lambda on Amazon Connect has to determine source and target languages itself, for example by language detection or by its own lookup of contact data.inferred
Enable in-flight sensitive data redaction and message processing · section 'Step 1: Create your Lambda function', input event code block · Checked 2026-09-30
15
As of 2026-09-30 the Amazon Connect 'Languages supported by Connect Customer features' page has no section or table column for a translation feature; its sections cover AI features, Contact Control Panel, chat message content, quick responses, admin website, Cases, forecasting and scheduling, Amazon Lex and Amazon Polly.
Languages supported by Connect Customer features · Topics list at the top of the page; column headers of the 'AI features' table · Checked 2026-09-30
16
Amazon Connect's documentation reviewed on 2026-09-30 shows no turnkey, vendor-managed real-time translation feature for either chat or voice: chat translation is a customer-supplied Lambda on the message processing hook, and voice translation appears only as a sample project.inferred
Languages supported by Connect Customer features · Topics list at the top of the page (absence of any translation feature) · Checked 2026-09-30
17
Amazon Connect message processing stays active for the entire duration of the chat, including across a transfer when an individual contact segment ends, and it does not retroactively process messages sent before it was enabled.
Enable in-flight sensitive data redaction and message processing · section 'How it works', second paragraph; section 'Important considerations' · Checked 2026-09-30
18
Amazon Connect quick responses for chat and email contacts are available in English.
Languages supported by Connect Customer features · section 'Quick responses' · Checked 2026-09-30
19
When built-in redaction and a custom message processor are both enabled in Amazon Connect, the output of redaction becomes the input for the custom processor.
Enable in-flight sensitive data redaction and message processing · section 'How it works', Note · Checked 2026-09-30
20
Before a custom processor Lambda can be used, it must be added to the Amazon Connect instance with the use case 'Custom processor lambda', or associated through CreateIntegrationAssociation with IntegrationType MESSAGE_PROCESSOR.
Enable in-flight sensitive data redaction and message processing · section 'Create a custom message processor', 'Add the Lambda function to your instance first'; section 'Step 2' · Checked 2026-09-30
21
The processed content returned by the custom processor Lambda replaces the original message when it is published to chat participants.
Enable in-flight sensitive data redaction and message processing · section 'Step 1: Create your Lambda function', sentence after the response format · Checked 2026-09-30
22
The Amazon Connect custom processor Lambda must return a status of PROCESSED, APPROVED or REJECTED, with processed content of type text/plain, text/markdown or application/json.
Enable in-flight sensitive data redaction and message processing · section 'Step 1: Create your Lambda function', response format code block · Checked 2026-09-30
23
With Amazon Connect message processing, processed chat messages replace the originals in the S3 chat transcripts folder, and the unprocessed original transcript is stored in a separate S3 folder whose path prefix begins with 'Unprocessed'.
Enable in-flight sensitive data redaction and message processing · section 'Additional information', 'Transcript storage' · Checked 2026-09-30
24
Amazon Connect chat provides full Unicode support, so chat message content can be in any language.
Languages supported by Connect Customer features · section 'Chat message content' · Checked 2026-09-30
25
In the aws-samples voice-to-voice translation project, both agent and customer audio are transcribed locally from the agent's browser over two websocket connections to Amazon Transcribe, so the README says agent PC performance and network bandwidth need to be checked.
aws-samples/connect-v2v-translation-with-cx-options · README, 'Key limitations' · Checked 2026-09-30
26
The aws-samples voice-to-voice translation project for Amazon Connect chains Amazon Transcribe, Amazon Translate and Amazon Polly in both directions, and its README says it is a sample project not meant to be used in production environments.
aws-samples/connect-v2v-translation-with-cx-options · README, solution description and 'Key limitations' · Checked 2026-09-30
27
The aws-samples voice-to-voice translation project's README says it has not been tested with outbound calls, conference or transfers, nor in combination with other channels such as chat, tasks or email.
aws-samples/connect-v2v-translation-with-cx-options · README, 'Key limitations' · Checked 2026-09-30
28
The Amazon Translate supported-languages table lists 75 language entries, counting regional variants such as French (Canada), Spanish (Mexico), Portuguese (Portugal) and Chinese (Traditional) as separate entries.
Supported languages and language codes · section 'Supported languages', table · Checked 2026-09-30
29
Amazon Translate may charge for automatic language detection when the source language is set to auto, and does not charge for a translation when source and target language are the same.
Supported languages and language codes · Note under the introductory paragraph · Checked 2026-09-30
30
AWS documentation names language translation through third-party services as a use case for a custom message processor Lambda in Amazon Connect chat; translation is not offered as a built-in processing option alongside built-in sensitive data redaction.
Enable in-flight sensitive data redaction and message processing · section 'Processing options', 'Custom message processors (through Lambda)' use-case list · Checked 2026-09-30
31
Genesys publishes an MIT-licensed developer blueprint, the Digital Messaging Translator, that uses the AWS Translate service to translate messaging interactions in the agent's Interactions panel in real time, including canned responses.
GenesysCloudBlueprints/digital-messaging-translator-blueprint · README, opening description · Checked 2026-09-30
32
In a July 2023 Genesys Community thread, a respondent said chat translation could be done then with the AppFoundry translation blueprint and described voice translation as part of future AI plans.field report
Question: does real-time translation exist today · replies to the original post of July 26, 2023 · Checked 2026-09-30
33
In the Genesys Cloud sources reviewed on 2026-09-30, the only vendor-documented native translation is after-the-fact transcript translation for reviewers; live agent-facing translation of messaging is available through a customer-deployed blueprint or third-party apps rather than a documented native feature.inferred
Work with a digital transcript · transcript translation section (scope: Interaction Details page) · Checked 2026-09-30
34
The Genesys Cloud 'Features coming soon' page for the 28 September 2026 release, as retrieved on 2026-09-30, listed no translation feature.
Genesys Cloud - Features coming soon · whole page (feature list) · Checked 2026-09-30
35
After an initial Genesys Cloud transcript translation, the translated text is cached for up to 20 hours.
Work with a digital transcript · transcript translation section, notes · Checked 2026-09-30
36
For digital interactions, Genesys Cloud transcript translation covers only approximately the first 10,000 characters.
Work with a digital transcript · transcript translation section, notes · Checked 2026-09-30
37
While a Genesys Cloud transcript is shown translated, a label at the top of the transcript panel states the source dialect and the selected target dialect.
Work with a digital transcript · transcript translation section, procedure · Checked 2026-09-30
38
Genesys Cloud transcript translation is limited to 1,000 translations per organization per day.
Work with a digital transcript · transcript translation section, notes · Checked 2026-09-30
39
Genesys Cloud offers on-demand transcript translation on the Interaction Details page when a transcription is present, and it requires the Speech and Text Analytics > Translation > View permission.
Work with a digital transcript · transcript translation section (permission note and procedure) · Checked 2026-09-30
40
Genesys Cloud's on-demand transcript translation comes from AWS Translate, and its language availability follows the Amazon Translate supported languages list.
Genesys Cloud supported languages · accordion section 'Transcript translation' · Checked 2026-09-30
41
Under 45 CFR 92.201(g), a covered entity that provides a qualified interpreter through audio remote interpreting must deliver real-time audio over a dedicated high-speed connection with clear, audible transmission of voices, and provide adequate user training.
45 CFR § 92.201 - Meaningful access for individuals with limited English proficiency · 45 CFR 92.201(g) · Checked 2026-09-30
42
Under 45 CFR 92.201(c)(3), a covered entity that uses machine translation must have the translation reviewed by a qualified human translator when the underlying text is critical to the rights, benefits or meaningful access of an individual with limited English proficiency, when accuracy is essential, or when the source material contains complex, non-literal or technical language.
45 CFR § 92.201 - Meaningful access for individuals with limited English proficiency · 45 CFR 92.201(c)(3) · Checked 2026-09-30
43
The 'Languages supported by Cisco AI Assistant' article covers Webex Suite message translation, Webex Meetings, Webex Calling and Devices, and as retrieved on 2026-09-30 it lists no translation feature for Webex Contact Center.
Languages supported by Cisco AI Assistant · product section headings · Checked 2026-09-30
44
A Webex Contact Center agents' what's-new entry dated 18 June 2026 says AI Assistant language support expanded to 15 languages in General Availability and 13 in Controlled Availability for Real-time Transcripts, Summaries, Real-time Assist, Auto CSAT and Wellness Breaks; none of those features is translation.
What's new for agents in Webex Contact Center · entry dated June 18, 2026, 'Expanded Global Language Support for AI Assistants' · Checked 2026-09-30
45
As retrieved on 2026-09-30, the 'What's new for administrators in Webex Contact Center' page, whose latest entry was dated 30 September 2026, contained no entry for Translator Agent, real-time translation or translated transcripts.
What's new for administrators in Webex Contact Center · whole page (no translation entry); latest entry dated September 30, 2026 · Checked 2026-09-30
46
A Webex meeting or webinar can use at most 15 unique caption languages at the same time.
Show real-time translation and transcription in meetings and webinars · limitations note · Checked 2026-09-30
47
Webex real-time translation in Meetings and Webinars translates a speaker's speech into text captions, offers more than 120 caption languages, and requires a paid Real-time translation add-on license.
Show real-time translation and transcription in meetings and webinars · overview and licensing note · Checked 2026-09-30
48
The Webex Blog announcement says Translator Agent would be available in the first half of 2026 for Webex Calling, with Webex Meetings and Webex Contact Center support to follow, and gives no date for Contact Center.
Translator Agent for Webex Calling: Bridging Language Barriers to Connect Customers Worldwide · paragraph on supported languages and availability · Checked 2026-09-30
49
The Webex Blog announcement lists ten languages for Translator Agent at launch: English, French, German, Hindi, Italian, Japanese, Korean, Mandarin, Portuguese and Spanish, with more described as coming later.
Translator Agent for Webex Calling: Bridging Language Barriers to Connect Customers Worldwide · paragraph on supported languages and availability · Checked 2026-09-30
50
Whether Translator Agent actually became available in Webex Calling in the first half of 2026 is unresolved: the February 2026 blog forecast it, but the 'What's new in Webex Calling' page retrieved on 2026-09-30 showed no Translator Agent or call translation entry.disputed
What's new in Webex Calling · whole page (no Translator Agent entry among 2024-2026 entries) · Checked 2026-09-30
51
Cisco announced Translator Agent for Webex Calling in a Webex Blog post dated 10 February 2026 and updated 18 February 2026, describing it as real-time, bi-directional speech-to-speech translation that preserves the caller's tone and emotion.
Translator Agent for Webex Calling: Bridging Language Barriers to Connect Customers Worldwide · opening paragraphs describing Translator Agent · Checked 2026-09-30

Documents

tier 1 standards and regulators

Cite this page

APA

WarmTransfer. (2026, September 30). Real-time translation in contact centers. WarmTransfer. https://warmtransfer.net/knowledge/real-time-translation-contact-center

BibTeX

@misc{warmtransfer-real-time-translation-contact-center,
  title  = {Real-time translation in contact centers},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/real-time-translation-contact-center},
  note   = {Verified 2026-09-30}
}