Real-time call translation for Amazon Connect calls.
52 languages, both directions, on the Connect call itself — from US$300 a session. The caller speaks their language, your agent speaks English, and each hears their own — translated live, on the call. One monolingual team, every caller served. Where data residency matters, the whole speech path can run onshore in Australia.
Available on AWS MarketplaceLive Interpreter for Amazon Connect — by LiveUCX
Real-time call translation · Runs on your own Amazon Connect instance · Two-way, live on the call · Onshore Australian speech path available
A live-translation layer for organisations running Amazon Connect, with a choice of speech and AI providers — Deepgram and Azure AI give a fully onshore Australian path where residency matters.
A monolingual agent serves a caller in another language — each hears their own, translated live on the call.
Translation runs on the live call in both directions, so it's a real conversation — not a form to fill in or a callback to schedule.
Speech recognition and synthesis can run entirely on Australian endpoints, so the language data never has to leave the country.
One call, two languages
Serving callers in many languages usually means hiring for each one, or bridging in a third-party interpreter and waiting on the line while everyone gets connected — slow, costly, and hard to staff. Live Interpreter translates the call itself, live and two-way, so a single English-speaking team can talk to a caller in their own language, on the same call, without a separate interpreter line. What that actually requires — latency, data residency, and where a certified interpreter is still the right answer — is set out in real-time call translation in Amazon Connect.
Vi: “Tôi cần đặt lại lịch hẹn.” — detected: Vietnamese
“I need to reschedule my appointment.” — translated live
The caller hears the reply back in Vietnamese — both languages shown side by side in the panel.
Live translation, on the Amazon Connect call
A caller reaches your Amazon Connect contact centre and is routed to an available agent, exactly as they are today — no separate interpreter line to dial.
Live Interpreter joins as a participant on the same Connect contact, so the call stays a routed Connect contact end to end — recording, analytics and reporting all still apply.
The caller's speech is transcribed and translated into English for the agent, and the agent's English is translated back into the caller's language — a full two-way exchange.
Synthesised speech plays back on the call so the caller hears their own language and the agent hears English, with the two sides kept cleanly crossed.
A live panel shows the conversation in both languages side by side, so the agent, a bilingual supervisor or the caller can sanity-check the translation as it happens.
Real-time, two-way translation on the live call; runs on your own Amazon Connect instance; the call stays a single routed Connect contact; onshore Australian speech recognition and synthesis available; a bilingual transcript shown to the agent for trust; one monolingual team can serve callers in many languages; no separate interpreter line to dial or wait on. Language coverage and the exact speech path are confirmed with you during onboarding.
Onshore where it counts — no forced offshore hop
Most live-translation offerings route your callers' speech through whichever cloud region the vendor happens to run in. For Australian government, health and financial-services buyers that is often the end of the conversation. Live Interpreter can run speech recognition and speech synthesis on Australian endpoints, so the language data stays in the country — and your Amazon Connect instance, recordings and reporting never leave your own AWS account and region.
Australian speech recognition and synthesis endpoints, so caller audio and transcripts stay in-country.
The call remains a routed contact on your own Amazon Connect instance — recordings and reporting stay in your AWS account.
Speech and language providers are configurable, so residency, quality and cost can be balanced for your use case rather than ours.
Already running one of our Amazon Connect CRM connectors for Dynamics 365, HubSpot or Pipedrive? Live Interpreter sits alongside the same agent workspace and the same Connect contact.
What Live Interpreter does
Translates a live contact-centre call as it happens, so agent and caller can actually converse across a language gap.
Caller-to-agent and agent-to-caller, crossed cleanly so each party hears only their own language.
Joins the same Connect contact as the caller and agent — no separate interpreter line and no separate app to babysit.
Speech recognition and synthesis can run on Australian endpoints, keeping caller audio and transcripts in-country.
Detects the caller's language from their first utterance and selects the right translation pair.
Shows the conversation in both languages side by side, so the agent, a bilingual supervisor — or the caller — can catch a mistranslation.
Because the call stays a routed Connect contact, recording, analytics and reporting work exactly as they do today.
Sits alongside the ProUCX connectors for Dynamics 365, HubSpot and Pipedrive on the same Connect contact.
Machine translation is not a certified human interpreter
We keep this caveat front and centre rather than bury it. Live Interpreter is built for everyday service conversations — appointments, accounts, enquiries, status updates — where speed and coverage matter more than certification. It shows both languages side by side precisely so mistakes can be caught in the moment. For legal proceedings, clinical consent, or anywhere a certified interpreter is required by law or policy, use a certified interpreter. If you're not sure which side of that line your calls sit on, talk to us and we'll tell you honestly.
Amazon Connect already speaks 50 languages. Isn’t that the same thing?
It is a fair question and it comes up in nearly every conversation, because AWS has shipped a great deal of multilingual capability in the last year. The short answer is that those features make the machine multilingual. Interpretation is about the moment a caller reaches a person who does not share their language — and that is a different problem. Here is each capability and what it actually covers.
Amazon Connect’s agentic voice speaks more than fifty languages, with Australian English among the locales added during 2026. If a caller’s whole enquiry can be handled by self-service in their own language, this is the cheaper and simpler answer and you should use it.
The moment that AI agent escalates, the caller reaches a person who speaks one language. The language barrier does not appear during the self-service part of the call — it appears at the hand-off, which is also the point at which the enquiry has already proven too complex for automation.
Amazon Q can give an agent knowledge articles and guidance in the agent’s own language. That helps the agent read. It does not translate what the caller is saying, or what the agent says back.
AWS publishes an approach for live chat translation using Amazon Translate, available as an open-source solution from a partner. It is a good pattern and it works — for chat. Text arrives as text, with no speech recognition, no turn-taking and no latency budget measured in hundreds of milliseconds.
That is the case this product addresses: a caller speaking one language and an agent speaking another, on a live voice call, both hearing the other in their own language without a third party dialled into the conversation.
If the work can be automated, a multilingual AI agent is the better buy and we will say so. If your people need to speak to callers they currently cannot serve, that is when this becomes the question worth asking.
AWS documents the multilingual agentic voice capability in its agentic voice guide, and the chat translation pattern on the AWS machine learning blog. For what the technology demands either way, see what real-time translation actually requires.
Which languages Live Interpreter supports
Fifty-two languages, in both directions. That figure is an intersection rather than a headline. A language is only offered when all three steps of the chain work for it — recognising what the caller said, translating it, and speaking it back in a natural voice. It is easy to advertise the longest list that any single one of those steps supports; this is the list where all three do. Counts were last verified in August 2026, and vendor language support moves quickly enough that it is worth asking us to confirm a specific language before you commit to it.
The 52: Arabic, Armenian, Bengali, Bosnian, Bulgarian, Cantonese, Catalan, Chinese (Mandarin), Croatian, Czech, Danish, Dutch, English, Estonian, Filipino (Tagalog), Finnish, French, German, Greek, Gujarati, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Kannada, Korean, Latvian, Lithuanian, Macedonian, Malay, Marathi, Norwegian, Persian (Farsi and Dari), Polish, Portuguese, Punjabi, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Tamil, Telugu, Thai, Turkish, Ukrainian, Urdu and Vietnamese.
Twenty-three run entirely on AWS services, with no third-party voice anywhere in the path: Arabic, Cantonese, Catalan, Chinese (Mandarin), Czech, Danish, Dutch, English, Finnish, French, German, Hindi, Italian, Japanese, Korean, Norwegian, Polish, Portuguese, Romanian, Russian, Spanish, Swedish and Turkish. For the remaining 29, Amazon Polly has no voice available, so the spoken side uses an Azure AI neural voice instead.
What we cannot do yet, and why. Malayalam, Swahili, Amharic and Sinhala all fail at the first step: there is no speech-recognition model available to us that covers them, so the caller cannot be heard reliably — and a translation of a bad transcript is worse than no translation. Nepali fails at a different step, with speech recognition available but no machine translation. These are awkward gaps for Australian contact centres and we would rather name them here than have you find them after signing. Sri Lankan Tamil speakers are covered, through Tamil.
Live Interpreter questions
Live Interpreter for Amazon Connect is listed on AWS Marketplace, so you can subscribe against the AWS account you already have. You can also book a briefing and we'll walk through language coverage and residency for your contact centre.
It adds real-time, two-way translation to a live contact-centre call: a caller speaking one language and a monolingual agent speaking another hold a conversation, each hearing their own language, translated live — so one English-speaking team can serve callers in many languages without a separate interpreter line.
Amazon Connect. Live Interpreter joins the same Connect contact as the caller and the agent, so the call stays a single routed contact and your recording, analytics and reporting continue to apply.
Yes. Speech recognition and speech synthesis can both run on Australian endpoints, which is the configuration we recommend for government, health and financial-services buyers. Confirm your specific language pairs with us during onboarding — onshore coverage is very good but not universal across every language.
No, and we won't claim otherwise. Machine translation is built for speed and coverage on everyday service conversations, not for certification. Live Interpreter shows both languages side by side so errors can be caught in the moment. Where a certified interpreter is required by law or policy, use one.
They're the same platform doing two different jobs. Live AI Agent replaces the agent on the call; Live Interpreter sits between a human agent and the caller and translates. They are complementary rather than alternatives.
Not between a human agent and a human caller on a voice call. Amazon Connect ships multilingual AI agents that speak the caller’s language during self-service, agent-assist in many languages, and a documented pattern for translating live chat using Amazon Translate. Live voice interpretation between two people is the part that is not a native feature.
Because the AI agent covers the automated part of the call. When the enquiry is complex enough to need a person — which is precisely when it matters most — the caller is handed to an agent who speaks one language. Interpretation addresses that hand-off, not the self-service that precedes it.
No, and the difference is most of the engineering. Chat arrives as text, so there is no speech recognition, no speaker turn-taking to manage and no latency budget measured in hundreds of milliseconds. Voice has all three, which is why a chat translation pattern does not extend to a phone call.
Whenever the enquiry can genuinely be completed without a person. Checking a balance, tracking an order, booking or changing an appointment — if an AI agent can finish the job in the caller’s language, that is cheaper and simpler than putting an interpreter in the path, and we would rather tell you that than sell you something you do not need.
Fifty-two, in both directions. A language is only counted when every step works for it — recognising the caller’s speech, translating it, and speaking it back — so the number is the intersection of all three rather than the largest figure we could quote. Twenty-three of the 52 run entirely on AWS services. Last verified August 2026.
Yes, for all 52. The caller is heard and answered in their own language while your agent hears and speaks English, both on the same Amazon Connect call. It is not a one-way transcript or a summary after the fact.
Malayalam, Swahili, Amharic and Sinhala, because no speech-recognition model available to us covers them, so the caller cannot be heard reliably. Nepali is missing for a different reason — the speech side works but the translation step does not support it. Sri Lankan Tamil speakers are covered, through Tamil.
Yes, all five, in both directions. Cantonese is treated as a distinct spoken language rather than folded into Mandarin. Mandarin, Cantonese and Arabic sit in the subset that runs entirely on AWS services, while Vietnamese and Urdu use an Azure AI neural voice because Amazon Polly has none for them.
US$300 per interpreted session on AWS Marketplace, subscribed against the AWS account you already have, with one, five and twenty-session bundles available — check the listing for current bundle sizes and terms. Amazon Connect telephony and service charges are billed separately by AWS at your region’s published rates, exactly as they are for a call no one translates.
Serve every caller, with the team you already have
Subscribe on AWS Marketplace and bill it to the AWS account you already have, or book a briefing and we'll walk through the language coverage and residency options for your contact centre.