The SeeClickFix 311 CRM system provides translation of the platform-based navigation and controls within the system. The platform does not translate user-generated content.
The mobile app provides translation for these areas based on the user's phone language settings. Languages on the mobile app are available in:
Arabic
Chinese Simplified
Chinese Traditional
English
Filipino
French
German
Italian
Korean
Portuguese
Russian
Spanish
Tagalog
Vietnamese
For the web-based platform, language preference is determined by the SeeClickFix 311 CRM user settings. The web platform enables language preferences in:
Arabic
Chinese Simplified
Chinese Traditional
English
Finnish
French
French Canadian
German
Greek
Italian
Japanese
Polish
Portuguese
Portuguese (Brazil)
Russian
Somali
Spanish
Swedish
Tagalog
Vietnamese
Mobile
In the SeeClickFix 311 CRM mobile apps (Android and iOS), data hardcoded into the system will be translated according to the phone's operating system. So, for a phone set to Spanish, hardcoded items in the mobile apps, such as the navigation buttons at the bottom of the screen and the prompts to upload a photo, will translate to Spanish.
However, items that are customizable by the municipality, such as mobile buttons and request categories, and content that is submitted by users, such as requests and comments, will remain in the language that they were entered in.
The following images illustrate how buttons on the bottom of the screen, as well as for instructions for the photo upload, are all translated, while user content and mobile buttons are not. This is a preview of an organization with the mobile buttons in English and the phone set to Spanish.
Web
The SCF web portal works similarly to the mobile app, except that the language of hardcoded content will default to the user's language preferences on SeeClickFix 311 CRM. They can set this at the creation of an account or by updating preferences within SeeClickFix 311 CRM. Like the mobile app, request categories, requests, and comments will remain in the language they were entered in.
Multi-Lingual Populations
There are three primary workarounds to accommodate a bi- or multi-lingual population. These workarounds are either with Request Categories or with Agencies.
Request Categories and Mobile Buttons
The first workaround is to create Request Categories and Mobile Buttons with short names and add a second language with a slash ("/"). For instance, "Pothole/El Bache."
The benefit of this workaround is that the categories remain the same, so duplicate detection will still work, and data collection will not be affected. The potential downside is that requests in a foreign language may be automatically assigned to someone who cannot read that language.
Agencies
Alternatively, a separate agency can be set up for each language needed. For instance, an agency with the same boundary might be created with a Spanish title, and all Request Categories under it will be in Spanish. This workaround is particularly useful for municipalities that need 3 or more languages featured.
A benefit of the agency approach is that requests will come into different categories, and they can be automated to go to individuals who speak the requester's language.
A downside of having multiple agencies configured like this is that the same category in different languages is no longer connected, which will affect duplicate detection and data collection.
Language-Specific Request Category
Finally, you can also create a single request category for each secondary language needed. All requests in this category can be automatically assigned to an individual who can translate the requests and then recategorize them.
The benefits of this solution are that requests are automatically sent to someone who can read and translate them. The request can then be recategorized into the correct category. The potential downside of this solution is that since all requests from one language will go to one person to translate and reassign, the workload may become overwhelming.
