Translate a Cisco Webex meeting or event in real time

Cisco Webex is the video meeting platform of choice for organisations with strict security, compliance, and on-premises infrastructure requirements — government, finance, healthcare, defence, and the enterprise tier where Teams and Zoom struggle to meet procurement requirements. Webex’s strength is that it’s been the right answer for these organisations for two decades; its complication for translation is the same as Teams’: built-in translation is licence-gated, language-limited, and locked behind an IT approval process for many tenants.

For a Webex host who needs translation on a single call — a regional all-hands, a customer call across continents, a partner meeting with non-English speakers — the gap between “we have Webex” and “we have functioning live translation in the languages we need” can be measured in months of IT tickets.

Loquira sits beside Webex without touching the Webex tenant. The host runs Loquira on a phone; attendees who want translation join from their own device. Nothing is installed in Webex, nothing in the corporate Webex Control Hub changes.

Why parallel matters more in regulated industries

Webex is the platform of choice for organisations where adding a new app is genuinely difficult — security review, change management, compliance documentation, sometimes a multi-quarter procurement cycle. The friction is not theoretical; it’s the actual reason translation needs go unmet in these organisations for years.

Loquira’s parallel model bypasses the friction because:

1. Nothing is installed in Webex. No app, no integration, no tenant-level change. Webex remains exactly what it was.
2. The listener uses their own device. A corporate-issued laptop running Webex is paired with the attendee’s personal phone running Loquira. No corporate IT change, no managed-device implication.
3. The host can deploy in five minutes. A team running a meeting today can add translation today, without raising a ticket.

For organisations where the alternative is “we don’t have translation,” this is the practical path.

Recommended setup

• Microphone. Wired or wireless headset is most common in Webex contexts. Close-mic positioning matters more than mic class for recognition quality.
• Loquira device. A phone on the speaker’s desk, close to the microphone source. In a conference room with multiple presenters, position the phone where it can hear all speakers, or run one session per speaker.
• Distribution. The Webex calendar invite is the primary channel. Webex chat is the fallback for late arrivals. For all-hands and customer events, consider a separate email reminder one hour before the meeting.
• Headphones for listeners. Most enterprise headsets work fine. The listener uses the headset for Webex audio and a phone with earbuds for Loquira’s translated track, or mutes Webex and listens exclusively to Loquira.

Webex Events / Webex Webinars

Webex Events (formerly Webex Webinars in some tenants) is the broadcast-style tier for one-to-many sessions with registered audiences. The pattern fits cleanly:

• Pre-event distribution. Put the Loquira link in the registration confirmation and the day-of reminder. Pre-registered attendees can pre-load translation on their phone before the event.
• In-event distribution. Post the link in chat at the start. Re-pin every fifteen minutes for late arrivals.
• Listen-only audiences. Attendees in listen-only mode are the natural Loquira audience — they’re not contributing audio, only consuming it.

For events with speakers across geographies, the per-speaker pattern applies: each speaker runs their own Loquira session from their own location. Listeners switch between sessions as the active speaker rotates.

Webex’s built-in translation

Webex has had live translated captions for several years, and recent releases include AI Assistant features that translate spoken audio. Where licence tier and language pair align, those features can be combined with Loquira without conflict — captions on the Webex UI for the desk-listener, audio on the listener’s phone for those who prefer to hear rather than read.

The gap Loquira closes is the language-pair coverage outside the supported set and the audio-first listening mode for sustained-duration meetings. A listener reading captions for sixty minutes will be exhausted; a listener with translated audio in earbuds participates the way a native speaker would.

Known limitations

• Closed corporate networks. Webex itself often runs on tightly-controlled corporate networks. Loquira’s listener app runs in a browser and requires standard WebRTC connectivity. If your corporate network blocks WebRTC, listeners should use their personal phone on cellular data — typically the simplest path.
• Government and high-security tenants. Webex deployments in government and regulated industries sometimes restrict external links in calendar invites. In those tenants, share the Loquira link through a separate approved channel (internal portal, email through compliant gateway) ahead of the meeting.
• Webex Calling and PSTN attendees. Attendees who joined the meeting by phone dial-in cannot use Loquira through the same line. Direct them to the Loquira link on a separate device.
• Recording and compliance retention. Webex’s cloud recording captures Webex audio per the organisation’s retention policy. Loquira’s transcript and per-language audio replays are separate artifacts; for compliance contexts where recording retention is regulated, treat them as parallel files and align them with your existing retention process.
• On-premises Webex deployments. Some enterprise tenants run Webex on-premises with limited public-internet exposure. Loquira’s listener app requires public-internet access from the listener device. This is rarely a blocker in practice (listener uses personal phone on cellular), but worth flagging for security-sensitive deployments.