Configuring CC and follower permissions

Have more questions? Submit a request

18 Comments

  • Edwin Goh

    Hi Charles Nadeau,

    How do I disable the email notification for 'You are registered as a CC on this request ({{ticket.id}}). Reply to this email to add a comment to the request.'

    I will want my users to continue receiving updates from the tickets, but not everyone knows that we are using Zendesk to manage our tickets. These updates somehow confuses them what to do with them.

    Edwin

    0
  • Brett - Community Manager

    Hey Edwin,

    You should be able to edit what shows up in this email by doing the following:

    1. Click the Admin icon () in the sidebar, then select Settings > Tickets.
    2. Edit the CC email text.
      • Edit the CC email subject field to change the subject that appears in CC email notifications.
      • Edit the CC email text field to change the body that appears in CC email notifications.
    3. Click Save tab.

    Let me know if you run into any issues :) 

    0
  • Edwin Goh

    Hi Brett,

    The default text is always shown. I tried deleting every text and it keeps coming back after I click on Save Tab.

    0
  • Brett - Community Manager

    Hey Edwin,

    The default text keeps getting re-added to the field I mentioned previously? Any chance you could provide me with a screenshot of what you see on your end when navigating to that page?

    Thanks!

    0
  • Alex Gerulaitis

    This new functionality disables reply-all when the CC is a Distribution List (team email address), and thus prevents effective communication using team addresses.

    E.g. I'd CC a team email address for a "side escalation"; one of the team members responds - the comment is flagged - the team and other non-agent CCs misses out on the response as private comments aren't visible to end users.

    How do we handle this?

    0
  • Brett - Community Manager

    Hi Alex,

    We do not support the use of aliases, distribution lists, or Google groups at this time. It may be worth looking into the Side Conversations feature which is part of the Collaboration add-on we have available.

    Side conversations are spaces in a ticket where agents can have a side conversation with a specific group of people, or discuss a specific area of concern or course of action.

    Hope this points you in the right direction!

    -1
  • Alex Gerulaitis

    > We do not support the use of ... distribution lists ... at this time.

    Even though distribution lists are an integral part of email as a communications mechanism - which Zendesk does support, I hope?

    Bottom line: this update / change of functionality broke our Zendesk, and no, "Side Conversations" don't fix it. What is the justification for breaking existing functionality that we (used to) rely on?

    0
  • Andrew J

    Hello Alex, having never really played with distribution lists, I'm not fully sure if the flow your method achieved.
    It sounds like you may be having problems with the flagging of non-directly cc'ed messages, which was not part of the recent update but one many months ago. This was a security release to prevent unauthorised emails from being able to insert public info into a ticket or other object. This I believe was originally identified as a security risk for other products in the Zendesk family.
    On other issues, there are various ways to handle notifications to individuals and groups and it is possible that a suitable solution may be found for the other issues you are facing, however replies from email addresses that are not in the Cc list will be flagged. The only way around that is to add all the emails to the cc field.
    Alternatively, since the message is at least present, and presumably you will see this update as the agent, the way we have handled this issue is to copy the message and paste it as a comment quoting them yourself.
    If the people in this distribution list were agents, would that work? I have tested that. Create and trigger to notify an agent group and if they reply, does this get flagged?
    The workflow that I think you are using could be considered using these other people as support agents, especially if they could publicly reply to customers. This could be used to bypass agent licenses. If you are just notifying them, this can be done with a target, you could invite anyone to email you directly if they are offering you advise etc, or of course reply to add a private comment to the request.
    Someone who is directly communicating with the end user and representing your business should really be an agent.
    Would be good to understand more how this is used.

    0
  • Brett - Community Manager

    @Andrew thanks for jumping in and sharing how you addressed this limitation :)

    @Alex as Andrew mentioned, this has been address months ago to address a security issue. The vulnerability would allow an unauthorized person to add themselves to a ticket via email by leveraging an ID known only to ticket participants. This vulnerability did not affect the security of information stored on the Zendesk platform. However, it could have potentially allowed access to external, non-Zendesk services that do not vet specific email addresses, but instead only check the domain name when a user is added.

    I realize that this may be an inconvenience for certain workflows but in some cases security becomes a balance against ease of use.

    0
  • Alex Gerulaitis

    Andrew: sending an email to a team and flagging (preventing from posting) a response from a team member breaks things for us. It doesn't matter whether you think they should be agents: it broke our Zendesk and generally broke an established communication and escalation mechanism in use in the enterprise.

    CC-ing 40 people is not an option. Making them all agents is unnecessary and not an option. When one of the team member responds to the ticket but their response doesn't go back to the team (because it got flagged) or because it requires an agent to copy-paste their comment as a public one - this breaks an established communication and escalation mechanism that is in wide use in the enterprise: communicating to teams via their team addresses rather than individual members' ones. Other team members will not know someone responded (unless there's an agent copy-pasting things) and will wonder why and will try responding on their own resulting in confusion, and potentially worse.

    Brett: thanks. JIRA doesn't do this, and neither does ServiceNow, to my knowledge. I get it that you needed to patch a vulnerability - all I am saying is that it broke certain parts of Zendesk (and generally, accepted email) behavior that are important to us, all without an apparent option to negate the damage - e.g. by whitelisting a domain or two as an exclusion to the rule, or disabling the rule altogether for our instance.

    The vulnerability doesn't apply to our instance as it's not public-facing and generally only for internal users - so the change in behavior is a bit hard to stomach.

    Thanks again for chiming in.

    0
  • Brett - Community Manager

    @Alex, totally understand where you're coming from! I'm going to bring this into a private ticket to discuss further and see if we can come up with some sort of alternative. You'll receive a follow-up email shortly :)

    0
  • Melissa Hoffmann

    Hi Brett

    I just wanted to add a comment to the recent discussions above, as we also communicate with external business partners via distribution lists. I've raised this an a few different forums.

    The individuals in the Dist Lists we have are intended to be set up as Light Agents, but they do not log into Zendesk.  If an individual replies by email, recipients on the email (dist list, or as individuals) will receive the comms via email rather than ticket, which is fine.  But our issue is when we reply back, it is via internal comment, and if that person is not a light agent, then they will not receive the reply.

    We used to be able to recognise if someone was not an agent, as the reply used to be in white public comment.  Now as all comments are yellow internal comments, there is no way to easily identify user type unless checking user profile.

    With no ability to CC groups from Zendesk, we need to use DLs to ensure comms reach the correct audience.  As the distribution lists are created by external parties, they can change members without our knowledge.  There has to be a better way to identify users when adding CCs.  

    Mel

    0
  • Brett - Community Manager

    Thanks for sharing Melissa!

    I'll pass this feedback along to the appropriate team as you and Alex have provided some great use-cases. I would also recommend cross-posting this in our Support Product Feedback forum to help provide visibility to both our Product Managers as well as other users running into similar roadblocks.

    I wish I was able to provide you with an easier alternative at this time but unfortunately I've not been able to find anything on my end to address this :-/

    We greatly appreciate you taking the time to share this with us so thank you again!

    0
  • Darren Taylor

    Is this still being rolled out? We are yet to see this option in our admin area. Thanks

    0
  • Brett - Community Manager

    Hi Darren,

    Yes this feature is still being rolled out which is why this may not show up on your account yet.

    Appreciate your patience and hang in there just a little bit longer :)

    0
  • Darren Taylor

    Hi there

    So we've just had this featured added, however it doesn't appear to work. When I add a CC, they never receive the email. 

    Does the CC have to be registered as an end user on Zendesk just to receive the email? If so, this means we have to create user each time before we can CC them in. Also if we have to create the user, they also receive an additional email asking them to create a password for a Zendesk account, which knowing our users will not want to do.

    0
  • Brett - Community Manager

    Hey Darren,

    Have you had a chance to check the Ticket Events to see if the notification was sent out from Zendesk Support?

    As for registering the user first, do you have enable anyone to submit tickets toggled on under Admin>Settings>Customers? If this is disabled, then yes the user would need to be added to your account before you can CC them.

    Keep me posted!

    0
  • Ivy

    Hi ,

    how can i activate the cc field in the request form? I have checked and enable the cc email fields, but still unable to see it in my request form

     

    Thanks

    0

Please sign in to leave a comment.

Powered by Zendesk