That plan sounds well and good, but having different communities for different languages would be a nightmare logistically. They would have different users and different tickets. Our customers have an understanding they are going t be getting support in English, because we are an English-speaking staff (though we do have Spanish and Portuguese speaking staff, too). So we do have some clients we do write in their native tongue, actually. But mostly it is English.
But having the UI elements, everything but the actual support content, translated would be a great help. So I do not see it as a problem of having "mixed" content.
That plan sounds well and good, but having different communities for different languages would be a nightmare logistically. They would have different users and different tickets. Our customers have an understanding they are going t be getting support in English, because we are an English-speaking staff (though we do have Spanish and Portuguese speaking staff, too). So we do have some clients we do write in their native tongue, actually. But mostly it is English.
But having the UI elements, everything but the actual support content, translated would be a great help. So I do not see it as a problem of having "mixed" content.
As we've mentioned in previous comment, we do plan on integrating it some day, but if customer see UI in his language, he will think that he can add content in his native language if UI matches his language.
There are no problems with tickets here, as content is not public, but we think that topics should be divided to different communities if languages are different.
That's how big companies does to have specific community dedicated to specific language - the same with Knowledge Base.
As we've mentioned in previous comment, we do plan on integrating it some day, but if customer see UI in his language, he will think that he can add content in his native language if UI matches his language.
There are no problems with tickets here, as content is not public, but we think that topics should be divided to different communities if languages are different.
That's how big companies does to have specific community dedicated to specific language - the same with Knowledge Base.
Now agents can choose language to use in the system. Users are not able to select it because they will have to mix the content in one system - but we have plans for this in long term road map.
Now agents can choose language to use in the system. Users are not able to select it because they will have to mix the content in one system - but we have plans for this in long term road map.
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
We'll consider adding that option, but no plans as of now.
The thing is that if you have community to provide support in one language, content shouldn't be mixed.
So it's better create different communities for different languages as we think it would work much better.
Otherwise, online translation tools could be used
We'll consider adding that option, but no plans as of now.
The thing is that if you have community to provide support in one language, content shouldn't be mixed.
So it's better create different communities for different languages as we think it would work much better.
Otherwise, online translation tools could be used
That plan sounds well and good, but having different communities for different languages would be a nightmare logistically. They would have different users and different tickets. Our customers have an understanding they are going t be getting support in English, because we are an English-speaking staff (though we do have Spanish and Portuguese speaking staff, too). So we do have some clients we do write in their native tongue, actually. But mostly it is English.
But having the UI elements, everything but the actual support content, translated would be a great help. So I do not see it as a problem of having "mixed" content.
That plan sounds well and good, but having different communities for different languages would be a nightmare logistically. They would have different users and different tickets. Our customers have an understanding they are going t be getting support in English, because we are an English-speaking staff (though we do have Spanish and Portuguese speaking staff, too). So we do have some clients we do write in their native tongue, actually. But mostly it is English.
But having the UI elements, everything but the actual support content, translated would be a great help. So I do not see it as a problem of having "mixed" content.
As we've mentioned in previous comment, we do plan on integrating it some day, but if customer see UI in his language, he will think that he can add content in his native language if UI matches his language.
There are no problems with tickets here, as content is not public, but we think that topics should be divided to different communities if languages are different.
That's how big companies does to have specific community dedicated to specific language - the same with Knowledge Base.
As we've mentioned in previous comment, we do plan on integrating it some day, but if customer see UI in his language, he will think that he can add content in his native language if UI matches his language.
There are no problems with tickets here, as content is not public, but we think that topics should be divided to different communities if languages are different.
That's how big companies does to have specific community dedicated to specific language - the same with Knowledge Base.
Now agents can choose language to use in the system. Users are not able to select it because they will have to mix the content in one system - but we have plans for this in long term road map.
Now agents can choose language to use in the system. Users are not able to select it because they will have to mix the content in one system - but we have plans for this in long term road map.
Replies have been locked on this page!