About Multilingual Support
The CRM Server is designed to provide multilingual support, enabling a multiple language Desktop Client (CRM Client) to connect to a single CRM Server transparently.
Desktop Client and Business Administrator are localized into different languages.
A user with an English CRM Client can send messages in Japanese or French if the user's operating system supports the required language fonts.
For example, if a French CRM User needs to send a message in German, the User can change their Input Method Editor to German and type the message.
The International features in CampusNexus CRM enable you to:
• Configure display names of Rules, Tabs, Groups, Properties, and Categories in multiple languages. While the names of Rules, Tabs, Groups and Properties can be configured in multiple languages from Business Administrator, the Category names must be created in multiple languages from the Category Manager in Desktop Client.
• Connect a CRM Client localized in a particular language (Client connection language) to the Server (Default server language) of a different language. For example, from a Spanish, German, or Dutch CRM Client it is possible for a User to connect to the Server (with language packs of German and Spanish, and default server language configured in German language). Now try viewing the Property and Category names in these languages. You see that all Property and Category names for English, German, and Spanish in their respective languages. But in case of Dutch, all Property and Category names are in German itself.
• Automatically detect locale changes and appropriately modify the display formats for date, time, and numbers.
• Automatically detect the language of incoming messages and auto-respond using the detected language. The language detection also helps to check the Subject Line prefix of the incoming message, which enables the system to thread the message to an existing Interaction.
• Configure Rules to use the Language property of an Interaction or Message and take appropriate action. For example, route the Interaction to a specific Team.
• Determine the language of Web Form messages and trigger language-based Rules accordingly.
• Create and display Rule descriptions in the default Server language.