Email notifications keep your agents and customers automatically informed about ticket activity. This article explains how to access, configure, and customize the different notification types available in Freshdesk.
TABLE OF CONTENTS
- Overview of email notifications
- Configure agent notifications
- Configure requester notifications
- Configure CC notifications
- Customize reply and forward templates
Prerequisites
Before configuring email notifications, make sure you have the following permissions and requirements:
- Administrator access to your Freshdesk account
- Set up a verified support email address
- Pro or Enterprise plan for multi-language notifications
Overview of email notifications
Freshdesk lets you send automatic email notifications to agents and requesters when specific ticket events occur. These notifications ensure that everyone involved in a ticket is informed without any manual follow-up.
For example, you can notify customers when agents add comments or public notes to their tickets with a customized email with a link to the ticket.
Tip: Email notifications are triggered automatically based on ticket events. However, to perform more advanced actions, such as updating fields, assigning tickets, or sending conditional emails, use automations.
Email notification types
The following table provides details about the different categories of email notifications:
Category | Receiver | Purpose |
Agent notifications | The agents assigned to a ticket | Alerts agents about new tickets, replies, assignments, and SLA breaches. |
Requester notifications | The customer who raised the ticket | Keeps customers updated on ticket status changes and agent responses. |
CC notifications | The users who are CC'd on a ticket | Notifies CC'd users when a ticket is created (by an agent) or a public note is added. |
Reply templates | - | Prefills default content in agent replies and forwarded tickets. |
For all notification types, you can configure the following settings:
- Enable or disable each notification type based on your requirements
- Edit the email template for the subject and body
- Insert dynamic placeholders (for example, {{ticket.id}}, {{ticket.url}}) to include ticket-specific information
- Configure multiple languages and customize templates for each language. When editing translations, the ⚠️ icon indicates that a translated version may be outdated and should be reviewed.
Note: Multiple-language support is available only with the Pro plan.
Access email notifications
To access and configure different types of email notifications:
- Go to Admin > Workflows > Email Notifications.
- Select the relevant tab to view and configure notifications for each category.
The following sections provide detailed information on configuring the different email notification types.
Note: If your account has multiple support email addresses, all notifications are sent from the primary email address. Also, failure notifications related to email configuration are sent to the account administrator.
Configure agent notifications
Agent notifications inform agents about ticket events in your account. You can turn each notification type on or off and customize the email templates.
The following table provides details on the different events for which you can trigger agent email notifications:
Event | Description |
New ticket created | This notification is sent to the select agents when a new ticket is created. You can also use the Notify Agents option in the template to specify recipients. |
Ticket assigned to group | This notification is sent to all agents within a group when a ticket is assigned to that specific group. |
Ticket assigned to agent | This notification is sent to individual agents when a ticket is assigned to them. |
Requester replies to ticket | This notification is sent to the assigned agent when a customer responds to an existing ticket. |
Ticket unattended in group | This notification is sent when a ticket in a group remains unattended for the duration set in Group settings. You can include the elapsed time since the ticket was assigned to the group in the email body. |
First response SLA violation | This notification is sent to an agent when they have not responded within the "first response due time" of the ticket. |
Resolution time SLA violation | This notification is sent to an agent when the resolution due time is approaching. |
Next response SLA reminder | The notification is sent to an agent when the next response SLA deadline is approaching. |
Next response SLA violation | The notification is sent to an agent when a ticket risks breaching the next response SLA. |
Note added to ticket | This notification is sent to agents listed in the Notify agents field when a note is added to a ticket. Tip: Since internal collaborators do not receive assignment notifications by default, you can tag them in a note so they receive notifications. |
First response SLA Reminder | This notification is sent to an agent when the first response time is approaching a potential SLA violation. |
Resolution time SLA Reminder | This notification is sent to an agent when the resolution due time is approaching. |
New threads on my tickets | This notification is sent to agents and watchers when a new thread is created on their ticket. |
New replies on my thread | This notification is sent to the agent handling the ticket, watchers, and tagged users when an agent replies to a thread. |
Threads I am tagged in | This notification is sent to an agent when they're tagged in a thread. |
Note: The SLA-related notifications are available only from the Pro plan.
Example: notify agents when a new ticket is created
Your support team wants every agent in the Billing group to receive an email whenever a new billing ticket is received. For this, you can configure the New ticket created agent notification:
- Go to Admin > Workflows > Email Notifications.
- Select the Agent Notifications tab.

- Click New Ticket Created.
- Edit the subject line and message as needed.
- In the Notify Agents section, add the agents who should receive this notification. For ecxample, all agents in the Billing group

- Use placeholders such as {{ticket.id}} and {{public.url}} to include dynamic ticket information.
- Click Save.
- Enable the toggle to activate the notification.
Note: You can add multiple agents only to the New ticket created agent notification. For all other notification types, only the assigned agent on the ticket receives the notification. If you want to notify multiple agents on other event types, set up an automation rule.
Configure requester notifications
Requester notifications keep customers informed about activity on their tickets. The following events trigger a notification to the requester:
Event | Description |
New Ticket Created | This notification is sent to the requester when they submit a ticket. |
Agent adds comment to ticket | This notification is sent to the requester when an agent adds a public comment. |
Agent solves the ticket | This notification is sent to the requester when their ticket is resolved. |
Agent closes the ticket | This notification is sent to the requester when their ticket is closed. |
User activation Email | This notification is sent to new customers to activate their Freshdesk account. |
Password reset Email | This notification is sent when a requester requests a password reset. |
Note: If you turn off the User activation email notification, customers will not receive an activation email after signing up unless you send it manually from the contact profile. Password reset emails are also affected when this toggle is off.
Example: send notifications to the requester when an agent solves the ticket
Notify the ticket requester proactively once an agent resolves the ticket, ensuring they are aware their issue has been addressed.
- Go to Admin > Workflows > Email Notifications.
- Select the Requester Notifications tab.

- Click Agent Solves the ticket.
- Customize the email body.
Add placeholders such as {{ticket.id}} and {{public.url}} to give customers a direct reference to their ticket.
- Click Save.
- Enable the toggle to activate the notification.
Note: If requesters receiving duplicate notifications when a new ticket is created, a ticket creation automation rule may be sending an additional email alongside this default notification. Check the ticket activity log (Show Activities) to see if an automation rule ran on that ticket. If the rule includes a Send email to requester action, remove it or add a Skip new ticket email notification action to prevent duplicates.
Configure CC notifications
CC notifications are sent to users added as CC on a ticket. These notifications ensure that stakeholders copied on a ticket are informed about key updates without being directly involved in ticket handling.
When a ticket is created with CC users, they receive the initial notification. The subsequent agent replies are delivered directly as regular emails rather than separate notification triggers. However, whenever a public note is added to the ticket, a notification is sent to all CC’d users regardless of how the ticket was created.
The types of CC notifications you can send are:
- New ticket created: This notification is sent to users added in the CC field only when an agent creates a ticket for a customer and adds them as CC.
- Note added to the ticket: Sent to everyone in CC when a public note is added.
Example: notify stakeholders about escalations
Automatically notify managers when a public note is added if they are included as a CC on the ticket. Ensure that the relevant stakeholder is added as a CC when creating or updating the ticket.
- Go to Admin > Workflows > Email Notifications.
- Select CC Notifications.

- Click Note added to ticket.
- Review or customize the email template if needed. You can also add placeholders.
- Click Save.
Customize reply and forward templates
Reply and forward templates define the default content that appears in the agent reply editor when an agent responds to or forwards a ticket.
You can include the [#{{ticket.id}}] in the subject line to ensure that email conversations are threaded properly. You can also control the content that appears by setting a default font in Helpdesk Settings and allow agents to choose their own font preferences.
To update a reply or forward template:
- Go to Admin > Workflows > Email Notifications.
- Select Reply Templates.

- Edit the required template.

- Use Insert Placeholder to add fields such as Ticket ID.
- Click Save.