Updating ticket requesters and organizations

Return to top


  • Wendell Joost

    We've notice that when we change the Requester for a ticket, the new Requester gets notifications when a Public Reply is added, and the old Requester gets notifications of the Public Reply and the Internal Note (to include the text of both Public Reply and Internal Note.)

    Is there a way to change Requester and ensure that the old Requester stops receiving notifications?

  • Jim
    Zendesk Customer Care

    Hi Wendell!

    The built-in default trigger "Notify requester and CCs of comment update" should help you with that. You don't have to update the conditions on that trigger since it's already set up the way you described it by default; not unless you configured the trigger's conditions.

    If the trigger uses the "(requester)" or "(requester and CCs)" value for the "Email user" > "(requester)" action, that'll always keep up with whoever the current ticket requester is. With that setup, you don't need to change anything in the trigger itself.

    Important note as a privacy/data security red flag. If the trigger's email notification includes a placeholder like {{ticket.comments_formatted}}, the new requester would be able to see the previous conversation between the support agent and the old requester. That could be alarming if the previous requester sent over their credit card number or provided any extremely sensitive information. I wouldn't suggest using a placeholder like that if you plan on changing ticket requesters often. Instead, use a placeholder that only looks at the latest comment like {{ticket.latest_comment}}.


    Customer Advocacy Team

  • Eli

    I'm wondering about the behavior of ticket updates when a requesters organization gets changed.  We are seeing that tickets created with a requester that dons't belong to an organization don't appear to update in data received via the api when they eventually do get added to an organization.  That is, old tickets organization ids stay as null. 

    Do requester organization updates cascade to all tickets or only some?  



  • Giuseppe
    Zendesk Customer Care

    Hi Eli,

    Tickets that are in status other than Closed can still be updated. This means, the changes mentioned in the article above applies to tickets in New, Open, Pending, On-hold, and Solved tickets. When you change a requester's organization (assuming that this requester only has one organization), then the requester's tickets will be updated.

    Closed tickets, however, will not be affected, because closed tickets can no longer be edited (see Can I edit closed tickets?). Once a ticket is Closed, ticket properties, including Organization, will remain the same even if you change the requester organization. 

  • Travel Syndication Technology

    Can I update the requester via the API? I need to update the requester on hundreds of tickets and I'd rather not do it one by one.

  • Dave Dyson
    Hi Cyn –
    You sure can! You'll want to use the Update Many Tickets endpoint in the Tickets API, which will allow you to update up to 100 tickets at a time: Update Many Tickets
  • Travel Syndication Technology

    Thank you, Dave!

  • Maky

    Hi @...

    How can I automatically change the ticket organization for a user who has many organizations depending on the type of request using triggers? I was trying to do it using organization tags or fields but it's not possible.



  • Arianne Batiles
    Zendesk Customer Care

    Hi Maky

    An organization cannot be set or changed through triggers and automations. The organization can has to be set upon ticket creation or manually updated by an agent in the ticket. 


Please sign in to leave a comment.

Powered by Zendesk