Enable dynamic content in the email template
Enabling dynamic content in the email template would enable us to use the same template for RTL and LTR languages instead of hard-coding it into every single trigger that sends mail (dozens of them.)
We could create tokens for direction and alignment and change them to rtl/ltr and right/left according to the language.
-
Thanks, Amalia -
We have email templates slated as one of our areas to improve as we move into 2017. There's no timeline at this point, but that is feedback we'll keep in mind.
-
Hi Max,
What is the status on this? We seem to be unable to use dynamic contents in our email template. This means that we cannot localize our logo, the phone numbers to our support center and our links to our website.
Any updates? Being able to properly localize emails is really important for our brand image. Serving English content to our multinational users would be really amateur.Thanks,
Raphaël -
+1 for this.
We thought this would be possible but it turns out dynamic content cannot be added to email templates at all which also means email templates cannot be translated!
-
+1
Tried to add our own localized text using {{dc.my_footer}} but the result was empty.
-
+1
Having multilanguage support in the templates is a must for so many companies. Hard-coding is not an option when it comes to multi-language.
Are there any updates? or at least any alternative approaches.
-
+1 Having trouble customizing the automated email sent out after a customer creates a new ticket.
-
Hi there, curious if there has been any additional traction here. As of ... 3 years ago Zendesk appears to have highlighted this as a need and area to focus on but doesn't seem to have put anything together to solve for it.
-
Hi, what's the latest on this, please? The inability to customise the email template per language really lets down those who support multiple markets, language, and brands. Thanks.
-
Hi all -
The product team is currently evaluating email templates and they are looking at ways to improve the functionality in that area of the product. Because they're still early in this project, they can't speak to whether or not their solution will ultimately include dynamic content or not.
For those who are interested in this, the most helpful thing is to share details of the challenges you're facing with templates as they currently operate. When product managers work on solutions, they look at how they can implement a couple of things that solve for multiple problems, so those details really help them look at the bigger picture.
Thanks as always for your participation, and for helping to make Zendesk better!
-
Comeon Zendesk - you do a lot of things right, but you also to very simple things very wrong.
It shouldnt take 9 years to implement a split functionality, and it shouldn't take 5 to implement branded templates for emails..
-
+1 from my side. E-Mail Templates or at least a Smarty-Like System would be amazing. I e.g. would be in need to use if/else conditions for parts of the mails.
-
+1, not being able to localize the footer text of our email template has been especially frustrating and has lead us to use undesirable work arounds.
-
+1 We need branded templates as well. More than ever now that the brand manager will stop working in the next couple of months.
-
This request was put in 3 years ago? But still no dynamic content?
Is it still not possible to add different URL's (dynamic content) based on user language inside the Email template/footer?
Is there another way this can be achieved?
Thanks -
As a company, we operate with multiple brands and each brand has its own phone number.
We would like to be able to add them in a footers for each brand separately? Will be that available?
-
@...I wrote the linked article below (including an example). It will get you the ability to have unique content per brand in the emails that are sent to customers. Adding a unique phone number per brand is simple. You can have completely brand specific email templates (layout, colors, logos, etc) per brand. Check it out here:https://support.zendesk.com/hc/en-us/community/posts/360033000374-How-to-structure-the-Zendesk-email-template-to-use-custom-HTML-layouts-for-each-of-your-Multiple-Brands
-
Thanks@...for your insights on how to indivualize e-mail templates using Brands.
However, this is not the solution requested many times ...
★★★ AND I STRONGLY +1 ★★★
... as translating your mail templates to some languages would not only need Enterprise but even the Multi brand upgrade. Just to set footers in 5 more languages than your main language.
In your article you addressed the ease of no longer maintain a shitload of triggers / notifications. Even with dynamic content this can be a hassle.
Zendesk, you leave us (your users, even Enterprise) empty handed bynotallowing liquid / dynamic content in e-mail templates, You even explained us why it might be so important to NOT have it.
Please!
Give us i18n abilities, we're multi-national companies!
Kind regards,
奥利弗
-
Hi,
Any update regarding the request?
You don't give us any timeline or update for a long time.
Please respond and give us answers.Thank
-
Hi Noam -
The product team doesn't have any updates on this request.
-
Hi,
+1 from me as well, supporting dynamic content outside the content placeholder would be much appreciated.
Thanks !!
-
+1 for me as well. Does anyone have a good workaround for displaying different footers for different languages?
-
Our base footer looks like this:
当电子邮件主体非英语语言wedish) and the footer in english it doesn't look very reliable. Having dynamic content tags in our footer would help with this.
-
We solved the email template problem with dynamic content by using a simple trigger to send the email. Using triggers the dynamic content does work and send the email in the user's language. Contact us if you need further detail!
-
Oscar, this has always been possible, but just for the e-mail content. We're talking about the e-mail template, which does the fancy header, footer, CSS part to make mails shine. But it does not allow to put a country- or language specific variation in the footer. Unfortunately but very traditionally.
{{dc.localized_salutation}}
奥利弗 -
This is fixed now right?
-
I've tried it right now, and NO, the feature from 2016 is still not developed.
-
I would love to see this available, managing the DC for things like footers separately is a lot of extra work and prone to human error. It would be great to have this built into the template instead.
-
We are investing a lot of time in making Zendesk multi-language but when we are unable to change the templates then customer is going to get mixed languages in their messages.
希望看到一个改善。一个统计us of the plan would be appreciated.
-
I came across the same problem and the only solution for the multibranding and multilanguage email template I was able to build is the following for 7 languages:
(change the BrandName1 and BrandName2 to your brand names)<！doctype html>
Zendesk Email Template
{{delimiter}}
{% case footer %}
<！-- email template for English -->
{% when 'This email is a service from BrandName1.' %}custom code
<！-- email template for Russian -->
{% when 'Это служебное письмо от BrandName1.' %}custom code
<！——邮件模板葡萄牙——>
{% when 'Este email é um serviço de BrandName1.' %}custom code
<！-- email template for Arabic -->
{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}custom code
<！-- email template for Japanese -->
{% when '本メールはBrandname1から送信されています。' %}custom code
<！-- email template for Spanish -->
{% when 'Este correo electrónico es un servicio de BrandName1.' %}custom code
<！-- email template for Chinese Simplified -->
{% when '此电邮是由 BrandName1 提供的服务。' %}custom code
<！-- email template for Chinese traditional -->
{% when '本電子郵件是 Picsart 提供的服務。' %}custom code
<！-- email template for English -->
{% when 'This email is a service from BrandName2.' %}custom code
<！-- email template for Russian -->
{% when 'Это служебное письмо от BrandName2.' %}custom code
<！——邮件模板葡萄牙——>
{% when 'Este email é um serviço de BrandName2.' %}custom code
<！-- email template for Arabic -->
{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}custom code
<！-- email template for Japanese -->
{% when '本メールはBrandname2から送信されています。' %}custom code
<！-- email template for Spanish -->
{% when 'Este correo electrónico es un servicio de BrandName2.' %}custom code
<！-- email template for Chinese Simplified -->
{% when '此电邮是由 BrandName2 提供的服务。' %}custom code
<！-- email template for Chinese traditional -->
{% when '本電子郵件是 Brandname2 提供的服務。' %}custom code
{% else %}custom code for ELSE option
{% endcase %}
{{content}}
<！-- here goes the footer for every brand -->
{% case footer %}
<！-- email template for English -->
{% when 'This email is a service from BrandName1.' %}custom code
<！-- email template for Russian -->
{% when 'Это служебное письмо от BrandName1.' %}custom code
<！——邮件模板葡萄牙——>
{% when 'Este email é um serviço de BrandName1.' %}custom code
<！-- email template for Arabic -->
{% when 'هذا البريد الإكتروني خدمة من Brandname1.' %}custom code
<！-- email template for Japanese -->
{% when '本メールはBrandname1から送信されています。' %}custom code
<！-- email template for Spanish -->
{% when 'Este correo electrónico es un servicio de BrandName1.' %}custom code
<！-- email template for Chinese Simplified -->
{% when '此电邮是由 BrandName1 提供的服务。' %}custom code
<！-- email template for Chinese traditional -->
{% when '本電子郵件是 Picsart 提供的服務。' %}custom code
<！-- email template for English -->
{% when 'This email is a service from BrandName2.' %}custom code
<！-- email template for Russian -->
{% when 'Это служебное письмо от BrandName2.' %}custom code
<！——邮件模板葡萄牙——>
{% when 'Este email é um serviço de BrandName2.' %}custom code
<！-- email template for Arabic -->
{% when 'هذا البريد الإكتروني خدمة من Brandname2.' %}custom code
<！-- email template for Japanese -->
{% when '本メールはBrandname2から送信されています。' %}custom code
<！-- email template for Spanish -->
{% when 'Este correo electrónico es un servicio de BrandName2.' %}custom code
<！-- email template for Chinese Simplified -->
{% when '此电邮是由 BrandName2 提供的服务。' %}custom code
<！-- email template for Chinese traditional -->
{% when '本電子郵件是 Brandname2 提供的服務。' %}custom code
{% else %}custom code for ELSE option
33 Comments