This article covers two common issues reported during Napster Station deployments: the companion defaulting to English instead of the configured language, and knowledge base updates not reflecting in the live deployed experience.
Companion defaults to English or refuses to switch languages
Napster Station companions support multiple languages, but if the companion is not configured with an explicit default language instruction, it will fall back to English regardless of what language the visitor uses.
To set a default language:
- Open the companion configuration in the Napster admin dashboard.
- In the Persona Prompt, add an explicit instruction such as: "Always respond in German unless the visitor speaks a different language, in which case match their language."
- If you need the companion to support multiple specific languages (e.g. German and Chinese), add instructions for both: "Respond in German or Chinese based on the language the visitor uses. If uncertain, default to German."
- Save and republish the experience.
The companion responds inconsistently in the target language
If the companion switches between languages mid-conversation or reverts to English unexpectedly:
- Strengthen the language instruction in the Persona Prompt - be explicit and repeat the instruction: "You must always respond in German. Do not switch to English under any circumstances."
- Ensure the knowledge base content is also in the target language. If the uploaded documents are in English, the companion may revert to English when drawing from that content.
- If the issue persists in a live deployed environment, submit a support ticket with the Station URL, the languages affected, and example conversation transcripts showing the incorrect behaviour.
Knowledge base changes not reflecting in the deployed experience
After updating the knowledge base on a deployed Napster Station, changes may not appear immediately in the live experience.
- Allow up to 5 minutes for knowledge base changes to propagate to the deployed experience after saving.
- After saving changes, use the Republish option to force the experience to reload with the latest configuration. Do not rely on auto-sync for time-sensitive deployments.
- If changes still do not appear after republishing, clear your browser cache and reload the experience, or restart the Station hardware if applicable.
- For event or exhibition deployments where timing is critical, apply and republish all knowledge base updates at least 30 minutes before go-live to allow for propagation and verification.
Pre-deployment checklist for multilingual or event deployments
- Set an explicit default language in the Persona Prompt
- Upload knowledge base content in the target language(s)
- Republish the experience after every change
- Test the live experience in each target language at least 30 minutes before the event
- Confirm knowledge base content reflects the latest version by asking the companion a question that references recently added content