How to Set Up Email Notifications in Freshdesk

Where Freshdesk email notifications live

Everything is in one module. Per Freshworks' Configuring email notifications documentation, you manage every automatic email under Admin → Workflows → Email Notifications.

Inside that module, notifications are split into two groups that are worth keeping straight in your head:

• Agent notifications — the internal emails your team receives about ticket activity (a new ticket, an assignment, a customer reply, an SLA breach).
• Requester notifications — the customer-facing emails your end users receive (their ticket was created, an agent replied, the ticket was solved or closed).

There's also a Templates tab in the same area for the Agent Reply Template, which controls the greeting and signature scaffolding agents start from when they reply. We'll come back to that.

Step 1: Turn on the agent notifications your team needs

Agent notifications are what pull your team into a ticket without anyone manually watching a queue. Open the Agent notifications section and you'll find a list of triggers, each with an on/off toggle.

1. Go to Admin → Workflows → Email Notifications → Agent notifications.
2. Toggle on the events your team should hear about. The core ones are New ticket created, Ticket assigned to group, Ticket assigned to agent, Requester replies to ticket, and Ticket unattended in group.
3. On the Pro plan and above, you'll also see the SLA-event notifications — First response SLA reminder and violation, Next response reminder/violation, and Resolution time reminder/violation. These are the emails that fire off your SLA policy, so they pair directly with how you set up SLA policies in Freshdesk.
4. Click a notification's name to open its editor, where you can rewrite the subject and body.

A word of restraint here: turning everything on is the fastest way to train agents to ignore their inbox. Pick the two or three events that genuinely demand a human's attention and leave the rest off.

Step 2: Configure the requester (customer-facing) notifications

Requester notifications are the ones your customers actually read, so they carry more weight for your brand than any internal alert. The same module lists them under Requester notifications, and the set typically includes:

• New ticket created — the acknowledgement your customer gets when they email in.
• Agent adds comment to ticket — sent when an agent replies publicly.
• Agent solves the ticket and Agent closes the ticket — the closing-loop emails.
• User activation email and Password reset email — portal-account transactional messages.

For each, use the toggle to enable or disable it, then click through to edit the copy. The acknowledgement email in particular is worth rewriting: the stock version is functional but bland, and a warmer line that sets a realistic expectation ("Thanks — we've got your ticket and a human will reply within one business day") does real work for your first impression.

Step 3: Edit the subject line and message body

Every notification, agent- or requester-facing, opens into the same style of editor. Inside it you get:

1. A Subject field — a single line you can rewrite freely and salt with placeholders (more on those next).
2. A Message body in a rich-text editor — bold, links, formatting, the works.
3. A </> (source) toggle to switch into raw HTML when you need precise control over layout, inline styles, or a branded template that the visual editor can't quite produce.

Edit, and Save. Freshworks notes that you can "edit the subject line and message body in the rich text editor, or select </> to switch to raw HTML for advanced formatting" — so if your marketing team hands you a designed email template, the HTML view is where it goes.

Step 4: Insert dynamic placeholders

Static notifications are close to useless — a "your ticket was updated" email that doesn't say which ticket just makes the customer hunt. Placeholders fix that by injecting live ticket data into the subject and body at send time.

Look for the Insert Placeholder button in the editor. Clicking it opens a picker of dynamic fields you can drop in. The commonly used ones include:

A practical subject line for the agent "new ticket" email might read New ticket #{{ticket.id}} — {{ticket.subject}}, and a requester acknowledgement can greet by name with Hi {{ticket.requester.name}},. Because the placeholders resolve per ticket, one template personalises every message.

The same Insert Placeholder mechanism powers the Agent Reply Template under the Templates tab, documented separately in Freshworks' agent reply templates guide. That template controls the standard greeting and signature agents start from, so the whole team's replies share a consistent, branded frame.

The honest limits — and where an AI layer picks up

Freshdesk's notification engine is solid at exactly what it's for: it's deterministic, reliable, and it will faithfully email the right people the moment a trigger fires. But it's worth being clear about what it doesn't do.

It's an alerting system, not a workflow engine. A notification tells a human that something happened; it can't read the ticket, understand the problem, or draft the reply. The "new ticket created" email lands in an agent's inbox and the actual reasoning and writing still fall entirely on that agent.

Some of the best pieces are plan-gated. The SLA-event notifications require the Pro plan and above, and localizing notification content into multiple languages is likewise a Pro/Enterprise capability — so if you're on a lower tier, part of the picture in this guide simply won't appear in your admin console. Confirm the exact gating against your own plan before you design a process around it.

Placeholders are static fields, not logic. {{ticket.id}} and {{ticket.subject}} inject stored data, but a notification can't compute anything, look a value up in an external system, or vary its wording based on what the ticket is actually about. When the underlying question is "where's my order #4471?", the notification just forwards the question — it can't answer it.

This is the seam where an AI agent layer fits, and it's worth understanding the build-versus-buy tradeoff before reaching for one. The broader category of AI agents for customer service exists to do the reasoning-heavy work a notification can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk or its notifications. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your notifications already announce: drafting or posting a grounded first reply the moment a ticket arrives, triaging by intent, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. If you want the fuller pattern, we walk through it in how to automate Freshdesk with AI. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: keep Freshdesk's notifications as the source of truth for who gets told what, and when, and layer an agent on top for the part the email can't do — actually reading the ticket and producing the response.

FAQ

Where do I set up email notifications in Freshdesk? Go to Admin → Workflows → Email Notifications. Notifications are split into Agent notifications (internal emails about ticket activity) and Requester notifications (customer-facing emails), each with its own on/off toggle and editable template.

How do I add the ticket number or a link to a notification? Open the notification's editor and click Insert Placeholder, then choose a dynamic field such as {{ticket.id}}, {{ticket.subject}}, {{ticket.url}} (the agent link), or {{ticket.portal_url}} (the customer link). The placeholder resolves per ticket when the email is sent.

Can I edit the HTML of a Freshdesk notification email? Yes. In the message-body editor, select the </> (source) toggle to switch from the rich-text view to raw HTML, which is where a designed or heavily branded template belongs.

Are all notification types available on every plan? No. The SLA-event notifications (first response, next response, and resolution reminders and violations) require the Pro plan and above, and localizing notification content into multiple languages is a Pro/Enterprise feature. The core ticket-activity notifications are available more broadly — confirm against your own plan.

Can I add AI to Freshdesk notifications without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing help desk and its notifications — it doesn't replace them. Freshdesk stays the system that decides who gets emailed and when, while Macha handles the reasoning a notification can't: reading the new ticket and drafting or sending a grounded reply.

Ready to turn the "new ticket" alert into an answered ticket? Start a free trial of Macha and connect it to your Freshdesk in minutes.