Skip to main content
New Idea

CC and Shared Ticket Email Notifications

Related products:Freshservice
  • February 25, 2025
  • 9 replies
  • 306 views

jcapitan-shoreline
Skilled Expert
Forum|alt.badge.img+5

The issue that I am having between CC and shared tickets is that the experience is very inconsistent and easily leads to communication breakdowns or upset customers in Freshservice.

 

As of right now CCs work just like emails (kind of), if a requester CCs a user to a ticket, the CC will get the direct email communication and also an email from Freshservice “Note added to Ticket”. Meaning the CC will get 2 notifications emails for 1 update.  If he CC user doesn’t reply all and replies directly to the ticket, the original requester will not get any email notifications (not ideal).  The same also occurs if the requester doesn’t not click reply all, the CC user on the ticket will not get any updates (not ideal).

 

These 2 issues lead me to wanting to lean on the Shared Tickets feature. If the requester adds a shared user to a ticket then they should be updated on all activity that the original requester gets updated on.  This should also apply to any public comments that either the original requester or the shared user add to the ticket. Both parties should always get any updates in relation to the ticket.  This is my feature request.

 

The original requester and shared ticket user should get all the following notifications via email.

  • Ticket Approved or Rejected
  • Requested Item Stage Change
  • Agent closes the Ticket
  • Agent solves the Ticket
  • New ticket shared
  • Note added to Ticket
  • New ticket created

9 replies

Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

ping ​@Roxwell ​@Medic1334 


Roxwell
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • February 25, 2025

@jcapitan-shoreline  is this not mostly covered already?

 

you just have to enable it at the bottom of notifications

 

 


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

In my test Note added is only when the OG requester adds a note and not when the agent adds a public note. 


Roxwell
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • February 25, 2025

@Daniel Söderlund ah, I see how that’s annoying. I supposed I haven’t noticed it, as for alot of customers we’ve moved notifications out of the global, as we need to be able to “skip” notifications to other automated systems and avoid blizzards of emails.


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

@Daniel Söderlund ah, I see how that’s annoying. I supposed I haven’t noticed it, as for alot of customers we’ve moved notifications out of the global, as we need to be able to “skip” notifications to other automated systems and avoid blizzards of emails.

Ya I have few customers as well that have moved to a custom notification WFA and disabled system notifications. It has it’s ups and downs. 


Roxwell
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • February 25, 2025

@Daniel Söderlund ​@jcapitan-shoreline  - I agree the share and CC needs working on though, this is something we have raised with @Freshworks multiple times, as it’s inconsistent 


jcapitan-shoreline
Skilled Expert
Forum|alt.badge.img+5

What are the custom notifications that you guys are speaking of? This is something I can use to work around my issue?


Daniel Söderlund
Top Contributor ⭐
Forum|alt.badge.img+14

What are the custom notifications that you guys are speaking of? This is something I can use to work around my issue?

You build your own workflow(WFA) to send out notifications when something happens to a ticket. 

Not sure it can be done with shared users. CC I’m sure there are a option to send out e-mail to. 


Medic1334
Top Contributor ⭐
Forum|alt.badge.img+9
  • Top Contributor ⭐
  • February 25, 2025

What are the custom notifications that you guys are speaking of? This is something I can use to work around my issue?

Global notifications dont have any visibility that they went out. An example we have here is email agent on ticket assigned to group. Globally, that creates a TON of noise. Instead, we have a workflow automator (WFA) that has a condition of “ticket is updated” and condition that includes any groups that want the email sent out, then an action that sends email to assigned group that the ticket was assigned.

This allows for visibility in the activities of the ticket that a notification should have been received as well as being able to selectively take actions instead of doing it globally.