You can specify an agent signature in all public ticket comments and outgoing messages when the agent responds using the agent interface. This signature will not appear if the agent responds to a ticket by email. An administrator can add a common signature for all agents on the account. If you're using multiple brands in Zendesk Support, an administrator can also add brand information to the signature. An agent can add a personalized signature.
You can use some placeholders in the signatures. Placeholders are references to agent and other data stored in Zendesk Support. Example: {{agent.email}}
. The following classes of placeholders are supported in signatures : "agent", "current_user", "account", and when used as HTML, "dc" (for dynamic content). The "ticket" placeholder class (such as {{ticket.assignee.name}}
) is not supported. For a list of placeholders allowed in agent signatures, see Zendesk Support placeholders reference: Agent data.
For general information on placeholders, see Using placeholders.
This article contains the following sections:
Adding a common agent signature and branded signatures
An administrator can add a common signature for all agents on the account. For example, you can include your company name and tagline in all ticket comments and outgoing email notifications.
Multibrand users (Suite Growth and above or Support Enterprise) can create a custom signature for each brand. This does not override the agent's personal signature, it simply adds brand-specific information to it. When you create branded signatures, make sure you've also set up your email template for multiple brands to ensure the branded signatures are included in your outgoing messages (see Using the email template with multiple brands).
To add a common agent signature (Suite Growth and above or Support Enterprise)
- In Admin Center, click the Workspaces icon (
) in the sidebar, then select Agent tools > Agent interface.
- In the Signature text box, enter the signature text and any placeholders.
{{agent.signature}} Love your Zendesk
- If you want to let agents add their own signature or add personal information to the common signature, include the
{{agent.signature}}
placeholder. It's included by default. See Adding a personal agent signature.
To add branded agent signatures
- In Admin Center, click the Account icon (
) in the sidebar, then select Brand management > Brands.
- Expand the brand you want to update.
- In the Agent signature text box, enter the information you want to include in that brand's signature. You can enter the information above or below the agent signature placeholder:
- Click Save changes.
- Repeat as needed for your other brands.
Adding a personal agent signature
As an agent, you can add a personal signature to all your ticket comments and outgoing email notifications. The signature can include any text such as your name and position, your group, contact information, and so on. Agents can use Markdown for advanced customization (see Formatting text with Markdown).
To add a signature
- In Zendesk Support, click your user icon in the upper-right corner and select View profile.
- Under Signature in the left sidebar, enter the signature text and any placeholders.
Regards, Jane Tolland Customer Care Associate {{agent.email}}
25 Comments
Should I be able to use Ticket Organization Custom Fields in Brand Signatures?
I am trying to get the brand signatures to include something like "You are on a Free Support Plan, see our website for details." Where the Free portion is replaced by the appropriate value found in a dropdown in the ticket's organization.
I tried using {{ticket.organization.custom_fields.support_plan.title}} where support_plan is the field key, but nothing is populated. I even tried {{ticket.organization.name}} and it didn't populate.
Hi Grant,
Unfortunately, the ticket placeholder class is not supported in agent signatures – as the article above states:
"The following classes of placeholders are supported in signatures : "agent", "current_user", "account", and when used as HTML, "dc" (for dynamic content). The "ticket" placeholder class (such as Dave Dyson) is not supported. For a list of placeholders allowed in agent signatures, see Zendesk Support placeholders reference: Agent data."
Perhaps you can add the information you're wanting to do in a macro, or in the trigger email notification body instead?
I was trying to do exactly the same as Paul super helpfully described in this comment: https://support.zendesk.com/hc/en-us/articles/203691076/comments/204241858
But was pulling my hair out trying to get it to work. The parameter may have changed in the last 6 years! (haha) but I found that to use custom user fields in the signature, you now have to use:
(Where 'fieldkey' is the field key created when configuring the custom user field... and also note the 's' at the end of fields which now appears to be required!)
Thanks, Tim!
Thank you for solution
Hello! We have enterprise support and we are looking to customize our agent signature. We have multi-brand enabled as well. We would like to add each brand logo to the agent's signature. If our logo is hosted in our help center on Zendesk. How do we add it to the agent's signature?
Hey there @...!
With that logo hosted in your help center: You're all set to right-click on on that specific image while viewing your help center, and then click on "Copy Image Address" or "Copy Image URL". The copied URL will likely begin with something like this: "https://theme.zdassets.com/theme_assets/..."
With that URL ready to go, you can display that image in your agent signatures using Markdown formatting just like this, where you can choose to display that image as-is or make it a clickable link.
Thanks again for reaching out Jennifer, and let us know if you need anything else!
hi @... make a try with this : https://www.zendesk.fr/apps/support/signsolvr/
@... Thank you for the suggestion, however, we are not looking to purchase an app to solve this issue. We would like to do it natively in Zendesk.
@... - Thank you for your help! I added it to the agent signature block under the brand and it showed up in the ticket, but it didn't show up in gmail. Can you tell me why? The file size is 15.3 kB.
Thank you!
Hi there. How do I prevent agents from personalizing/adding to their own signatures?
I've been an admin of ZD for years, but I just switched companies, and I don't know why this is stumping me!
We have a common signature (not agent ones yet), and I thought it would be appended to all email notifications sent out via automations as well (such as, "your ticket has been pending for 2 days.") But it seems to only go out on email notifications that contain a new public comment directly from an agent.
"An administrator can add a common signature for all agents on the account. For example, you can include your company name and tagline in all ticket comments and outgoing email notifications."
^ Since this says "and outgoing email notifications" I would've expected that to include automations as well.
Hey Sara Silva & Nikki -
Thanks for writing in! Sara - for your question you can disable agent signatures by following these steps. Unfortunately Zendesk doesn't have the option to restrict an agent from editing their own signature at this time, but this should at least allow you to standardize it.
Nikki - As you've noted above, the common signature is for all of the agents. Since the automations are sent from the system versus an agent, this common signature would not be included. That said, you could work around this by including your common signature in the comment/description of the automation itself, thus bypassing the need to integrate the existing one. Hope this helps!
Brandon Tidd
729 Solutions
Hey Brandon,
Thank you very much for your help!
I'd like to request/suggest adding HTML Signatures for agents. It seems like this would be the simplest and easiest way to format individual signatures with logos or images.
Here's the best thread in our product feedback forums to upvote and add your use case to: Feature Request: HTML or Rich Text Editor for Signatures
I can't seem to find any way to disable the brand level signatures for the SMS channel? Is there one?
Here's a workaround that may work for you -- by replacing the native Zendesk signatures and using this free third-party app, you can use a script that will prevent signatures from being sent in outgoing SMS messages: How do I remove the agent signature from proactive outbound SMS messages?
In order to achieve the formatting you want, it's probably best to make the entire signature an image and then use the clickable image technique in this article: How can I add a hyperlink or image to my signature? In this case, your image would need to be uploaded to a public image server, or uploaded as an asset to your Help Center – see Using your own theme assets for help center if you want to do the latter.
It is possible to have an image that's above or below some text in your signature -- see Dan Ross' comment here.
Hi, was wonder why added the signature in the View profile is always like a big font, can this changed so its in line with the under text?

@... Thank you Dave, I was able to get the issue resolved, by raising a ticket and the Zendesk agent getting in touch.
Thanks
Can you add colour to text in a user or brand signatures?
Currently, adding colors to our agent signature is natively not supported at the moment. However, they can be edited using Markdown allowing you to use italics and bold as well as adding pictures and hyperlinks to the signatures. You can find more information about how to use markdown on Zendesk here: Formatting text with Markdown. You may also consider editing your email templates per brand to uniquely present your brands in addition to signatures
Additionally, we want to take this opportunity with you to share this article that might help you in the future to know when you can use HTML and when you can use Markdown in Zendesk: Where can I use Markdown and HTML in Zendesk Support?
We hope this information helps!
Is there any way to have the personal agent's signature overwrite the common agent's signature?
Please sign in to leave a comment.