Question
How can I set up different agent signatures to appear in email notifications based on the brand and ticket group?
Answer
You can set up different signatures for each brand and ticket group by cloning your email triggers so that one version per brand exists. In each trigger, use liquid markup to show different signature text depending on the group.
Disclaimer: This article is provided for instructional purposes only. Zendesk does not support or guarantee the code. Post any issues you have in the comments section or try searching for a solution online.
To modify your email triggers and use liquid markup:
- Open the following standard triggers:
- Notify requester of new proactive ticket
- Notify requester and CCs of comment update
- Create clones of each trigger for all of your brands.
- Rename each cloned trigger by adding your brand name to the Trigger name field.
As a best practice, deactivate the original trigger. - In each trigger, define the brand by adding the Condition:
-
Ticket > Brand | Is | Your brand name
-
Ticket > Brand | Is | Your brand name
- In the Email body field, after any existing text, add liquid markup to show your signature per group. For example:
{% case ticket.group.name %} {% when 'Group A' %} Write your signature text for Group A here. {% when 'Group B' %} Write your signature text for Group B here. {% when 'Group C' %} Write your signature text for Group C here. {% else %} Write your signature text for anything that doesn't have a group here. {% endcase %}
In the example above, replaceGroup A
,Group B
andGroup C
with your group names. ReplaceWrite your signature text...
with the signature text of your choice. -
Save your changes in each version of your trigger.
- Test your new workflow in a ticket. The signature will not appear on tickets; however, end users will see it in their email notifications.
Important: Do not remove existing placeholders or conditions from your standard triggers. Standard triggers send emails to your end users from tickets.
For more information, see these articles: