How to Set Up Freshdesk Email Signatures

The three layers of signature in Freshdesk

Before touching any settings, it helps to know that a Freshdesk reply signature can come from three sources, and they stack in ways that surprise people.

The first is the personal agent signature, which an individual agent owns and edits themselves. The second is the admin-set agent signature, the same field but filled in by an admin while creating or editing that agent. The third is the Agent Reply Template, a single global block that sits at the bottom of every agent's outgoing reply regardless of who they are. The Dynamic Signature app is a fourth, optional layer that automates all of this with placeholders and conditions.

The trap to remember up front: if you fill in both a personal signature and the global Agent Reply Template, Freshdesk can append both, and customers get your sign-off twice. Pick one layer as the source of the actual signature and keep the other minimal.

Step 1: Set a personal agent signature

This is the fastest path and the one most agents will use. Per Freshworks' email signatures documentation, an agent sets their own signature from their profile.

1. Click your profile picture at the top-right corner of Freshdesk.
2. Choose Profile Settings.
3. Scroll to the Signature field.
4. Compose your signature in the rich-text editor — you can Bold, Italicise, underline, change text colour, add links, and insert an image.
5. Save.

From then on, the signature is appended automatically whenever the agent clicks Reply on a ticket. One real limitation to note here: agents cannot paste raw HTML into the signature from Profile Settings — they get the rich-text toolbar, not a code view. Images have to be hosted at a public URL and inserted with the image button, not uploaded as an attachment.

Step 2: Set an agent's signature as an admin

Admins can fill in the exact same signature field on an agent's behalf, which is useful when you're onboarding someone or standardising the format across a team. The catch worth knowing, from the same Freshworks guidance, is that an admin cannot edit another agent's core profile details — but the signature is one of the fields you set while creating or editing the agent.

1. Go to Admin → Agents.
2. Click into the agent you want to edit (or create a new one).
3. Find the Signature field in the agent's details.
4. Compose or paste the signature and save.

If you're doing this at scale — provisioning many agents, assigning roles, and setting signatures as part of the same flow — it's worth reading our walkthrough on how to manage agents in Freshdesk so the signature step slots into a repeatable onboarding routine rather than a one-off.

Step 3: Create a global signature with the Agent Reply Template

If you want the same footer on every agent's replies — a company address, a legal disclaimer, a support-hours line — the personal-signature route means editing it person by person. The Agent Reply Template solves that with one edit for the whole help desk, and crucially, it is the layer that does support HTML.

1. Go to Admin → Workflows → Email Notifications.
2. Open the Templates tab.
3. Click Edit next to Agent Reply Template.
4. Add your shared block — and because this editor exposes a code/HTML view, you can drop in a properly formatted HTML signature here, something Profile Settings won't let you do.
5. Save.

This is the right home for anything that must be identical everywhere, and the wrong home for anything personal. Because it applies to every reply, remember the duplication warning: if agents also carry a personal signature, decide which layer holds the name-and-title block so customers don't see it twice.

Step 4: Go dynamic with placeholders and conditions

The three layers above are static. If you want signatures that change based on who is replying or which group the ticket belongs to — without editing anyone's profile — Freshdesk offers a free Dynamic Signature app on the Freshworks Marketplace. Per the Dynamic Signature integration docs, it pulls agent and ticket data into placeholders.

1. Click the Freshworks Marketplace icon (top-right) and choose Marketplace Apps, or go to Admin → Apps.
2. Search for Dynamic Signature and click Install.
3. The app auto-fills your Freshdesk domain and API key; click Authenticate account.
4. Name your template and build the signature in the editor.
5. Insert placeholders — the app supports Agent name, Agent email, Agent number, Agent title, and Ticket ID — plus a company logo via a public image URL, and a code view for HTML.
6. Set the conditions that decide when this signature applies: by Email, Product, or Group. The signature only fires when all selected conditions match.

Once installed, signatures auto-populate in replies based on your conditions, and a Dynamic Signature icon appears in the reply editor so agents can manually pick an alternative template when they need to.

Which signature method should you use?

The right layer depends on how personal versus how uniform you need each part of the block to be.

A common, clean setup: a short personal signature per agent for the human touch, plus a minimal global Agent Reply Template for the legal disclaimer only — so nothing duplicates and the two layers do different jobs. Teams that lean heavily on templated replies often pair this with canned responses in Freshdesk so the whole reply, signature included, is consistent.

The honest limits — and where an AI layer fits

Freshdesk's native signature tooling is solid for what it is: three predictable layers plus a free app that covers placeholders and conditions. But it's worth being clear about the edges.

The HTML gap is real. Agents editing their own signature in Profile Settings get rich text, not a code view, so a pixel-perfect HTML signature with a banner or button has to live in the Agent Reply Template or the Dynamic Signature app instead — and the two static layers can duplicate if you're not careful. The placeholder set is narrow: name, email, number, title, and ticket ID cover the basics, but there's no native field for, say, the agent's calendar link or a per-region disclaimer unless you build separate conditional templates. And a signature is fundamentally cosmetic — it makes a reply look finished; it doesn't help write the reply or make sure the answer underneath it is correct.

That last point is where an AI agent layer earns its place, and it's worth weighing the build-versus-buy tradeoff before adding one. The broader category of AI agents for customer service exists to do the reasoning-heavy part your signature can't — reading the ticket and drafting the answer. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector, so it never replaces your help desk or its signature settings. You connect Macha to Freshdesk with your subdomain and API key, and it drafts or posts grounded replies into the same tickets — replies that land under whatever signature you configured here, using your existing branding rather than reinventing it. If you want to see how that automation actually works end to end, we cover it in how to automate Freshdesk with AI, and Macha can pull live order or account details into a reply through a custom tool that wraps your own API. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. Credits are consumed per AI action, not per resolution — the pricing page breaks that down.)

The division of labour is clean: let Freshdesk own the signature — the branding and sign-off on every message — and layer an agent on top for the part the signature can't do, which is producing the answer that sits above it.

FAQ

Where do I set my email signature in Freshdesk? As an agent, click your profile picture at the top-right, choose Profile Settings, and edit the Signature field. It's appended automatically whenever you click Reply on a ticket.

Can I add a global signature for all agents at once? Yes. Go to Admin → Workflows → Email Notifications, open the Templates tab, and edit the Agent Reply Template. That block applies to every agent's replies and, unlike Profile Settings, supports an HTML/code view.

Why does my signature appear twice? Because two layers are both active. If you set a personal signature and a signature in the Agent Reply Template, Freshdesk can append both. Keep the full name-and-title block in only one layer and use the other for something minimal, like a disclaimer.

What dynamic placeholders can I use in a Freshdesk signature? Through the free Dynamic Signature Marketplace app, you can insert Agent name, Agent email, Agent number, Agent title, and Ticket ID, plus a logo via public image URL, and apply signatures conditionally by Email, Product, or Group.

Can I use an AI tool without changing my Freshdesk signatures? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and drafts or sends replies into your existing tickets — they land under the signatures you already configured. It runs on top of Freshdesk and doesn't replace your help desk or its settings.

Ready to make every reply read as human as it looks? Start a free trial of Macha and connect it to your Freshdesk in minutes.