Which platforms offer live translated captions for external business guests?

An external client joining a product demonstration does not care that an administrator can see “translated captions” on a feature list. They care whether their own meeting window offers the right caption language when the presenter starts talking. That is a narrower question than which platform translates best. The answer depends on the host’s entitlement, the meeting’s settings, the guest’s joining route, and sometimes the guest’s own license. Being admitted to a meeting is not itself proof that translation is available.

Short answer: Zoom documents host-configured translated captions that participants and webinar attendees can use when the feature is enabled. Microsoft Teams documents an organizer-license path under which all meeting participants can use translated captions, alongside a different path limited to individually licensed participants. Google Meet documents translated captions on specified Workspace editions and allows external participants on its business editions, but its translated-caption help page does not spell out every unlicensed external guest entitlement; test the exact host and guest combination. OllaSync publicly describes individual caption-language selection in meetings and a Free plan with translated captions, but its public materials do not explicitly guarantee every no-account, external-organization joining route. Rehearse that route rather than promising frictionless access. These are live text captions, not automatically translated speech.

This article addresses an external-person workflow: a seller invites a customer, partner, supplier, investor, or candidate who is not managed by the host’s organization. It is not a translation-accuracy ranking, an audio-interpretation comparison, or a capacity calculation for a 100-person meeting. The existing general live-translation comparison, real-time audio guide, and 100-person multilingual meeting comparison address those different questions. Here the unit of analysis is one actual external invitee’s access to a translated-caption control. Vendor documentation and OllaSync’s public product descriptions were checked on November 10, 2026. Verify current availability, contract terms, and regional settings before a consequential meeting.

What “available to a guest” must mean

There are at least four separate gates. First, the person must be able to join under the organizer’s lobby, authentication, domain, and external-access policies. Second, the meeting must offer live captions and the host or administrator must have enabled the translation feature. Third, the guest must be entitled to select a target language in their own interface, rather than only seeing the host’s language. Fourth, the source and target languages must work for the actual conversation and device. Failure at any gate makes a marketing feature irrelevant to that guest. A vendor might document the third gate clearly while leaving the fourth dependent on a supported-language list and an up-to-date client.

Translated captions convert recognized speech into written text in another language. They are not a separate audio track, a certified interpreter, an automatically localized recording, or a guarantee that every word survives cross-talk. Ordinary same-language captions are useful but do not answer the translation question. A guest seeing a “Captions” button is not enough: ask them to choose a different target language and read the result while someone speaks. If the person must listen without reading a screen, scope that as an audio-translation or human-interpretation procurement instead.

For external meetings, the most useful procurement question is therefore not “Does the app have translation?” It is: If our licensed organizer schedules this exact kind of meeting and an unlicensed person from another company joins by this route, can that person personally turn on translated captions in the required language? Get the answer in a vendor document or contract, then verify it in the guest’s session. Organizers should not accidentally conduct the rehearsal while signed into their own tenant and mistake their entitlement for the invitee’s.

External-guest decision matrix

This matrix separates published claims from cases requiring validation. “Unconfirmed” means the cited public material is insufficient for the precise guest scenario, not that the product lacks the feature. The links lead to primary vendor documentation or OllaSync’s own published product pages, not third-party pricing roundups.

Platform	Published translation and entitlement evidence	External invitee implication	What remains to verify
Zoom	Zoom’s translated-captions explanation says the feature is included in certain named plans or sold as an add-on for paid accounts; captions follow the host’s settings, and, when enabled, participants and webinar attendees can use them.	The documented path is host-configured availability, not a requirement that each attendee buy the feature.	Confirm the actual host account, meeting/webinar setting, supported language, guest client, and any account or sign-in restrictions on the meeting.
Microsoft Teams	Microsoft’s live-captions instructions say that when the meeting organizer has Teams Premium or eligible Microsoft Copilot licensing, all meeting participants can use translated captions without that specific license. Otherwise only individually licensed participants see Translate to.	Organizer entitlement can be decisive for an external participant; a license assigned to an internal attendee is not equivalent to an eligible organizer.	Confirm the organizer identity and license, guest’s admitted join path, meeting type, tenant policy, and whether the guest actually sees Translate to.
Google Meet	Google’s translated-captions help lists eligible Workspace editions and the participant-facing caption settings; its edition matrix marks external participants supported on business editions.	External joining and edition-level feature availability are documented separately. The cited caption article does not explicitly resolve every anonymous or cross-tenant entitlement combination.	Confirm host’s edition, administrator settings, target language rollout, guest identity and browser, and whether that guest can select Translated captions.
OllaSync	Published pricing lists translated captions on Free, Pro, and Business; the live-translation feature description says each participant chooses captions in a shipped language for a meeting.	The product describes per-person selection rather than a caption language fixed for the whole room.	Public pages do not specify every external/no-account access rule. Confirm invitation, login requirement, E2EE setting, live-language limit, and the guest’s actual caption controls.

This is deliberately not a “free guest everywhere” chart. The host-side translation entitlement is clearer in Zoom’s and Teams’ published explanations than the exact anonymous-guest entitlement in the cited Meet and OllaSync pages. Even where a vendor says “all participants,” an organizer may disable external joining, require sign-in, block an untrusted domain, or use a client on which the feature does not behave as expected. Ask which meeting type the rule covers: an ordinary interactive meeting, a webinar, and a town hall need not share the same controls. The table does not infer those rules from a similarly named feature.

Zoom: check the host’s configuration, then the guest’s menu

Zoom’s own description of translated captions explicitly says the feature works in Zoom Meetings and Webinars. It identifies named plans with inclusion and an add-on route for paid accounts. More importantly for this question, Zoom says translated captions follow the host’s configured settings: when the host enables the feature, participants and attendees can use it in the meeting or webinar. This is stronger evidence for an external-participant workflow than a generic language-count advertisement. It does not mean that any Zoom link automatically has translation. The meeting’s hosting account and settings matter.

The Zoom article also says that participants can select a speaking language and a caption language. For a multilingual customer call, ask the presenter to set the language they actually speak; Zoom specifically warns that an incorrect speaking-language setting can spoil captions and translations for others. A guest’s target-language choice is a distinct operation from the presenter’s source-language selection. If a salesperson toggles captions in their own session and reports success without asking the outside client what they see, the wrong user has been tested. Have the guest share a screenshot of the relevant caption menu if permission and confidentiality allow; otherwise ask them to narrate the labels and translation result.

Zoom says translated captions do not appear in the recording itself, though they can appear in the full recording transcript; a replay deliverable needs its own validation.

Teams: the organizer’s license is not the guest’s license

Microsoft’s live captions guidance states a remarkably useful distinction. When a meeting’s organizer has Teams Premium or eligible Microsoft Copilot licensing, participants can use translated captions and transcription without each needing that specific license. When individual participants hold eligible licenses instead, only those licensed participants see the Translate to option. The distinction applies to meetings in the cited licensing note. An internal person with a license joining someone else’s meeting does not prove the organizer-enabled path is active for that organizer’s other guests.

For an external sales or support call, find the person who created the meeting, verify their assigned entitlement with IT, and keep them as organizer in the rehearsal. If an assistant schedules on behalf of a sales executive, ask the administrator whose organizer entitlement actually governs the meeting; do not infer it from who sends the calendar invitation or presents slides. Microsoft describes live captions and translated captions separately, so a guest who can read same-language captions has not necessarily been offered translation. Ask them to look for Translate to, choose a target language, and confirm that the displayed text changes. Take care not to promise that every anonymous, browser, or phone participant has the same user interface just because the organizer licensing condition is satisfied.

A second Teams-specific trap is mixing meeting and event rules. Microsoft’s same guidance describes town halls and live events where organizers preselect caption languages, and attendee choices are limited to that selection. That is not the same flow as an ordinary interactive meeting participant choosing Translate to. If an organization routinely hosts external clients in webinars or town halls, ask which event product it uses, confirm the event’s language-selection configuration, and run a separate test with an actual outside attendee. The organizer-license rule in the meeting documentation is not a blanket procurement guarantee for every Teams event format.

Google Meet: external entry and translated captions are separate facts

Google’s translated captions help page names eligible Workspace editions, including Business Standard, Business Plus, Enterprise Standard and Enterprise Plus, and gives participant instructions for choosing Translated captions and languages. The page warns that some languages are gradually rolling out or in beta. Google separately lists external participants as supported in its Meet edition comparison for Business Starter, Standard and Plus. These two facts are useful but should not be fused into a stronger undocumented assertion: the Starter edition’s external-participant check mark is not evidence that Starter includes translated captions, and an eligible edition’s caption setting alone does not fully specify every outside person’s license or joining state.

Google’s joining guidance explains why a guest test needs to capture identity. Workspace admins can restrict who joins; people without a signed-in Google Account may have to request admission. A guest from another Workspace domain, a person with a personal Google Account, and an unsigned visitor are not interchangeable test cases. If a prospect cannot get through the door, fix external-meeting access first. If they can enter but cannot select translated captions, examine edition eligibility, administrator controls, availability in their region and language, and the user interface. Avoid blaming a missing feature on “external guests require paid accounts” without vendor evidence.

Unlike Meet’s separately documented Speech Translation feature, translated captions are text. Spoken-translation entitlements do not settle whether a guest can read translated captions. On the guest’s computer, explicitly select Translated captions and the source and target languages. Google’s help page says previously displayed translated captions can be reviewed for the portion of the conversation while the person was in the meeting with captions on; that does not create a record of anything said before they joined.

OllaSync: individual language selection, with guest access to prove

OllaSync’s live translation page describes translated captions available for each participant in a meeting, with each person choosing a shipped language from the Captions menu; spoken translated audio is an additional toggle. The page describes 19 shipped languages and a maximum of five distinct languages per live session. This means an external meeting with six guests wanting six different output languages needs a specific capacity check: do not silently assume that one meeting can deliver every requested language simultaneously. The feature description says translation follows a beat behind the speaker, not that it is instant or suitable for certified legal interpretation.

The public pricing page lists translated captions on Free, limited to one meeting at a time, up to 30 minutes and 20 people. Pro and Business describe larger meeting and duration limits. The feature page says translation is included on paid plans while pricing also lists translated captions on Free; confirm the precise capabilities of the selected account rather than assuming these pages define identical voice entitlements.

For a prospective external client, the unanswered question in the cited public pages is the precise no-account or cross-organization invitation path. They describe what a learner or participant can select, but they do not spell out a universal guarantee that any unknown visitor can join without an account, a browser limitation, or a contract condition. Arrange a guest test with the real host and an outside email address. Ask that person to report whether an account, verification, or approval is required, and whether the caption language menu appears after admission. If the use case demands frictionless unsigned joining, require an explicit vendor confirmation for that exact flow, not an inference from “browser meeting.”

OllaSync also states that end-to-end encrypted meetings do not provide translation because the service cannot read the audio in that mode. An administrator might select E2EE for a sensitive client conversation and thereby remove the very caption feature being evaluated. Confirm the meeting’s security mode and data-processing terms before inviting a client. If a regulated conversation requires both strict E2EE and machine-generated captions, do not pretend this published OllaSync configuration satisfies both. Decide whether an appropriately governed alternative or human interpretation is necessary. As with the other products, a live language menu is not a warranty about an exported transcript, privacy approval, or translation accuracy.

A guest rehearsal that answers the question

Rehearse around the invitee, not the host. Use the intended organizer, meeting type, security mode, client and browser. If both signed-in and unsigned guests matter, test both. Collect only the observations necessary to decide; do not capture confidential conversation.

1. Write the acceptance criterion. Specify who is organizing, who is invited, whether that person has an account, whether they may sign in, the meeting format, the spoken language, and the desired caption language. “Captions work” is too vague; “the unsigned French-speaking client admitted by browser can turn on English-to-French live captions” is testable.
2. Verify the host entitlement before the invitation. Have an administrator identify the Zoom feature setting and purchased entitlement, the Teams organizer’s eligible assignment, the Google Workspace edition and administrator configuration, or the OllaSync plan and meeting security mode. Save the source URL and date. Do not infer the entitlement from an employee’s unrelated meeting.
3. Send an ordinary outside invitation. Use the same calendar invitation, authentication policy, lobby configuration, allowed domains, browser and device that clients will receive. Record whether the person needed to create an account, sign in, download a client, ask for admission, or change organization. Keep access problems separate from caption problems.
4. Ask the guest to drive. The guest, not the host, turns on captions and selects a target language. Check whether they can select translated captions rather than only ordinary captions. If there is no option, record the visible controls and account state, then ask an administrator or vendor to explain the entitlement rather than guessing.
5. Speak a realistic sample. Use the planned presenter microphone, a short introduction, a product name, a date, a number, and one question. Compare the live result against intended meaning with a bilingual reviewer if available. Repeat when the guest speaks if the meeting is two-way. A short rehearsal demonstrates availability and catches obvious problems; it is not a measured accuracy benchmark.
6. Exercise a change and a failure. Ask the guest to switch caption languages and rejoin once. Test the likely fallback: original-language captions, a human interpreter, a bilingual colleague, rescheduling, or written follow-up. Decide who the guest can contact without translating an inaccessible help message.
7. Close the record. Record host edition or entitlement, meeting type, outside identity category, date, device, join method, security setting, languages, whether the control appeared, whether text was intelligible, and unresolved limits. Do not record “tested” if the only evidence was a vendor web page.

A pilot passes only if the invited person can join and use the target-language captions independently under the intended meeting settings. If the host must reconfigure the call during rehearsal, write down the change and repeat the test from a fresh guest session. If the guest’s own paid license was used, say so: the result may not apply to an unlicensed prospect. If a vendor representative demonstrates on their own licensed account, treat that as a product demonstration, not proof of your customer workflow. The distinction saves more trouble than any unsupported claim about latency or language counts.

Purchasing and accessibility decisions after the pilot

Ask vendors to quote the configuration that passed: organizing accounts, inclusion or add-on, concurrency, event format, guest restrictions, languages, service geography and contractual minimums. Zoom’s add-on route and Teams’ organizer route show why multiplying a per-user price by every outside invitee can mislead. “The guest did not pay” says nothing about the host’s cost. Do not invent a per-guest price.

Captions may be hard to follow on a small screen or alongside a dense screen-share. Pause, offer a written summary, and confirm key decisions. For critical agreements, use a qualified interpreter or bilingual reviewer; do not treat automated captions as a legal transcript. Obtain appropriate consent for transcription or recording. Live captions do not automatically produce a guest-shareable translated file.

Recheck availability when the organizer changes, a plan renews, a policy tightens, a guest switches from desktop to mobile, or the target language is added to a rollout list. Keep the original source links with your procurement notes: Zoom’s feature explanation, Teams caption licensing and controls, Meet translated-caption eligibility, Meet external participant edition matrix, OllaSync’s translation feature, and OllaSync’s plans. These are the evidence for the conditional conclusions above, not proof that every account in every jurisdiction has already been tested.

Practical takeaways

• Choose the guest’s outcome, not the host’s screenshot. An outside person must join and independently select the needed translated-caption language.
• Zoom: confirm the hosting account’s enabled translated-caption entitlement; Zoom explicitly describes host-configured access for participants and attendees.
• Teams: verify the organizer has eligible licensing if unlicensed invitees must use translation; an individually licensed attendee does not enable everyone else’s option.
• Meet: check an eligible Workspace edition and external admission separately; run a guest test before asserting that anonymous visitors have the caption control.
• OllaSync: the published meeting workflow offers participant-selected translated captions; prove the desired external/no-account route and check the five-language session limit and E2EE incompatibility.
• For every vendor: obtain a current contractual answer when the public documentation leaves a guest identity, meeting format, language, device, or region unconfirmed.

FAQs

Does an external invitee need a paid translation license?

Not as a universal rule. Zoom describes a host-configured feature usable by participants and attendees. Microsoft says an eligible meeting organizer enables translated captions for participants without each needing that specific license; if only individual participants have eligible licenses, only those participants see Translate to. The cited Google Meet and OllaSync descriptions do not conclusively specify every external person’s license and login combination. Ask about your precise join route, then test it. A free-to-join meeting and a free-to-use translated-caption feature are different claims.

Can a person without an account use translated captions?

Do not assume so for all four platforms. Google explains that unsigned visitors may have to request admission, and administrators can restrict who joins (Meet joining guidance); that alone does not settle which caption controls an admitted unsigned visitor sees. Zoom and Teams document participant access under particular host or organizer conditions, but the exact anonymous browser experience should be rehearsed. OllaSync’s published feature page describes participant controls without explicitly promising every no-account join route. Use a genuinely unsigned outside browser in your pilot if this is a requirement.

Do live captions translate what the guest says back to the host?

Do not infer automatic two-way comprehension from a guest’s successful one-way caption test. Ask the guest to speak, make sure the product’s spoken-language setting reflects the actual speaker, and have the host select a target language if their workflow allows it. Zoom discusses speaking-language selection, and Microsoft documents changing the meeting spoken language; these are settings to check, not guarantees that overlapping multilingual speech will always translate accurately. If a business negotiation needs reliable two-way interpretation, validate both directions with the same people and consider a human interpreter.

Are translated captions the same as an interpreted audio channel?

No. Captions are text that a participant reads. A translated voice or human interpreter supplies speech through a separate workflow. Google has a separately documented Speech Translation feature; OllaSync describes optional translated audio in addition to captions; neither fact turns all translated-caption entitlements into audio entitlements. The decision here is whether an external guest can read a live translation. If the customer needs to listen while driving, presenting, or watching a complex demonstration, ask a separate audio-access question and never suggest reading a screen in an unsafe setting.

Will the translated text be included in a recording?

Do not assume that it will. Zoom says translated captions do not appear in the recording itself, though they may appear in the full recording transcript. Teams says live captions are not saved and points to transcription for a retained record. Meet’s help page distinguishes caption settings and a recording-captions option; confirm the resulting artifact. OllaSync’s live caption feature description does not promise a guest-shareable translated recording. Decide separately what the external guest is allowed to receive after the meeting.

What if an eligible host still cannot give a client translated captions?

Check the gates in order: outside admission, actual meeting organizer or host entitlement, enabled meeting feature, guest’s client and account state, source and target languages, and the meeting’s security mode. For OllaSync, E2EE disables translation according to its feature page. For Meet, eligibility and external access are documented in different pages; for Teams, distinguish organizer-enabled from individually licensed access; for Zoom, confirm the host’s setting. If support cannot verify the precise configuration, record the case as unconfirmed and use a tested fallback rather than promising captions for a high-stakes call.