If you've set up your Zendesk to support multiple brands, you might want to ensure that proper branding is included in all of your outgoing messages. That might mean the voice of any statements made, different contact information or brand names, or different logos, colors, and other styling.
First, you need to remove any branded information from your email template, because you get only one email template per account. Next, use triggers to create specially branded notifications.
Removing branded content from your email templates
Your email template is the skeleton of every email sent by your Zendesk to your customers. It's the structure used to determine where the major parts of each notification are located. The default Zendesk email template doesn't show any of your brand's information, so if you want to be sure you aren't putting any branded info in notifications, you can always revert to the default template.
However, you can also add content to it. Some Zendesk accounts have created custom footers, added logos, or provided helpful text. This is obviously an advantage of an email template. But, if you are supporting multiple brands, you shouldn't put brand-specific information in the template, because that email template is applied to all messages, regardless of brand.
There are a few things to think about if you've set up an additional brand. Take a glance at your email template to see if any of these apply to you:
- Colors -- You should avoid any colors that are specific to one of your brands. The default template colors are all in gray, so they should be fairly neutral.
- The Footer -- Many people remove the Zendesk branded footer from the email template -- {{footer}}{{footer_link}} -- which is fine. However, if you've added your own footer, make sure it doesn't have brand names, phone numbers, or messaging that's inappropriate for some brands.
To edit your email templates, see Customizing your email templates.
Branding your emails using triggers
Even though your template can't be branded, you can use triggers to send different messages depending on the brand of the ticket. Triggers enable you to use conditions to create a fully branded suite of messages.
In this example, we'll set up a notify requester of comment update trigger and differentiate it for two brands.
To set up your branded triggers
- In Admin Center, click the Objects and rules icon (
) in the sidebar, then select Business rules > Triggers.
- Find the Notify requester of comment update trigger, then click Edit.
- Add the condition [Brand] [Is] [Acme], then click Save.
- Hover your mouse over the trigger you just modified, then click Clone.
- Change your cloned trigger so that the brand condition matches your second brand, in this case Brand-X, then click Save.
At this point you have two functional triggers with nothing different about them. From here you can differentiate the brands. - Edit the Notify trigger action in your new trigger and update the message with whatever needs to be changed for your brand.
For example, this is the message that Acme sends to customers when they receive a notification of an updated ticket:
An update was made to your ticket by one of our Acme support reps. You can reply to this email if you need more information or reach during business hours by phone at +1-888-123-4567.
To support Brand-X, you can update the phone number and brand name to create an alternate version:
An update was made to your ticket by one of our Brand-X support reps. You can reply to this email if you need more information or reach during business hours by phone at +1-888-765-4321.
You can go a step further by adding logos using HTML. For example, Acme can add their corporate logo to their emails. Because they've created multiple triggers, they can now brand each one differently.
You can use HTML to do more than just add logos, too. With this method You can impart the correct voice, wording, information, and styles into each of your outgoing messages.
Fixing ticket links for multiple Help Centers
When you create multiple brands, you have the option to create multiple Help Centers. Each Help Center enables your customers access to the tickets they've opened and are CC'd on for that brand only. This means that each Help Center has its own unique branding, and, when viewing tickets, the branding and the ticket match.
One downside to this is it means that if a brand has no Help Center (an option you can choose if you prefer to do email only support for a brand) then email notifications with ticket links will be broken.
You can use the process above to correct for this. If you choose to have one or more brands with a Help Center and one or more without a Help Center, you need to create separate triggers for these brands. Include the {{ticket.url}} placeholder in the former but not in the latter.
For example, here's a trigger for a brand with a Help Center.
And here's a trigger for a brand without a Help Center.
20 comments
Automate My Store
Hi Fernando Mendes, Andrea Rodriguez (CD Baby), m.diani, Jason Wong,
since we also have multiple brands, we were dealing with the same issue.
We created an app for us to solve this issue once and for all. If you want it too, check it out here: https://www.zendesk.com/marketplace/apps/support/261269/select-email-sender-address/
Here are some features we integrated:
- Automatically use the correct email sender, depending on the agent's user group
- Restrict sender email based on user-agent group
- Warn the user when submitting a ticket with the default address, if the default address is not allowed for his group
- Based on your sender address, specific Tags will automatically be added
- Search for the support address associated with your ticket
- Easy & fast – you don't need to scroll through the Dropdown
Feel free to try it for 30 days for free: https://www.zendesk.com/marketplace/apps/support/261269/select-email-sender-address/
If you want to automatically apply the correct brand signature to all of your emails you can check out:
0
Hiedi Kysther
Hi Hannah,
We may be able to find a workaround for that, but we'll need to review a few ticket samples. I'll create a ticket on your behalf so we can discuss this further. Please check your email for more information!
0
Hannah Lucid
Hi Heidi,
Thank you for this information. Unfortunately, this isn't what I meant.
Our support teams support our internal employees, however, there may be exceptions where our support teams deal with outside sources. We want to put a disclaimer on our notifications that would only be visible or send when our support team is responding to someone within our organization. Is this possible?
0
Hiedi Kysther
Hi Hannah,
Could you expound more about the notification disclaimer you are pertaining to? Are you referring to Email notification agents receives? For example, "Notify group of assignment"? If yes, you can add the disclaimer to the email notification.
0
Hannah Lucid
Hi! Is there a way to hide a notification disclaimer from users outside of a specific email domain? (example: @google.com or @company.com)?
We want to place a disclaimer for our internal employees, reminding them not to share the information with outside resources since our Support team is B2E support, but we don't want this to be visible to individuals outside our organization. Is this possible?
0
Florian - SEIF Partner
Nous avons mis en place une application qui vous permet de créer en quelques clics un design personnalisé ===> Email Crafter Disponible sur le marketplace
1
Florian Kunz
Wir sind den obigen Ansatz gefolgt und haben jetzt in unseren Auslösern und Automatisierungen einige Zeilen Html ergänzt. Wir sind deutlich über ein einfaches Logo hinausgegangen.
Leider geht der Artikel nicht auf den Absendernamen ein bzw. wie man diesen sinnvoll ändern kann. Wir zeigen im Moment nicht unseren Agentennamen. Ich bin hier noch mit dem Alias des Agenten am Spielen, aber der ist leider immer fix. Mal schauen, was wir hier finden werden.
0
Christophe A.
Nativement, je crains que les options soient limitées sur ce point pour l'instant.
Nous disposons par contre de quelques applications sur le marketplace (Marketplace) qui pourraient vous aider à créer ces modèles de manière à éviter de dépasser cette limite d'octets. Certaines semblent conçues pour personnaliser vos modèles de courrier en fonction des marques. N'hésitez pas à contacter les développeurs de ces applications pour vous assurer qu'elles répondent à votre besoin.
0
Alexandre DEUEZ
Bonjour Christophe,
Merci de votre réponse.
Cependant, les balises HTML utilisées dans les contenus dynamiques ne sont pas interprétées lors de l'envoi de mails, ce qui constitue le gros de notre template.
Une autre solution?
0
Christophe A.
Il y a effectivement une limite de taille sur les modèles d'emails des déclencheurs, principalement dans le but d'éviter les conflits possibles avec d'autres fonctionnalités.
Une solution pour contourner cette contrainte est d'utiliser des contenus dynamiques.
Vous pouvez créer du contenu dynamique auquel vous faites ensuite référence par le biais de marqueurs dans vos déclencheurs. Cela devrait alléger votre modèle d’e-mail.
En espérant que cela aide :-)
0
Sign in to leave a comment.