Add 'Remove cc' trigger/automation action



Data ultimo post: 13 feb 2012

Dear Zendesk

It would be great to have a bit more control over 'cc' functionality via triggers.  In addition to being able to specify end users as cc on tickets via triggers (https://support.zendesk.com/entries/71421-add-cc-as-trigger-automation-action), please could you add a new trigger action 'remove cc'?

(Business case: allow the agent to send a one-off notification to another user, allowing them to add a on-time private comment to the ticket, but not copy them in on all future correspondence on a ticket.  In the interests of streamlining agent workflow as much as possible, I'd like to automate this process.)

Thanks


150

187

187 commenti

Ufficiale

image avatar

Bailey Whitaker-Lea

Zendesk Product Manager

Hi Everyone - 

New PM for Triggers & Automations here, catching up on the requests in the Community. It has been great to see all the feedback from you! I certainly understand your frustrations around needing more flexibility in your trigger conditions and actions. While we are actively working to improve Triggers this is not a feature we currently have planned, however it is in our backlog of potential improvements. 
Thank you for sharing your use cases as this helps our Product teams tremendously to know what is most important to you. 

0


Has there been any action on this? 

My team needs the ability to strip out all internal users from the cc line and add them as followers at a minimum.

I see in preferences I can choose to select Follower and CC but not Follower or CC and rejecting all CC adds from our own internal domain for customer tickets would help our process greatly.

 

0


Ufficiale

Hi Everyone - 

New PM for Triggers & Automations here, catching up on the requests in the Community. It has been great to see all the feedback from you! I certainly understand your frustrations around needing more flexibility in your trigger conditions and actions. While we are actively working to improve Triggers this is not a feature we currently have planned, however it is in our backlog of potential improvements. 
Thank you for sharing your use cases as this helps our Product teams tremendously to know what is most important to you. 

0


I've ran into this issue a couple of times.

Right now we recieve a lot of emails, up to 200, from the same sender over an hour. Most of them are caught in zendesks spam, but because there is a mailgroup on as cc, which our supportmail is part of, a mailoop is created, so even more mails are sent. It's this that we're trying to stop.

0


This is a classic example on how Zendesk doesn't care on what their users think. We are trying to make their product better. 10 Years later and this is still in the maybe pile. 

1


Great news!

Our app was approved by Zendesk and listed on the Apps Marketplace.

Always FREE for early customers.

Sign up to automatically remove the CCs based on your own criteria.

0


Yes, it will use a trigger & target to get notified of any new ticket, then the Zendesk REST API to remove the CCs as per configuration.

0


413833168293
So, this app of yours presumably uses the API to look at tickets and remove CCs when set criteria are matched?

0


Hey everybody,

Great news! 

Given the strong demand for this capability in the current thread, I decided to build a FREE app that would help Zendesk customers automatically remove all or specific CCs from any new ticket.

The app is work in progress, but you can register your interest from here.

1


Hi all, thanks for sharing your feedback. I appreciate you highlighting this gap in the current product functionality. Whilst it's not something we're implementing at this moment in time, it's on our radar as a potential improvement as we're rethinking triggers and automations in the coming year. Thanks again for sharing - it's always helpful to understand what's top of mind for customers as we develop our roadmaps.

0


I cannot remove all CC's. That was in my original comment 6 months ago. I need to remove specific CC's and leave other ones that are intentionally on the ticket, on there.

From my earlier comment: "This IS a Zendesk Issue because Zendesk hasn't given us a way to handle CC's that we literally cannot control a customer adding without remove ALL of their CC's, including their own, valid CC's."

0


Accedi per aggiungere un commento.

Non hai trovato quello che cerchi?

Nuovo post