"Requester can see this comment" default setting

67 Comments

  • Brad Bilotta

    Not sure why we have to ask for a simple setting to be added over the course of 3+ years...I can't imagine the programming for this would take all that long.  Please consider as this would make the solution more customizable and flexible for anyone's use case.

    2
  • skwitz

    Doesn't look like there's been much/any movement on this in 4 years, but Reddit would love to have this ability as well.

    0
  • Traci Lamm

    Really need this option too!

    0
  • Anna

    We'd love this at FutureLearn as well. We merge many tickets each day, and particularly with a COVID-related backlog we're not always able to get back to the user that same day. If we forget to uncheck the boxes we often end up with annoyed users, because they're getting emails about the ticket being merged before they get a response. Setting the default to unchecked feels like such a small thing but it causes a lot of frustration!

    0
  • daniel.savage

    Plus 1 

    0
  • Wouter Herrygers

    Hi there,

    We'd really like to have this at Lyreco as well. Merging tickets is part of the daily business of co-workers of multiple departments and although I don't have data for all groups I can safely say that we use this feature around 50 times per day within just the marketing department. Now that we are aware of the amount of extra communication merging tickets creates towards our clients, we ask our colleagues to manually untick these boxes every time they merge two tickets. It would just be such a quality of life improvement for the people working with the platform if there was an option to have the boxes unticked by default, given that we wouldn't ever want to send our clients more mails than necesary.


    I don't know how big of a technical challenge this would be and I definitely understand there are more critical developments that deserve priority, but even after 4 years people like myself end up finding this ticket. More so, given how frequently people seem to return to this thread just to chip in, I'm convinced a lot of the users would love to have this option.

    0
  • Jason Katz

    Adding an additional +1 on this request. This lack of functionality creates a significant number of issues for our Members

    0
  • Maik Künnemann

    We also need this setting!!

    0
  • Josh Kelly

    Echoing all previous posts, Prodigy would love this setting - I can't think of a reason this would be on by default, why would a customer care if their issue has been merged together?

    As it stands, the setting being on by default just confuses end users when it is not unchecked, and just adds 2 extra clicks for every ticket which consistently doubles the time it takes to slim out duplicate tickets. We run into this between 50-100 times every day.

    I would love to see any efficacy report that shows having this setting enabled is the preferred state for most businesses.

    1
  • Mindy B

    This would be a huge benefit to us as well we merge probably 50 tickets a day and this is a pain.

    The suggested workaround on another thread to default agent comments to internal is not a valid workaround and would likely create more issues than resolve any.  

    1
  • Michael Eugster

    Same here: We need this setting, too.

    0
  • Hannah Ehrlich

    Just adding my note and upvote that defaulting merge to private would be more than ideal.

    0
  • Roman Hladkyy

    Greetings! The setting would be benefitial for us, too.

    0
  • Trevor Piercey

    This would be great. (to have this as a setting as I'm sure there are use cases that would require it) but for us, it doesn't make any sense to tell the customer their request is being merged into another. So would be really helpful to see this unchecked by default. Thanks!

    0
  • Russ Milton

    Hi, This would be ideal to have as a default, we have to recommend to all users to untick every time they merge a ticket so it would far easier if this was off by default (or if we could set this by default as admin via the role.)

    0
  • Chris Iacofano

    Our team would find this extremely helpful, as we likely merge 50+ tickets on an average day without sending comments to the requestor. My former colleague was the first comment in this thread 5 years ago, and the need for this feature has only increased in our case. 

    1
  • Fintan Maher

    5 years on, this is still something every single company would want. Please disable the public comment by default for merging tickets. 

    1
  • Sara Pearson

    Is this feature still not available? 

    0
  • Andrew S

    Upvoted on the original post, but for context, we merge maybe 100 tickets per day across the organization, and we've even got snarky emails back from customers saying "well if you closed it, then my request is fulfilled, right?"

    3
  • LockitNetwork Support 1

    We need this useful feature as well.

    0
  • LVB

    I cannot believe this is not possible. After FIVE YEARS!?

    1
  • Yunus Unia

    You will never get this feature. Just switch to Freshdesk/Freshservice. I know Freshservice by default doesn't send anything to the client/customer when merging tickets. You might even get better pricing.

    0
  • Sorin Alupoaie

    In case it helps, I've built this app recently that automatically merges new tickets that are found as duplicates (same requester & additional configured criteria). Like a "virtual" agent that sits on top of the queue constantly looking for duplicates. By default it adds a private comment to the merged ticket, but you can configure it to add a public comment instead.

    Last but not least, it's affordable (€40 per month with unlimited agents & tickets) and easy to use.

    -1
  • Gilles Vanagtmael

    You can easily achieve this by disabling the option "non-email conversations are public by default"  (Tickets - Settings - comments)

    ---

    Note from the Zendesk Community Team -- the label for this setting has been updated to “Agent comments on all tickets are public by default", because the setting applies the email channel as well.

    0
  • Annie MacMillan

    I don't have that option available. Is there something I need to do to get that option?

    https://capture.dropbox.com/UDj6GWezIGIEAIGL

    0
  • Dane
    Zendesk Engineering
    Hi Annie,
     
    That option is not available for accounts that does not have Agent Workspace. You'll need to enable it to have that option.
     
    -1
  • crystal

    Our Agent Workspace is enabled (On), but we don't have the setting for "non-email conversations are public by default" - I can't find that setting anywhere in the Admin Center...

    0
  • Cheeny Aban
    Zendesk Customer Care
    Hi Crystal! 

    I can see that you already lodged a support request regarding this inquiry. Rest assured that we'll do our best to help you identify why the setting is not showing on your end. Thanks! 
    -1
  • Anita Nayob

    I don't seem to be have the setting available on our instance aswell: "non-email conversations are public by default"

    Was there a resolution to this? 

    0
  • CJ

    I've never heard of the setting referenced above "non-email conversations are public by default" , also don't have it despite using Agent Workspace. It doesn't track to me that a setting related to agent replies via email or not, would have any impact on the status of merging ticket comments. I already have the similar setting off, and I can confirm is has no impact on merge situation outlined. 

    0

Please sign in to leave a comment.

Powered by Zendesk