SeeClickFix 311 CRM supports language preferences differently across mobile and web experiences. Fixed navigation and controls can be localized in both experiences. Supported mobile apps can also automatically translate applicable organization-configured and user-generated content. Automatic translation changes only what the resident sees; the original content remains unchanged.
Note:
The following lists apply to fixed interface localization.
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 mobile apps for Android and iOS, fixed navigation, controls, and other interface content follow the resident’s device language. The language selected in a resident’s SeeClickFix profile does not control the mobile app.
Supported mobile apps can also automatically translate applicable organization-configured and user-generated content into the resident’s device language. This can include:
Home content and Notices
Request categories and questions
Request descriptions
Comments
Other organization-configured or user-generated content
Automatic translation is enabled automatically in the standard SeeClickFix 311 CRM mobile app (Container app). For eligible Marketplace mobile apps, Organization Owners can control automatic translation through Organization Settings.
Availability depends on the app version, device, operating system, region, and translation service. Translations may not be exact, and the original content remains unchanged.
See Automatic Translation in SeeClickFix Mobile Apps for current availability, supported languages, device requirements, configuration instructions, and troubleshooting.
Web
The SeeClickFix web experience uses the language selected in the user’s SeeClickFix profile to localize fixed navigation and controls. It does not automatically translate organization-configured or user-generated content, such as request categories, requests, or comments. This content remains in its original language.
Multi-Lingual Populations
The following configuration approaches may still be useful for web and CRM experiences or when an organization needs language-based routing. Automatic mobile translation is display-only; it does not modify original content or translate content in the web portal or SeeClickFix 311 CRM.
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.
