Overview

When Simpplr sends a notification about content like a page publish, event reminder, or album activity, the title and summary now appear in each recipient’s preferred language. This works across every notification channel: in-app, mobile push, SMS, web push, and email.

Simpplr uses manual translations first when an editor has provided one, then falls back to auto-translation if your organization has it enabled. If neither is available, the notification shows the original content language.

What’s included

• Translated content titles and summaries shown automatically based on each user’s preferred language (locale).

• Supported channels: in-app, mobile push, SMS, web push, and email.

• Supported content types: Pages, Events, Albums.

• Translation source priority: manual translation first, then auto-translation; if neither is available, notifications show the original language.

How it works

1. When a notification is generated for content (for example, a page publish, event reminder, or album activity), Simpplr determines the recipient’s preferred language from their profile.

2. Simpplr selects the translation to use, in this order: manual translation provided by an editor, then auto-translation generated by Simpplr translation services, then fallback to the original content language if no translation exists.

3. The translated title and summary are delivered per recipient to every channel they’ve enabled (email, in-app, push, browser or web push, SMS).

Editors can improve accuracy by supplying manual translations for key content. When present, manual translations always override machine translations in notifications.

User experience by channel

Requirements and controls

• Tenant translation enablement: Automated translation must be enabled by your organization for auto-translations to appear. Manual translations work regardless.

• Feature rollout: Delivered as part of the 26.06 release stream. No user action is required once enabled by your Simpplr admin team.

• Graceful degradation: If a translation is unavailable, the original content title and summary are used.

Scope

• Only content titles and summaries are translated in notifications. Other dynamic notification text (for example, action verbs) follows Simpplr’s standard UI localization.

• Translation in notifications depends on either an existing manual translation, or successful completion of Simpplr auto-translation for the target language.

• Dialect variants (for example, en-US vs en-GB) may share the same translated strings today; future enhancements may refine dialect handling.

Best practices

For App managers and editors

• Provide manual translations for high-visibility announcements and Must Reads to ensure top accuracy.

• Confirm your tenant’s automated translation is enabled to maximize coverage.

• Maintain accurate source language on content to improve machine translation quality.

For end users

• Set your preferred language in your profile to receive localized notifications.

• If a notification appears in the original language, it likely means a translation isn’t yet available for that item.

Troubleshooting

Identify your issue below, understand what happened, and take the right action.

You’re not receiving translated notifications

• What happened: The channel may not be enabled for your account, or your profile language isn’t set. Past fixes have also addressed language-specific gaps in non-email channels (push, SMS, browser).

• What to do: Confirm the channel is enabled for your account and that your profile language is set. If the issue is isolated to push, SMS, or browser notifications for specific languages, contact your admin.

The notification shows the original language instead of your preferred language

• What happened: No manual translation exists for your language, auto-translation hasn’t completed yet, or translation is disabled for your tenant or that content module.

• What to do: Wait for auto-translation to complete, or ask an editor to provide a manual translation. If translation is disabled for your tenant, your admin can enable it.

The notification shows the auto-translation even though a manual translation was provided

• What happened: The manual translation may have been saved against the wrong language code or a different version of the content. Manual translations should always take precedence over auto-translations.

• What to do: Verify the manual translation was saved for the correct language code and content version. If the problem persists, contact support.

Translated titles look different between your mobile and desktop notifications

• What happened: Mobile and desktop should present translated titles consistently. Differences are usually caused by an older app version or a mismatch in language settings between the two devices.

• What to do: Verify your app version and confirm the same language is set on both devices. If the inconsistency continues, report it to your admin with examples so support can investigate.

FAQs

Q: Which content types are supported for translated titles and summaries in notifications?

Ans: Pages, Events, and Albums are supported.

Q: Do I need to do anything to receive translated notifications?

Ans: No user action is required. Your Simpplr admin must have translation features enabled for auto-translations; manual translations work when provided by editors.

Q: Which language will my notifications appear in?

Ans: You’ll see the language set in your user profile. If a translation in that language isn’t available, you’ll see the original language version.

Q: When was this introduced?

Ans: Title and summary translations were introduced in 26.05 for core content surfaces. Notifications are now included.