Why do replies to email-target notifications create a new ticket?

Have more questions? Submit a request

9 Comments

  • Piotr Szlazak

    Hello,
    I don't agree with this statement:
    "The target notification system is not designed to thread to an existing ticket and it is expected behavior that a new ticket would be created".

    It creates strong confusion for email receivers - how can they decide if they can replay to received notification w/o creating new ticket?
    We are currently adding warning, like 'Please do not replay', but still sometimes this is ignored and we have to struggle with tickets created by accident.

    The best would be to have option to configure behavior for email targets. Either general setting for Zendesk instance or individual one for each email target.

    Regards,
    Piotr Szlazak

    1
  • Nicole - Community Manager

    Thanks for the feedback, Piotr. 

    0
  • Piotr Szlazak

    Hi,
    I applied small workaround - using appropriate placeholder I'm adding encoded ticket id to the subject of notification pushed using email target:

    [{{ticket.encoded_id}}]

    Please note that square brackets are mandatory.

    This way Zendesk will recognize to which ticket, received email should be added.

    Regards,
    Piotr Szlazak

     

    <Edited by Zendesk to remove an outdated link>

    3
  • Kim Lake

    I am surprised at this statement too - "The target notification system is not designed to thread to an existing ticket and it is expected behavior that a new ticket would be created."

    As the target notification is added to the existing ticket history, I would absolutely have expected the reply to update the existing ticket rather than creating a new one.

    I don't know how feasible adding customers as CCs on their own tickets by automations using targets is, but thankfully a workaround has been found and shared by another customer (to call out, it'd be nice if Zendesk were able to share these tips when answering the question rather than relying on customers finding a way for themselves).

    Separately, (I can't seem to access the link Piotr provided above - is this locked? If so, can ZD provide summary of the details/conversation it contained? Thanks!

    0
  • Jessie Schutz

    Hi Kim!

    The link Piotr provided was to a 3-year-old Product Feedback thread; that post has since been archived, which is why you're not able to access it. I've gone ahead and removed the link from Piotr's comment. 

    As far as the information contained in that thread, one of our Product Managers explained that one of the ways we identify incoming tickets is by checking in-reply-to and references headers for our encoded id. If that encoded id is present, the incoming message is added to the corresponding ticket.

    1
  • Kim Lake

    Ah thanks for that Jessie

    0
  • Dave Draxyl

    Jessie,

    I'd suggest that Piotr's workaround be added to the main Email Target articles that Zendesk has provided, including the one at the top of this page and perhaps this one: https://support.zendesk.com/hc/en-us/articles/203660866-Notifying-External-Email-Addresses

    The ability to forward tickets (besides CC) and allow the ticket to be updated via response to that forward seems to be highly desired by Zendesk customers, based on all the similar threads about it. 

    I had to dig more than necessary to find this solution, but am happy I found it among the comments here. 

     

    0
  • Brett - Community Manager

    Hi Dave,

    Most likely this hasn't been added to our documentation because this workflow is not supported by us. That being said, I agree we could make this information readily available to users in need of the same functionality. I'll see if I can spin up a Community Tip that includes this workflow and provide a link here to help provide visibility.

    Thanks for sharing this with us!

    2
  • Dave Draxyl

    Brett,

    That would be awesome and, I think, greatly appreciated by the community.

     

    Thanks for the swift follow up!

    0

Please sign in to leave a comment.

Powered by Zendesk