Multi-directional Translation In-Community
Community supports a global audience but to often supports one language - English. With In-Community translation on Community is able to support multiple languages speakers - all in real-time. With LanguageConX community can plug into your language translation engine (MSFT, Google, etc.) or your Translation Management System (TMS) such as Smartling, DeepL, Lingotek, Systran, etc. taking advantage of translation memory and glossaries established by your organization. The configurable option allows for automated or manual translation requests, in other works you can have all your content with your community (or by category) translated automatically upon publishing or send the request off for translation when requested by the user (manual). Once the content is requested for translation, that discussion will be update in real-time from that point forward. In both cases, user from around the world are able to engage in community, not matter the language they speak. Add benefit is that translations are retained in community so that requests are not sent to the translation engine upon every view, costing more in translation costs. Moreover, the translated posts can be edited within Community.Cross-Community Translation
Many larger organizations establishes language specific communities to support the diverse customers around the world. The challenge has been how do the language specific communities benefit from the subject matter experts (SMEs) that participated and contribute in the "other" language communities? With Cross-Community LanguageConX content such as "Accepted Solutions" from one language community can be automatically translated and shared with the other language specific community(ies). This is a multi-directional translation and syndication of content in which a English speaker can be engaged online with a German speaker, and both can be engaged with a Spanish speaker, etc. Often the "English Community" is the most vibrant and contains the most value as it relates to solutions and SME engagement. Now, no matter the community the choose to engage they are able to consume content in their language and engage across what was language barriers.Syndication of Knowledge between SFDC and Community
Surface content (knowledge base articles) both in Community and SFDC KB, without any additional effort. Surface content with the user chooses to be - and with ContentConX we syndicate KB articles bi-directionally between SFDC and Community. Any edits of the source document will automatically be reflected in the syndicated article."Sharing" Content Across Community
Often content is relevant across categories and boards within the community but exists only in one place. The ShareConX capability allows users to "share" content across the community - while maintaining the ability for all to collaborate no matter where they choose to engage in the Community.Bi-Directional Syndication Between Teams and Khoros
Many of the most knowledgeable team members (Product Mgrs, Engineers, etc.) live inside the organization and use an internal collaboration tool such as Teams. They rarely if ever engage in the external community where customers and prospects engage. Although they may be tasked by management to contribute to the external community, it is outside their normal workflow within Teams, which in as of itself is an inhibitor to contribution. Now with CollaborationConX for Teams, content is easily syndicated between Khoros Community and Microsoft Teams in real-time. This is a role based capability that can be enabled for Community Managers, Moderators and expand to SuperUsers as an additional benefit giving them greater access to SMEs within the organization.
Knowledge Base
Learn how SmartConX can be leveraged to help prevent siloed information.5 Posts
