Running multilingual events across global markets

You can run multilingual events across the attendee app, event content, registration pages, live sessions, the meeting request portal, and lifecycle notifications. You set workspace languages per event in Backstage. You set portal and notification languages 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 comes with built-in interface translations for English, German, French, Italian, Spanish, Dutch, Japanese, simplified Chinese, and traditional Chinese. You can add more languages and supply their translations through the Translation manager in Backstage.

Use the workspace-language guides to set up and maintain languages:

• Supported languages lists the built-in languages and explains the language fallback.
• Exporting, importing, and copying over workspace translations explains 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 have content that your team writes. Translate that content where you maintain it in Backstage. You can target pages by the attendee's preferred-language profile field. Sessions, speakers, and sponsors have the fields you can translate on their detail pages.

Multilingual registration pages

A registration page can follow the registrant's browser language and offer a language selector. You can translate its landing page, forms, session content, speaker content, sponsor content, header, and footer.

Follow Creating a multilingual registration page for what you need first, the setup, and how to test it. The guide also explains how to add ?i18n=true to the registration-page URL to spot missing translation keys.

Important: Multilingual registration pages are not supported when you embed the registration page in another website.

Meeting request portal and lifecycle notifications

The meeting request portal and lifecycle notifications are set up once for your whole organization. Your 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.

Each language has its own set of lifecycle notification templates. A notification uses the recipient's preferred language when the platform has one on record, and the organization default language if not. 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 add 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 language you set up.

When AI assistance is enabled, Onomi drafts both key sets for a language you add. Drafts are not shown to requesters until a reviewer accepts or edits them. Coverage counts 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 each lifecycle template on its own in Policies > Notifications. See Configuring notifications for requests and approvals for triggers, recipients, and how to maintain the templates.

Some messages that the system sends on its own do not have a template you can edit, including budget-policy notifications and travel-module sends. They use a built-in interface language or the organization default language. Keep these messages in mind when you choose the default language.

Live captions and interpretation

Live sessions can use AI captions and audio translation or human interpretation. Which option you can use depends on the session format and provider:

See Live session closed captions and simultaneous translation capabilities to compare providers, the session formats each supports, and how each behaves for attendees. Contact your SpotMe Account Manager to confirm what is available and plan the provider setup.

* Onomi 360 MeetingsEQ exclusive capabilities.