The Zendesk Signature for Agents

Q: Can each agent have a different signature?

Yes. The admin template includes `{{agent.signature}}`, and each agent fills their own text into that slot from their profile.

Q: Can I use different signatures for different brands?

Yes, with a Liquid conditional on `ticket.brand.name` inside the signature. Match the brand name exactly or the fallback branch takes over.

A small setting that appears at the bottom of every email you send. Which is exactly why the mistakes in it are so expensive.

Start free trial All guides

The Zendesk signature in two layers

Zendesk signatures work as a template plus a personal part.

An admin sets one signature template for the account, in the agent settings area of Admin Center. Every agent inherits it. Inside that template you place {{agent.signature}}, and each agent fills in their own text under their profile settings, which drops into that slot.

So the company controls the structure and the agent controls the personal line. Set the template once, tell agents where their bit goes, and you never have to police thirty individual signatures again.

If you skip the template entirely, agents just get whatever they typed into their profile, formatting and all. Some accounts run that way. It shows.

Placeholders worth using

The signature field accepts placeholders, which is what makes a shared template workable.

`{{agent.signature}}` is the important one. It pulls in the agent personal signature from their profile.

`{{agent.name}}` and `{{agent.first_name}}` for the name. First name only reads warmer in most consumer support, full name in enterprise.

`{{agent.role}}` if job titles genuinely mean something to your customers. Often they do not.

Placeholders are case sensitive and a typo fails silently, leaving a blank line where the name should be. Send yourself a test ticket after any change. Every time, not just the first time.

The full list of what is available is in the Zendesk placeholders guide, and it is worth skimming before you invent a workaround for something that already exists.

Different signatures per brand

One account, three brands, three different sign-offs. The signature field supports Liquid, so you can branch on the ticket brand rather than maintaining separate accounts:

{% if ticket.brand.name == "Acme Support" %}
The Acme Support Team
{% elsif ticket.brand.name == "Northwind Help" %}
Northwind Customer Care
{% else %}
{{agent.signature}}
{% endif %}

Match the brand name exactly, including capitalisation, or the else branch quietly wins and nobody notices for a month. There is more on the syntax in the Liquid markup guide.

The same trick handles language. Branch on the ticket locale and your German customers stop getting an English sign-off under a German reply.

The formatting traps

Signatures cause more email ugliness than any other single setting.

Length. Every reply quotes the previous one. A six-line signature after ten exchanges is sixty lines of repeated boilerplate the customer scrolls past to find your answer. Three lines is plenty.

Images. Logos need to be hosted somewhere public, and plenty of mail clients block remote images by default, so your careful branding arrives as a broken icon. A text sign-off never breaks.

Legal disclaimers. If compliance insists, push them into the email template rather than the signature, so they sit once at the bottom of the message rather than repeating inside every quoted reply.

Notes. Signatures apply to public replies, not internal notes. Agents who paste a manual sign-off into notes are adding noise nobody needs.

Channels. Email is where signatures belong. In chat and messaging they read strangely, and behaviour there differs, so check the current Zendesk docs for how your channels handle it.

If the signature is longer than most of your replies, it isn't a signature. It's a letterhead.

FAQ

Frequently asked questions

Can signatures differ per brand?

Yes, with Liquid. A Zendesk brand signature is a conditional in the account-level Zendesk email signature, and a Zendesk signature placeholder pulls the agent's name and title into it.

Where do I change my Zendesk signature?

Your personal signature lives in your own profile settings. The template that wraps it's set by an admin for the whole account, so if the format is wrong for everyone, that's where to look.

Can each agent have a different signature?

Yes. The admin template includes {{agent.signature}}, and each agent fills their own text into that slot from their profile.

Can I use different signatures for different brands?

Yes, with a Liquid conditional on ticket.brand.name inside the signature. Match the brand name exactly or the fallback branch takes over.

Why is my signature placeholder showing as blank?

Almost always a typo or wrong capitalisation in the placeholder, or an agent who never filled in their profile signature. Placeholders fail silently rather than erroring.

Do signatures appear on internal notes?

No, only on public replies. That's deliberate, and it is the correct behaviour.