"Requester can see this comment" default setting



Data ultimo post: 28 giu 2016

Hi,

For us, when merging tickets, the vast majority of use cases do not require the requester to have the ability to see the comment/reply letting them know the ticket was merged.

It would be a huge time saver (and also helpful to avoid human error) if we could have a setting to set this as disabled/unticked by default.

 

Cheers.


124

88

88 commenti

Please make this update Zendesk.

2


2025 still no update.

+1 - A must!

1


I have read the entire thread of comments and agree with all - I have held off using this feature for the sole purpose that we cannot take the risk of the customer being informed - we merge tickets that contain sensitive data and it is vital we do not cause any confusion for our customer.  Please consider this for development, it seems like this will be a welcome update for all! 

1


Nicole at Acuity Scheduling here! Appreciate this being considered for this year as mentioned in Shawna's post back in May. 

 

Removing this as a default at a minimum would be an efficiency gain for those of us that need to manually merge tickets as well as create a clearer customer experience. For my  that don't normally merge tickets un-clicking BOTH tick boxes can be missed and the customer ends up reaching out confused and frustrated. 

2


We never want customers to know that their tickets have been merged. We'd love to see these checkboxes in the merge interface disabled by default or configurable to never be an option for agents. 

3


+1 to this feature - this is an absolute must. We just had a close call. We had a huge bulk merge and the setting was not disabled so 90+ people got an email and had no idea why. 

 

We need to either be able to turn off bulk merges, set a default setting or remove the option to change the default. This is an absolute must as this can have such a huge human error rate.

We are looking for 3 changes in behavior:

  1. Ability to set the default so that we have a consistent experience
  2. Ability to set a default with no settings to adjust it at time of merge
  3. Restricting access so no merges can be completed for ticketw with different requesters, org, groups, etc

2


Hey everyone, thank you for taking the time to provide us with this product feedback. We apologize for the delay on our end in providing you with a response to the feature request.

 

I work in managing our customer product feedback forums and have been in communication with the product team that owns this area. They noted the following: this is a great feature request and we have added it to the backlog for future consideration. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community. 

 

If you are interested in learning more about this and other features being built please make sure to check out and follow our Community eventsWhat’s New Community Topic, and Zendesk Updates. Again, we apologize for our delay and appreciate you being a valuable Zendesk Community member.

 

Thank you again for your feedback and for being a valuable customer with Zendesk.

-2


My team's SOP is to uncheck the boxes. We never let customers know we are merging tickets - can't wait to have this be a default option!

 

0


We un-check the 'requester is notified of merge' 100% of the time. We do not have any use cases for notifying a requester that their ticket is merged.

Upvoting that this is needed! We would like the default to be that this box is un-checked. 

0


Guys, seriously. It's a default option, you must be able to change it easily - not referring us to external apps and extensions...

0


Accedi per aggiungere un commento.

Non hai trovato quello che cerchi?

Nuovo post