Problem: Email notifications are not going out when a ticket is created, an update is posted to the ticket, etc.
Cause: Notifications are only sent out when the Notify Policy is configured correctly for the corresponding Organization or Machine Group. Let's take a look at some potential pitfalls.
1. An email notification will only go out if a ticket is associated to an organization, machine group, or machine ID. An email notification will NOT go out if the ticket is associated to a staff record, department or inventory asset. This is by design.
2. Notify Policies need to be configured on a Per-Organization or Machine Group basis. Failing to configure this for an Organization will inhibit notifications for tickets in that Organization
3. If you have set the "Send auto response to emails creating new tickets" notify policy on organizations/machine groups this specifies that ONLY those tickets created by email will receive an email notification. Users that submit tickets via the UI or their agent icon will not receive an auto response since they are able to physically view the ticket get created.
4. If you have enabled the "Received emails send alert to assignee", this specifies that an email notification will only go out if the ticket was updated via email. If a ticket is updated via the agent icon or UI, an email notification will not go out. This is by design and a feature request to change this behavior as already been submitted.
5. It is NOT possible to have an email notification go out when a ticket is closed. The Ticketing module is not built around too much automation.
6. When a ticket is assigned to someone, an email notification will ALWAYS go out to the assignee. This is an internal notification that gets triggered. There is no way to turn this notification off. The email that is uses to send the assignee an email notification is the one in system tab > Users that is associated to that assignee/user
Solution: Please double-check your configurations and if you would like to know more about each event please see our documentation.
Pictured below is an example of a fully configured Notify Policy which is sending Notifications for every possible event.