What this section is for

Use Content / Country Message to manage optional AI-generated greetings that can vary by player country, site language, and device type. Mobile and desktop text are generated separately so the same greeting can fit both layouts.

This feature is independent of registration, payments, bonuses, games, and ordinary CMS text. If personalized greetings are not part of the brand's content plan, the section can remain unused without changing those flows.

Where the greeting appears

Generating messages does not place them on a page automatically. A published CMS page must contain the section:

General - Personalized Greeting Message

When that section renders:

• an authenticated player uses the country from the player profile when it is valid
• a guest uses the country cookie or the country supplied by the page request
• the current site language selects the greeting locale
• the mobile or desktop version is selected from the current device layout
• an exact country greeting is preferred, then the shared AX fallback
• missing, expired, malformed, or empty content causes the block to stay hidden

Main settings

Setting	Operator impact
isEnabled	Allows scheduled automatic regeneration. It does not prevent an authorized manual run.
reNewEveryDays	Sets the expiry date written onto newly generated messages. It is not the scheduler interval.
prompt	Reusable instruction used to generate greeting text.
mobileTextLength	Generation limit for the mobile version.
desktopTextLength	Generation limit for the desktop version.
countries	Saved fallback country list and the country selection stored by the manager.
languages	Optional configured language list; the broad renewal flow primarily uses active Backoffice languages.

The prompt supports {country}, {language}, and {date}.

Save Settings to Config saves the current prompt and selected countries. Target Language and Countries per Run are browser-local controls and are not saved by that action.

Manual generation

1. Open Manage AI Greeting Messages.
2. Select the target language and countries.
3. Review or edit the prompt.
4. Use Preview Generated Greeting to inspect one mobile and one desktop example. Preview does not save content.
5. Use Generate Greetings to save the first selected countries up to the Countries per Run limit.
6. Review coverage, recent greetings, expiry dates, and activity results.
7. Add General - Personalized Greeting Message to the required CMS page and publish the page.
8. Test the published page with the intended language, country, and device.

Automatic regeneration

Scheduled regeneration requires:

• personalizedGreetingMessage.isEnabled set to true
• a valid prompt and expiry period
• active languages
• user-derived or configured countries
• working AI generation
• the personalized-greeting scheduler and its signed service access
• successful content persistence and cache invalidation

The current scheduled worker normally calls the regeneration endpoint once per configured schedule. In the verified implementation, that endpoint starts a full country-and-language regeneration when enabled. Therefore reNewEveryDays = 7 sets seven-day expiry on generated rows, but it does not guarantee that generation runs only once every seven days.

Renew All Countries & Languages is also a full manual regeneration and ignores isEnabled.

Troubleshooting

If the greeting does not appear:

• confirm that the published page contains General - Personalized Greeting Message
• confirm that the visitor has a valid country and that the site uses the expected language
• check for an exact country greeting or the AX fallback
• check that the message exists, is not expired, and contains text for the current device
• review generation failures, coverage, and recent activity
• confirm that a settings save was followed by generation when new text was required
• confirm that page/content caches were refreshed after generation

If a change is denied, do not assume a particular permission name from the menu alone. The service checks access before changing greetings, but the exact non-superadmin permission alias is not currently established.

Access recommendation

Keep this section available only to content, marketing, or operations users who own localized player messaging. Generation and deletion can change published player-facing copy across many countries and languages, so preview and coverage review should be part of the operating process.