Add 'Remove cc' trigger/automation action

152 Comentarios

  • Andrew J
    Acciones de comentarios Permalink

    @edwin - I'm don't know what in particular you are trying to accomplish.  But removing all CCs is relatively simple... I'll write a tutorial I think is best.

    See - Removing ALL CCs from a ticket via a Trigger/Target

    Hope this helps.

    0
  • Edwin Schukking
    Acciones de comentarios Permalink

    @AndrewJ: You're tutorial really helped, thanks!

    0
  • Mindaugas Verkys
    Acciones de comentarios Permalink

    Hi Edwin,

    But it dont help if you have to remove one agent from many tickets. For example for us by mistake one agent was added on CC for 1000 tickets with trigger...

    0
  • Andrew J
    Acciones de comentarios Permalink

    @ Mindaugas,

    Is there no way this could be done using json/http target?  I'm no expert on it, but I believe it's pretty flexible from what I have learnt.

    Maybe... (please research and test this - or maybe @wes can confirm or amend it!)

    {"ticket":  
    {"collaborators": remove;'name@domain.com' }
    }

    Then bulk edit the tickets with a macro to trigger that?

     

    1
  • Mindaugas Verkys
    Acciones de comentarios Permalink

    @Andrew workaround we can always find,

    but where is the logic to add CC and don't apply function for remove CC?

    In our case we solved the issue but it was possible to solve it in few minutes with one trigger, without looking another solutions. 

    0
  • Andrew J
    Acciones de comentarios Permalink

     

    @Mindaugas

    Could you share the trigger you used to solve this?

     

    0
  • Mindaugas Verkys
    Acciones de comentarios Permalink

    I asked why trigger is still not created, we solved with devtools not triggers

    0
  • Andrew J
    Acciones de comentarios Permalink

    Thanks Mindaugas,

    Probably a slight typo!  Yep a trigger to remove CCs is still a great idea.

    0
  • Paul Schöber
    Acciones de comentarios Permalink

    it definitely is.

     

    All that increases the control over what happens with CCs is very much appreciated.

    0
  • Benedikt Pruys
    Acciones de comentarios Permalink

    +1

    0
  • Caroline Scott
    Acciones de comentarios Permalink

    +1

     

    Please provide the ability to create a trigger or automation to remove all cc's. Agent training is one thing but human error can cause data protection breaches.

    0
  • Hamish
    Acciones de comentarios Permalink

    +1

    0
  • RachelKardos
    Acciones de comentarios Permalink

    +1

    0
  • Benedikt Pruys
    Acciones de comentarios Permalink

    +1 need removing one or all ccs.

    0
  • Mindaugas Verkys
    Acciones de comentarios Permalink

    you should enable to add custom email instead of only agents.

    0
  • Andrew J
    Acciones de comentarios Permalink

    @Mindaugas - I'm just another Zendesk user of course, but as a business owner I would think it would be commercially dangerous to make it easy to add ANY ccs.  This would enable considerable abuse of the platform, avoiding paying for agents etc.  

    0
  • Brendan Ittelson
    Acciones de comentarios Permalink

    +1 for removing CCs...

    0
  • Nathan
    Acciones de comentarios Permalink

    We're sending notifications to Slack so that our Inboxes stay clean. End-users send email to our ZD email address and CC our staff's email addresses (I guess thinking that more is better). Since we get notified in Slack, we have to delete the redundant email notification. As I write this, I realize that we could just create server-side Outlook rule to delete these, but...c'mon :-)

    0
  • Hemin Desai
    Acciones de comentarios Permalink

    +1

    0
  • Timon Zuelsdorf
    Acciones de comentarios Permalink

    +1

    0
  • Yahor Darashkevich
    Acciones de comentarios Permalink

    +1

    0
  • Michael F
    Acciones de comentarios Permalink

    My Support team will escalate tickets to Development. Dev are only interested in what the escalation note contains, not what responses go into the ticket in X number of days after being handed back to Support. I can't rely on people to remove CCs in 100% of cases so a remove CC trigger built to select which agents to remove in a given action would be awesome.

    0
  • Isaac Slape
    Acciones de comentarios Permalink

    I'd like to add a +1 to this post for a feature that was requested in 2012... However, since it's been a full 5 years, I think we can safely assume that ZD is not going to add this.

    @andrew - do we know if the API call that you posted works or if it needs revision?

    {"ticket":  
    {"collaborators": remove;'name@domain.com' }
    }

    @Mindaugas - can you share the solution that you used?

    0
  • Brett Youngberg
    Acciones de comentarios Permalink

    +1 We'd like this action/trigger available for Macros as well so you can mass update tickets and remove yourself or certain agents or all agents from being a cc on the ticket.

    0
  • Andrew J
    Acciones de comentarios Permalink

    @isaac - we only got to the point of removing all CCs, not individual ones.  Actually I had no use case for this so any effort I put in was only to help others in the community - run out of time for this.

    I think to make it work (having learnt just a little more code in the meantime) is that you'd need to fetch the existing CCs, then delete the CC to remove, then re-post the CCs.

    Post any code you've tried and maybe some clever brains will be able to troubleshoot it...

    @Brett - removing all CCs is possible. See - Removing ALL CCs from a ticket via a Trigger/Target.

    CC functionality is being reconsidered currently I believe...

    @Max McCal - can ability to remove CCs (agents) be included?  In my opinion - this would at simplest be an option in triggers etc.  

    I could see this being useful in a macro too to support a workflow that include adding a CC earlier in the process.

    1
  • Brett Youngberg
    Acciones de comentarios Permalink

    @Andrew - thanks for that, but we only to remove certain agents or yourself when mass updating tickets. We would want to keep all the end-user cc's. 

    I think removing all cc's would be nice option, but if we can add cc's using triggers/actions then we need to be able to remove cc's as well.

    0
  • Andrew J
    Acciones de comentarios Permalink

    @Brett - I agree :)

    Hoping Max will weigh in soon.  

    0
  • Robert Sutherland
    Acciones de comentarios Permalink

    +1

    0
  • Ariana Pagano
    Acciones de comentarios Permalink

    +1

    0
  • Matthew Knight
    Acciones de comentarios Permalink

    +1 I have recently started using Zendesk and quickly needed this functionality so we can escalate tickets outside of Zendesk and allow the user to respond without being added as a CC.

    I have put together an API call using liquid markup in a Zendesk trigger that does the trick but it isn't the most elegant solution:

    {% assign cc_list = "[" %}
    {% for cc in ticket.ccs %}
    {% if cc.email != current_user.email %}
    {% assign cc_list = cc_list | append: '"' | append: cc.email | append: '",' %}
    {% endif %}
    {% endfor %}

    {"ticket": {"collaborators": {{ cc_list | append: "]" | replace: ",]","]" }} } }

    The above just removes the current user's email address from the list of CC's.

    0

Iniciar sesión para dejar un comentario.

Tecnología de Zendesk