+2
Hello - looking for user stories on your use of supporting language support roll out, specifically non-roman character languages (Chinese, Japanese, Korean).
Tip and tricks for email assist and journey orchestrator emails? How do you account for character rendering, how do you build your templates? Appreciate any lessons learned as I look to enable our global CSMs.
Best answer by jean.nairon
View original
+1
+4
Hi
We have CSMs across the globe and in Asia, they document all their timeline activities and CTA tasks in their native language.
We don’t send translated emails in Journey Orchestrator however I have helped other companies set this up. If you track language on a contact or company record, you can send different language emails around the world.
Journey Orchestrator gives you the ability to do HTML. If the characters render correctly in HTML, they will render correctly in the email template.
Hope this helps!
+11
+1
+10
+11
+2
I think we are also trying to request Folder Organization within the Chrome plugin since it can be a bit cumbersome to search and scroll through a whole lot of templates instead of grouping in logical Bins :)
+2
Hi all, thanks for the responses. Sorry, my questions weren’t around variants, more the rendering of characters, looking to see if anyone faces issues. I’ve never worked with non-roman characters in html before, but I did some testing and think I have a handle on ensuring it renders correctly.
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
