Globalization and Localization of Application

Coach Pulse: Globalization & Localization Framework

Today, Coach Pulse serves one global experience. What we're building is a region-aware architecture where the four core surfaces — Today (Welcome Dashboard), Train (AI Voice Roleplay), Culture Feed (What's New), and Ask Pulse — are each customized per region, so an associate in Tokyo, Riyadh, or Kuala Lumpur opens an experience built for their market, not a US experience translated after the fact.

There are three layers to it:

1. Regional content buckets. Each region gets its own configuration of the four modules: region-specific Culture Feed content and campaigns, Train personas and scenarios relevant to that market's customers, Ask Pulse knowledge scoped to regional product assortment and selling context, and a Today dashboard reflecting regional priorities and training calendars. Content admins manage each bucket independently through the admin PWA.

2. Language selection within region. Region and language are decoupled. Within any regional bucket, associates can switch their display language from a dropdown — so a Malay-speaking associate in a Singapore store and an English-speaking colleague in the same store see the same regional content, each in their own language. The roleplay agent infrastructure already supports this pattern (persona sets exist per language — Korean, French, Arabic, Malay, Indonesian, Thai, etc.), and this extends that model across the full app.

3. Automatic regional assignment. No manual setup: on sign-in, the associate's region is derived from their identity — store/location data from the Location Data API and Entra token claims — and they're automatically dropped into the correct regional bucket. Region is assigned by the system; language is chosen by the user.

The net effect: one codebase, one platform, many market-correct experiences — with region determined automatically and language personally.

4. Region-aware admin. The admin PWA has to mirror the same regional structure so content can be created, translated, and published per bucket — not just consumed per bucket. That breaks down into:

• Admin scoping by role. The AD group structure already anticipates this: Global Training Admins see and manage all regions; Regional Training Admins are locked to their own bucket. Region assignment on the admin side comes from the same identity plumbing (Entra claims), so a regional admin signs in and lands directly in their region's workspace with no visibility into others.

• Per-region content management. Every content surface in admin — Culture Feed posts, Train persona/scenario assignments, Ask Pulse knowledge scoping, Today dashboard configuration — gets a region dimension. Admins author into a specific bucket, or Global admins can publish globally with regional overrides.

• Language variants at the content level. When an admin publishes a Culture Feed post or dashboard item into a region, they manage language variants of that content (authored or translated), so the associate-side language dropdown has real localized content behind it — not machine-translated UI chrome over English content.

• Regional analytics. Team and training analytics in admin roll up within the regional boundary — a Regional Training Admin sees their region's data only; Global sees cross-region rollups.