Business rules such as triggers, automations, and macros affect email notifications to CCs and followers in several ways. For example, your default triggers send email notifications to requesters and CCs (seeCustomizing default email notifications to CCs and followers). You can also create business rules to do these things:
- Add followers to tickets automatically using triggers, automations, and macros.
- Use triggers and automations to send email notifications to both CCs and followers.
- 使用触发器和自动化自定义文本in email notifications to CCs.
You cannot configureviewsfor CCs and followers. However, you can view all of the tickets that you are copied on or following from your user profile (seeViewing your user profile in Zendesk Support).
This article includes these sections:
- Adding followers to tickets automatically using business rules
- Sending email notifications to requesters and CCs automatically using business rules
For more information about email notifications for CCs and followers, seeCustomizing the text in email notifications to followersandUnderstanding when email replies become public or private comments.
For a complete list of documentation about CCs and followers, seeCC and followers resources.
Adding followers to tickets automatically using business rules
You can add followers to tickets automatically using business rules (triggers, automations, and macros). This is done by adding action statements to the business rules.
These are actions you can use that are related to followers:
- In triggers, use theAdd followeraction.
- In automations, use theTicket: Add followeraction.
- In macros, use theAdd followeraction.
When an agent is added as a follower to a ticket by means of these actions, the follower does not receive an email notification saying they were added. Followers only receive email notifications when comments are added to tickets they are following.
To add followers to tickets automatically using business rules
- Create or update triggersto include theAdd followeraction.
- Create or update automationsto include theTicket: Add followeraction.
- Create or update macrosto include theAdd followeraction.
Sending email notifications to requesters and CCs automatically using business rules
You can send email notifications to requesters and CCs automatically using business rules (triggers, automations, and macros). This is done by adding action statements to the business rules.
These are actions you can use:
- In triggers, use theEmail user + (requester and CCs)andAnswer Bot + (requester and CCs)actions.
- In automations, use theNotifications: Email user + (requester and CCs)action.
Remember that two default triggers use these actions, but you can create others (seeCustomizing default email notifications to CCs and followers).
It's also important to note that the trigger actionEmail user +(requester and CCs)is suppressed if a ticket update does not include a public comment. The trigger still fires and performs any other actions that may be included in the trigger, but the email message is not sent. You must include a public comment if you want to use this action to send an email message.
Placeholders are allowed in these actions (and in theComment/descriptionaction in macros). This includes theticket.cc_names placeholder, which returns the names of all the CCs on the ticket. For more information about placeholders, seeUsing placeholdersandzendk Support placeholder reference.
TheComment/descriptionaction in macros can be used by agents to add comments to tickets, and those comments can include placeholders about CCs and followers, but macros themselves don’t cause email notifications to be sent to users. However, keep in mind that you may have other business rules that cause email notifications to be sent to users when a comment is added to the ticket.
To send email notifications to requesters and CCs automatically using business rules
- Create or update triggersto include theEmail user + (requester and CCs)action.
Enter an email subject and body text in the fields provided.Placeholdersare allowed.
- Create or update triggersto include theAnswer Bot + (requester and CCs)action.
Enter an email subject and body text in the fields provided.Placeholdersare allowed.
- Create or update automationsto include theNotifications: Email user + (requester and CCs)action.
Enter an email subject and body text in the fields provided.Placeholdersare allowed.
22 Comments
Is it possible to create triggers for just followers (i.e. agent-only followers, not other CCs)?
Hi,
I would like to automatically add a follower (CSM) based on the organization they are associated to.
Currently the only way I can do this is by having a trigger which would need to list all the organizations they are associated to.
This is not scalable when staff join or leave and when accounts are constantly changing.
We have a Salesforce integration where the CSM for the account is being added to Organizations.
Is there a way to automatically ad the CSM as follower or Cc based on the ticket being associated with an Organization?
Hi,
A question from our end-users has come up in regards to notifications for CCs:
When an end-user replies to a ticket that has CCs, it sends a notification to the requester + CC'd.
But that means that the end-user who sent the reply, regardless of whether they're the requester or one of the CC'd, also gets the same notification - about the exact reply that they've submitted just now.
This has been reported to be quite an annoyance to our end-users, who end up being spammed by too many notifications, including from themselves.
Is there any way to resolve this?
After all, it's really not necessary for an end-user to be notified about their own replies that they just submitted.
At this time unfortunately, we don't support follower-based conditions for business rules. At the moment it's only limited to adding followers to a ticket
I've marked this conversation as product feedback for review, which means that your input will be aggregated as a part of our Voice of the Customer program that provides customer feedback to our product development teams.
此外,我鼓励你去创建一个新的职位in theGeneral Product Feedback topicin our community to engage with other users who have similar needs and discuss possible workarounds. Conversations with a high level of engagement ultimately get flagged for product managers to review when they go through roadmap planning.
Specific examples, details about impact, and how you currently handle things are helpful for our product teams to understand the full scope of the need when working on solutions. You may also want to review the Product feedback guidelines and how to write an effective feedback post [https://support.zendesk.com/hc/en-us/community/posts/360004391547-Product-feedback-guidelines-how-to-write-a-good-feedback-post].
We truly value customer feedback and your voice and votes in the forums help influence future Zendesk functionality!
We've just migrated to the new user experience for followers and CCs, and the design choice to follow the reply convention which drops CCs is causing us immediate pain. We deal with hundreds of tickets each day, and the stakeholder expectation is that communication via tickets stays visible to all parties, and that CCs aren't dropped off by one respondent. This is captured here as a design choice of the new experience:https://support.zendesk.com/hc/en-us/community/posts/360037182953-New-Follower-and-CC-s-problems-CC-s-getting-removed-by-End-user-unintentionally
We're looking for other work arounds, and wondering if triggers could be used to identify this case (of a Reply rather than a Reply All), and adding back the CCs or stopping them being removed?
Thanks, Charles, but it's not what I asked.
The recipients still need to be notified of comments added to the request, even if they're posted by other end-users.
The only issue is that recipients should not be notified about comments that they themselves have posted.
That's correct, agent replies thru Zendesk are being sent to the end-users email thru triggers. When notification triggers are deactivated or misconfigured, ticket updates do not send an email to the end-users.
Thanks for the heads-up, Jeff, we got it fixed!
Okay, so to summarize:
If an end-user replies, regardless if they're the requester or CC'd, all recipients (except the poster) would receive a notification, regardless of a trigger.
If an agent replies, then it's dependent on a trigger.
Did I understand that correctly?
I have this scenario. Our finance team use our Zendesk instance to contact members of staff across the organisation. Not all of the staff members use Zendesk but are all agents, light or full agents. Finance create a ticket and use a macro that sets the staff member contact as a CC (as you cannot set the requestor to a specific person). The CC gets a notification that they need to investigate the case and to respond either directly on the ticket or via their email if they don't use Zendesk. There is a 14 day timeframe to respond. If the staff member (the cc) does not respond I need them to receive a follow up notification reminding them this ticket is outstanding.
I created an automation to send a follow up to the requestor and ccs after 7 days, the requestor receives a followup but the cc does not because they are an agent. I contacted Zendesk about this and was told this is normal.
I am currently testing followers and cc's but cannot see how I can send a followup notification using automations. I do not need to add a follower as the staff member is already as follower. What do you suggest?
Hi Eitan,
Since the CCs(end-users) are sending the replies via email, the requester should still receive it even if the triggers do not fire on the ticket.
Here's a sample from my test account.
As you can see, there's no trigger that fired when the comment (Test reply from CC, checking if requester will receive this even if trigger has condition "Current user - Is - Agent")was added by the CC'd end-user.
But on the email of the requester, that comment was still received.
Hello Tarandeep,
Creating triggers is also the best way I can think about if you want to automate notifying users depending on what the ticket organization is.
Would it also help adding an organization tag, so that tickets under the organization would automatically have the tag. However, you would still need to create triggers for this. This way, instead of updating the trigger to update the recipient (CSM), you can just update the org tag so that a different trigger would run depending on who's the CSM that should receive a notification.
Email notifications for followers are handled differently. Followers get email notifications when comments are added to tickets they are following, and this happens as soon as you turn onEnable followersin your admin settings. There’s no way to disable email notifications to followers (other than to stop using followers by turning offEnable followers), but you can customize the text in email notifications to followers using the followers email template .
Thank you!
Kind regards,
I have the same requirement as Tarandeep.
I have already added under the Organisation a 'CSM' field (that value comes from HubSpot), however, I can't seem to find a way to create a trigger which will automatically add the CSM If this value is not empty as a follower on the ticket.
That's interesting.
Does that work for CC'd contacts as well?
For example, when the requester adds a message, will the CC'd receive an e-mail?
FYI; there is a is in this article. It is in the second bullet point. it is uee opposed to see.
Adding followers to tickets automatically using business rules
You can add followers to tickets automatically using business rules (triggers, automations, and macros). This is done by adding action statements to the business rules.
These are actions you can use that are related to followers:
I see. Okay, I'll try it out. Thanks!
Eitan Blumin
Here's a sample.
I tried sending a reply (using the requester's email)
It showed in Zendesk and no trigger fired.
It also showed in the CC's email even if no trigger fired in Zendesk.
Eitan Blumin
You still need the trigger for agent replies, without that trigger, the requester and the CC won't be updated when an agent replies thru Zendesk.
As for your question, "what if I DON'T want end-users to receive notifications? (for a certain type of tickets, for example)" - You need to define that it the conditions of your trigger.
Example, if the ticket that you want to exclude from the trigger has a specific tag "no_notification", you can use the condition "Tags-Contains none of the following - no_notification"
More information about the trigger conditions that you can use here:Trigger conditions and actions reference
HiEitan Blumin
You can add this condition"Current user - Is - Agent"to your trigger so that it will only fire on tickets if it is an agent who replied on the ticket but not if it is an end-user.
Hello,
The article mentions we can use a trigger or automation to send notifications to followers:
I don't see that option in either the trigger or automation:
In this article,自定义默认的CC的邮件通知nd Followers, It says you can only change the subject and body text:
Can you please confirm if it is possible to add conditions to notifications sent to followers through a trigger/automation? I would really like to be able to exclude certain notifications from being sent to any followers.
So, actually, I don't need to configure any trigger that sends notifications to end-users about posted comments?
But conversely, what if I DON'T want end-users to receive notifications? (for a certain type of tickets, for example)
Pleasesign into leave a comment.