Running multilingual events across global markets

Onomi supports multilingual events across the attendee app, event content, registration pages, live sessions, the meeting request portal, and lifecycle notifications. Workspace languages are managed per event in Backstage. Portal and notification languages are managed once for your organization in Onomi 360.

Workspace languages and translated content

The attendee app follows the language of the attendee's browser or device when that language is enabled for the workspace. If there is no match, it uses the workspace's default language.

Onomi includes built-in interface translations for English, German, French, Italian, Spanish, Dutch, Japanese, simplified Chinese, and traditional Chinese. You can add further languages and supply their translations through the Translation manager in Backstage.

Use the existing workspace-language guides for setup and maintenance:

• Supported languages lists the built-in languages and explains the language fallback.
• Exporting, importing, and copying over workspace translations covers the spreadsheet workflow and reuse across workspaces.
• Recommendations and guidelines for creating translation keys explains how to name and maintain custom keys.

Note: Enable a language only when you plan to translate the full attendee experience. Missing labels fall back to English, which can leave the app partly translated.

Pages, sessions, speakers, and sponsors also contain content that your team writes. Translate that content where it is maintained in Backstage. Pages can be targeted using the attendee's preferred-language profile field. Sessions, speakers, and sponsors expose their translatable fields in their detail pages.

Multilingual registration pages

A registration page can follow the registrant's browser language and offer a language selector. Its landing page, forms, session content, speaker content, sponsor content, header, and footer can all be translated.

Follow Creating a multilingual registration page for prerequisites, configuration, and testing. The guide also explains how to append ?i18n=true to the registration-page URL to identify missing translation keys.

Important: Multilingual registration pages are not supported when the registration page is embedded in another website.

Meeting request portal and lifecycle notifications

The meeting request portal and lifecycle notifications are organization-level surfaces. Administrators manage them in Onomi 360 > Policies > Languages.

The portal follows the requester's browser language. If that language is neither built in nor added for your organization, the portal uses the organization default language.

Lifecycle notification templates are maintained per language. A notification uses the recipient's preferred language when the platform holds one, and the organization default language otherwise. Choose a default language that your approvers, compliance reviewers, and finance owners can read.

To add a portal language:

1. In Onomi 360, open Policies > Languages.
2. Under Portal languages, select Add language.
3. Review the translations for the portal and notification key sets, or supply them with the export and import controls.
4. Under Organization default language, select the fallback language.
5. Select Save, then test the portal and notification templates in each configured language.

When AI assistance is enabled, Onomi drafts both key sets for a newly added language. Drafts are not shown to requesters until a reviewer accepts or edits them. Coverage reports reviewed strings, not generated drafts. See How to use AI assistance in Onomi 360 for the review flow and governance controls.

You can also edit individual lifecycle templates in Policies > Notifications. See Configuring notifications for requests and approvals for triggers, recipients, and template maintenance.

Some system-generated messages do not have editable templates, including budget-policy notifications and travel-module sends. They use a built-in interface language or the organization default language. Factor these messages into the choice of default language.

Live captions and interpretation

Live sessions can use AI-generated captions and audio translation or human interpretation. The available option depends on the session format and provider:

See Live session closed captions and simultaneous translation capabilities to compare providers, supported session formats, and attendee behavior. Contact your SpotMe Account Manager to confirm availability and plan provider setup.

* Onomi 360 MeetingsEQ exclusive capabilities.