Customizing your email templates

Fastpath: Admin > Channels > Email

All the email notifications sent from your Zendesk are formatted for both HTML and plain text emails. Both formats are included in each email. The version end-users see depends on the preference settings of their email clients. You can customize the HTML template to match your branding by making a few simple style changes. You can also edit the information in the text versions of your emails.

The look and feel of the emails are controlled by an HTML template and a text template.

To edit the email templates

1. Click the Admin icon () in the sidebar, then select Channels > Email.
2. Modify the email templates.

   If you need help, see the following topics:

   • Editing the HTML template
   • Editing the text template
3. If you want to start over with the unmodified version of the template, click the Revert to Default link below the template.
4. Click Save.

In addition to customizing the email templates, you can change emails as follows:

• Show user profile photos
• Add or remove ticket links
• Edit the delimiter text
• Use Liquid markup

Tip: If you are on Enterprise, you can modify and test email changes in a sandbox before deploying them publicly. See Testing changes in your sandbox (Enterprise).

Editing the HTML template

You can change the appearance of HTML emails by editing the HTML and CSS in the HTML template.

Note: HTML template editing is not enabled by default. To enable editing in the template, send a request (including your subdomain) to [e-mail].

This section covers the following topics:

• Changing the appearance of HTML emails
• Guidelines for customizing HTML emails

Changing the appearance of HTML emails

The HTML template consists of DIV tags and system placeholders.

The placeholders supply most of the content to the email. The following two system placeholders are required and should not be deleted: {{delimiter}}, {{content}}. The {{styles}} and {{attributes}} placeholders are for future use and are sometimes used by the system to inject styles and attributes to support Right-to-Left locales. The {{footer}} placeholder is optional. No other placeholder can be used in the template. For more information, see Understanding the system placeholders.

The DIV tags apply CSS styles to the content. By adding or modifying CSS styles, you can change the look and feel of the email as a whole, the delimiter, or the footer.

To edit the styles in the template

1. Click the Admin icon () in the sidebar, then select Channels > Email.
2. Scroll down to Email Templates.

   

3. Make your changes.

   If you want to use any of the standard template placeholders, start typing the placeholder name, then choose from the available options that appear.

   

4. Click Save when you're finished.

For example, here's how to change the font color of the footer to teal:

...
 <div style=" color: #009966;
              margin: 10px 0 14px 0;
              padding-top: 10px;
              border-top: 1px solid #eeeeee;" >
    {{footer}}{{footer_link}}
  </div>
...

The font color is set to teal's hexadecimal value with the following style declaration:

color: #009966;

Note: The color of links can't be customized. Links are styled with CSS pseudo classes such as :hover. Example: a:hover {color:#FF00FF;}. Unfortunately, CSS pseudo classes are not supported in inline CSS, and major email clients like Gmail strip out any CSS that is not inline.

To add an image such as a company logo to the template, insert an IMG tag that references the image. Example:

<img src="http://YOURWEBSITE.com/logo.png"/>

Note: Before adding logos and other images, remember that most email clients don't display images by default.

If you want to add a hyperlink to the logo, enclose the IMG tag in an anchor tag, as in this example:

<a href="http://YOURACCOUNT.zendesk.com"><img src="http://YOURWEBSITE.com/logo.png"></a>

For more information, see the following resources:

• CSS portal on the Mozilla Developer Network
• Help Center CSS Cookbook

Guidelines for customizing HTML emails

You can customize the HTML template extensively. However, keep in mind that designing HTML emails is hard because of the way HTML and CSS are rendered in different web browsers and email clients. Certain types of formatting can even be interpreted as spam. In general, keep your customization as simple as possible and follow these guidelines:

• Do not use CSS3 style declarations. Stick to CSS1 or 2.
• Do not add more DIV sections.
• Do not use <style>...</style> to apply styles. Most email clients strip out the tag.
• Keep text formatting to a minimum. Lots of bold text can trigger spam filters.
• HTML5 is not yet supported, so don't use it.
• Don't add lots of images (another trigger for spam filters) and downscale the images that you do use.
• Use the ALT tag on all images. The tag displays a description of the image before users allow the images to be displayed.
• If you know the width and height of the image, define it. This forces the email client to reserve the image space in the layout of the email before the images have been downloaded.
• Background images are not supported in all email clients, so don't rely on them for information or functional design.
• Don't link to images in a closed Zendesk. If the intended recipient is not a registered and signed-in user, the images will be broken.

Editing the text template

The text template is used when the user elects not to read email messages in HTML format. To edit the text template, open the Email channel settings page and scroll down to Email Templates. Make sure to click Save when you're done.

The text email template consists of two system placeholders:

{{content}}

{{footer}}

The {{content}} placeholder inserts the text delimiter, the ticket title, the text that is generated from business rules (triggers, automations, or macros), and the ticket comments. The {{footer}} placeholder is optional. You can remove it if you want. For more information, see Understanding the system placeholders.

Note: The {{delimiter}} placeholder is not required in the text template. The {{content}} placeholder contains the delimiter text.

If you'd like to add a line to your emails, simply add it to the template.

Thanks for contacting MondoCam Support!

{{content}}

{{footer}}

Showing user profile photos in HTML emails

To show user profile photos next to ticket comments in HTML emails, select the Show User Profile Photos in Emails option on the Channels/Email page.

Be aware of the costs and benefits of displaying profile photos. On the positive side, pictures lead to a more personal experience for your customers. On the negative side, most email clients don't display images by default.

The emails display the photos from Zendesk account profiles or from Gravatar. If you want to display your company logo next to ticket comments, upload it to Zendesk as your profile photo. Make sure the image size ratio is 1:1. The recommended size is 200x200px.

Note: The various rendering engines used by mail clients and web browsers may affect the quality of the images.

Adding or removing ticket links in emails

Your email notifications can provide a link back to the ticket being discussed. Example:

This type of link is defined in a trigger or automation, not in the template. For example, most of the default triggers have an action that sends an email notification with a link to a ticket. If you provide support with email only, you don't want customers to see a link to a ticket that would prompt them to log in. In this case, you must edit your triggers or any other business rules that generate email notifications.

To add or remove a ticket link in a notification trigger or automation

1. Click the Admin icon () in the sidebar, then select Triggers or Automations.
2. Locate the notification trigger or automation and select Edit.
3. Modify the action or actions as needed.

   The following placeholders insert ticket links in the email body: {{ticket.link}} or {{ticket.id}}.

4. Click Update.

For more information on editing triggers to remove ticket links, see Removing tickets links from your notifications.

If you provide support through email only, see Setting up to provide email-only support. The article describes how to remove links back to your Help Center that would prompt your end-users to attempt to sign in.

Editing the delimiter text

The text in the email delimiter is used to inform the email recipient that any text entered into a reply must be above a certain line in the email.

When the recipient's reply is received in Zendesk, the delimiter is used to separate old content from new. The new content is added to the ticket as a comment.

Note: You cannot remove the delimiter from the email template. Without a delimiter, any text typed below it would not appear in the ticket.

Even though you cannot remove the delimiter, you can customize your delimiter's text and font size, color, and type.

Editing the delimiter text

1. Go to Admin > Channels > Email.
2. In the Mail Delimiter section, enter a personalized delimiter that's between 20 to 65 characters long.
3. Click Save.

Your delimiter can also support multiple languages if you use the {{txt.email.delimiter}} placeholder. The text in the delimiter is drawn from the translations provided for the languages supported in Zendesk. The language shown in the email message is based on each user's language preference. This is a convenient way to support different languages in your email template. However, it also means that you have no control over the words in the translated versions of the delimiter.

Note: If your users don't have a language preference selected, as is the case with unverified users in a Zendesk set up for email-only support (see Setting up to provide email-only support). The delimiter is displayed in your primary (default) language.

Editing the delimiter font size, color, and type

You can edit your delimiter font size, color, and type in your Email template HTML. Your edits should be on the same line as the placeholder. Do not make these changes on any other line as it will affect the rest of your text.

For more information on customizing text see, Jordan Wheelock's support tip Changing your email template content fonts and Ben Lucier's community tip, A better email template for Zendesk.

Using Liquid markup

Liquid markup does not work in the email templates. It only works in the business rules (triggers, automations) that generate the email notifications.

If you want to use Liquid markup to have more control over the content of email notifications, see Using Liquid markup to customize comments and email notifications.

Understanding the system placeholders

Most of the content in notification emails is generated dynamically by the Zendesk system. The dynamically generated content is represented by placeholders in the email templates. The placeholders are enclosed in double curly quotes, such as {{footer}}.

The placeholders insert delimiter text, the email contents, and a footer.

{{delimiter}}

Displays the line "##- Please type your reply above this line -##". The delimiter is used by the system to separate old content from new. When a person replies to an email, the new content in the reply is added to the ticket as a comment. This placeholder is required in the HTML template. For more information, see Editing the text in the mail delimiter and supporting other languages.

{{content}}

Displays the email content, which can include ticket comments and user profile photos. The content is defined in the trigger, automation, or anything else that sends email from your account. See Creating and managing triggers for ticket updates and notifications.

{{footer}}

Optional. Displays the line "This email is a service from YourZendeskName." It also displays ticket properties, such as status and requester, in emails sent to agents. The properties are not displayed in emails sent to end-users. The list of properties can't be customized at this time.

{{footer_link}}

Optional. Displays the line "Delivered by Zendesk". The word Zendesk is a link to http://www.zendesk.com.

{{styles}}

Optional. For future use. Currently, the system uses this placeholder to inject styles when it detects that the locale is a Right-To-Left locale.

{{attributes}}

Optional. For future use. Currently, the system uses this placeholder to inject attributes when it detects that the locale is a Right-To-Left locale.