With dynamic signatures in Zendesk, you can show contact details and closing lines that match the service request. Your billing team can use a different phone number from technical support, and VIP customers can receive an additional contact option. First, decide where the signature should be created: in an agent profile, for a brand, or through a rule that uses ticket information.
This guide explains the differences and provides a group-based email signature configuration example with a default for all other groups.
How to change your Zendesk signature
A personal agent signature adds details such as your name, role, or phone number to your replies. In Zendesk Support, click your user icon, select View profile, and edit the Signature field. Your common or branded signature must include {{agent.signature}} for this personal text to appear. See Zendesk’s guide to adding an agent signature.
| Your requirement | Where to configure it | What to consider |
|---|---|---|
| Each agent’s name and contact details | Personal agent signature | The common signature must include the personal signature. |
| Consistent identity for each brand | Branded signature | Brand availability and related features depend on your Zendesk plan. |
| Different contacts by ticket group or customer segment | Liquid in a macro or a ticket trigger’s email action | Ticket conditions need a context that supports ticket data. |
| Reusable text in several languages | Dynamic content | Zendesk selects an active language variant using the requester’s language. |
Do not put ticket placeholders directly in the agent signature field. Zendesk supports the agent, current_user, account, and dc placeholder classes there, but not ticket placeholders. Its recipe for Liquid in agent signatures explains this limit. Referencing dynamic content does not automatically remove that restriction.
When dynamic signatures help
- By responsibility: Billing requests show the billing team’s contact details, while technical questions show the support contact.
- For VIP customers: A maintained customer or organization attribute determines whether an additional contact option appears.
- By customer segment: The message includes a personal contact or the general support address.
- For the time of the reply: A Friday closing can wish customers a good weekend. Date and time zone handling must match your intended rule.
- With relevant extra information: A newsletter link appears only when the required subscription information is available.
These conditions need reliable data. Missing VIP information or a new group should therefore lead to a deliberately chosen default.

Set up group-based signatures with Liquid
This example for a manually applied macro uses the ticket group to choose an email address and phone number. It illustrates the approach with sample data; replace the group names and contact details before using it. Put the code in the macro’s comment/description action, rather than in the agent signature field or the global HTML email wrapper.
1. Define groups and a default
Decide which contacts to use for Sales, Support, and Press. The example uses the documented ticket.group.name placeholder, so names must match your groups exactly. Check them in Admin Center under People → Team → Groups or through the Zendesk Groups API. If you rename a group, update the conditions too.
2. Include a fallback for other groups
The else branch provides the fallback: tickets outside the named groups receive the general support contact details.
Kind regards,
{{current_user.name}}
{% if ticket.group.name == 'Sales' %}
sales@example.com
+49 30 12345-100
{% elsif ticket.group.name == 'Support' %}
support@example.com
+49 30 12345-200
{% elsif ticket.group.name == 'Press' %}
press@example.com
+49 30 12345-300
{% else %}
support@example.com
+49 30 12345-200
{% endif %}
3. Apply the macro at the right moment
Choose the ticket group before applying the macro. Once inserted, the comment is text and will not automatically change if the group changes later. Check the signature again in that situation. An existing agent signature must not add the same details a second time.
{{current_user.name}} identifies the user making the current update. In this manually applied macro, that is the agent. Do not reuse it unchecked in automatic notifications, where an end user or the system may have triggered the update.
What the result could look like
Kind regards,
Fred Parker
support@example.com
+49 30 12345-200
Sample output for the Support group; the name and contact details are fictional.
4. Use a ticket trigger for automatic output
To generate the signature automatically when sending an email, use the relevant email action in a ticket trigger. Define which public agent replies should receive it and retain the existing comment output. The signature logic adds to the message rather than replacing it. Check the sender context and duplicate signatures separately. For the underlying logic, see Zendesk’s introduction to Liquid markup.
Use dynamic content for multilingual signatures
Under Workspaces → Agent tools → Dynamic content, create reusable text items and their language variants. Zendesk generates placeholders, for example {{dc.signature_email}} and {{dc.signature_phone}}. Copy the actual placeholders shown in your account. Language selection is handled by Zendesk; selecting content by ticket group requires a separate condition.
Use these items in the appropriate macro or ticket trigger and test them in that context. Updating a central item does not rewrite comments that have already been inserted or sent. Zendesk explains setup and language variants in providing multiple language support with dynamic content.
Zendesk signature formatting, links, and logos
For links and images in agent signatures, use Markdown. A logo needs a publicly accessible image address, for example from your help center assets. Use a direct image URL and check the email actually received by the customer. A file saved only on your computer is not enough. Zendesk provides the syntax in adding a hyperlink or image to a signature.
HTML and Markdown are not interchangeable. Ticket trigger email actions and the global email wrapper have different capabilities from the signature field. The global wrapper also uses its own placeholders. See Zendesk’s Markdown and HTML overview for supported locations. For ticket values, use the business rule placeholder reference and the guide to using placeholders.
Maintain a large signature content library
If you manage many text items and language variants, our Dynamic Content Manager helps you maintain them. It shows missing or outdated variants, references to placeholders in macros and rules, and a preview for each variant, including HTML. Our feature overview explains these capabilities. The preview helps with content maintenance; also test delivery and the email received by the customer.
For messages to other departments or service providers, our Side Tickets app also supports signatures. This applies to messages created through the app, a separate use case from signatures for regular ticket replies described here. See the Universal Toolkit feature overview for details.
What to test before rollout
- Groups and fallback: Test every configured group and an additional or newly created group.
- Languages and brands: Check active language variants, default text, and the correct brand assignment.
- Missing values: Test empty phone numbers, missing customer attributes, and tickets without an assigned agent.
- Sender and timing: Compare a manually applied macro, a public agent reply, and a system update. Check a group change after inserting the signature.
- Received email: Review line breaks, logos, links, and duplicate signatures on desktop and mobile. Also check that internal notes do not trigger an unintended customer email.
Consistent signatures that fit your workflows
A well-configured signature rule saves manual edits and keeps contact details consistent across teams and brands. At Leafworks, we help you include these rules in your Zendesk automation. Our automation page includes more workflows and examples.


