Skip to main content
Future Consideration

Exceptions list for requesters mail notifications

Related products:Freshservice
  • Feb 22, 2024 5:05 PM UTC
  • 3 replies
  • 100 views

xTofC4Be
Apprentice
Forum|alt.badge.img+2

We currently deactivated the standard requesters notifications in freshservice and are using workflow automators instead for one and only reason: exceptions cannot be configured in the standard notifications settings to avoid notifications being sent to specific requesters. This is needed because some of our requesters are also our suppliers, they're of course using ticketing tools at their side and enabling notifications for them creates loops of notification messages being sent between their system and ours.

Would it be possible to add that feature (exceptions list) for each type of notifications so that we could use the freshservice standard requester notifications instead of automators ?

3 replies

Forum|alt.badge.img+4
  • Active Contributor
  • Feb 29, 2024 3:56 PM UTC

Having the ability to have some conditions or rules around the notifications would be helpful.  We do not want the out of the box notifications because we don’t want any external people receiving the notifications.  While we use a workflow for one workspace, we are unable to do that in another workspace because we use auto-assignment which bypasses workflows as they are system events and therefore workflows aren’t triggered.  It is causing a lot of chaos for us that really is a huge pain point.  


mbutler
Top Contributor ⭐
Forum|alt.badge.img+10
  • Top Contributor ⭐
  • Feb 29, 2024 9:22 PM UTC

Absolutely a fantastic idea! We should have the ability to implement rules for notification purposes, but they don’t exist - they are either on/off. We should have more control than that.


Forum|alt.badge.img+1
  • Apprentice
  • Jul 20, 2026 6:59 PM UTC

Two years and no traction on this? I’ve ran into this issue at multiple companies. We need to be able to skip these notifications for specific requesters.