Automate / trigger the change of a requester

4 Comments

  • Nicole Saunders
    Zendesk Community Manager

    Thanks for sharing this request, Chris. Can you provide some additional detail about your use case? It's helpful for the product manager to understand how frequently this need arises, why existing functionality or workarounds doesn't solve the issue for you, and how much of an impact this has on your day-to-day. 

    If other users need similar functionality, please up vote Chris' post and add your own use case in the comments below. 

    0
  • AKW Admin

    I think you should be able to do this with a kind of complicated workaround.

    Create an HTTP Target and a Trigger to notify this Target. In the JSON that you're sending to the Target, it should be possible to figure out the first CC with Liquid markup and then that as the requester. 

    This is how the target notification would look like (kind of): 

    {% for cc in ticket.ccs %}
    {% if forloop.first == true %}
    {
    "ticket": {
    "requester": {
    "email": cc.email
    }
    }
    }
    {% endif %}
    {% endfor %}

    I'm not an expert with Liquid markup though, so you'd need to test and play around with this a little bit. 

    1
  • Ian

    Nicole Saunders 

    Our use case would consist of automating a switching of the requester email upon ticket creation, so that all notifications (including the immediate "We've received your request") & comments are kept between the updated requester & Support staff.

    I'd like to use a custom field - "User Email" - to refer to who the updated requester is, because tickets will be submitted on behalf of the actual requester/user from an external support partner (who should not receive follow-up). Requiring this particular field on the ticket form appears to be the best way of pulling that key info for us to redirect the reply & any notifications in a manual sense, but only after an initial "We've received your request" email has first gone out to the external support partner's email unnecessarily. 


    For context on a potential approach I explored, Email Targets do not appear to be usable here. There's no way to consistently pre-add the users in question, given there is a sizeable, ever-changing base of potential requesters - or to automate the requester switchover that I've found as of yet. 

    1
  • Pete

    This would be very helpful for us as well.

    Many times the IT Staff receives an automated email notifications or alerts from products or services we use, these emails typically come from a "noreply@domain.com" , "accounts@domain.com", or "support@domain.com". When we forward this email to Zendesk, the ticket is created on their behalf. Sometimes causing email loop between ticketing systems as well, or the external party viewing communication within our internal process.

    We would prefer an automation or trigger option which would change the requester of an email to be automatically changed when the initial requestor matches a predefined list of addresses. 

    1

Please sign in to leave a comment.

Powered by Zendesk