It's possible to change an existing ticket's requester to someone else and, if a requester belongs to more than one organization, you can also change the organization their ticket is assigned to.
This article includes the following sections:
Changing the ticket requester
You may want to change the user designated as the ticket requester if someone sent in a support request on someone else's behalf. The user who you want to set as the requester must be an existing user.
To change the ticket requester
- Open the ticket where you want to change the requester.
- Click directly into the Requester field in the ticket properties panel to change the requester.
- Begin entering a user's name, email domain, or organization name and the relevant results appear. Select the user. If the user does not yet have an account, add them by clicking +Add user at the bottom of the search results.
- Click Submit to save the ticket update.
After you've changed a requester, you can later see who the original requester was by checking the ticket's events and notifications.
Changing the ticket requester's organization
On Professional and Enterprise, end-users can belong to multiple organizations. If a ticket's requester belongs to multiple organizations, the ticket can be assigned to any of the requester's organizations.
When a user who belongs to multiple organizations submits a ticket by email, it is assigned to their default organization. When the user creates a ticket in your Help Center, or when an agent creates a ticket on behalf of the user, the user or agent can select the organization for the ticket. You can change the organization for a ticket, if necessary.
When a ticket is created through an API call, the ticket is assigned to the requester's organization_id as specified in the call. If the call doesn't specify an organization_id or specifies an organization_id that the requester isn't part of, the ticket is assigned to the requester's default organization.
When a requester is removed from an organization, any tickets associated with that user and that organization, will be assigned to the user's default organization if the user belongs to multiple organizations. If the user does not belong to multiple organizations, the tickets will not be associated with an organization.
- When an organization is deleted, any tickets associated with the deleted organization will be assigned to the requester's default organization. If the organization that was deleted was the requester's default organization, one of the requester's other organizations will be promoted to default, then any working tickets will be associated with the requester's new default organization. If the user does not belong to multiple organizations, the tickets will not be associated with an organization.
- In the ticket, click the current Organization, then select one of the requester's other organizations.
If the requester does not belong to multiple organizations you will not see the Organization field on the ticket. You can only choose an organization that the requester belongs to.
The organization for the ticket appears in the ticket and at the top of the ticket.