Creating a ticket on behalf of the requester




What's my plan?







All Suites

Team, Growth, Professional, Enterprise, or Enterprise Plus










Support

Team, Professional, or Enterprise







Verified AI summary ◀▼
Create tickets on behalf of users to capture support requests, either publicly or privately. Public tickets notify users and appear in their activity list, while private tickets remain hidden until made public. Use private tickets for internal tasks, sensitive issues, or preparation. You can change a ticket from private to public, but not vice versa, ensuring flexibility in managing customer interactions.




There may be times when you need to open a ticket on someone else's behalf. For example, you may
be providing support to someone using a telephone (not using Zendesk, which creates a ticket
for you when you take the call), and you want to capture the support request in a ticket. You
can create a new ticket and then set the person you're providing support to as the ticket
requester.
Also known as proactive tickets, tickets created on behalf of an end user can be public (the
end user for whom it was created can view the ticket) or private (the end user cannot view the
ticket until it's manually made public).
This article contains the following topics:

Creating a public ticket for an end
user
Creating a private ticket for an end
user



Creating a public ticket for an end user

When an agent creates a public ticket for an end user, they will need
to add the end user as the requester. If the Requester field is not completed, the agent
will be set as the requester. When the end user is added to the ticket as the requester,
they can view and update the ticket.
When you create a public ticket for an end user, it triggers the following events:

The end user receives a notification that a ticket was created on their behalf, if you
have a trigger enabled for this
action.
The ticket appears in the end user's My Activities list.
The ticket appears in the end user's help center searches.

In most cases, a public ticket cannot be made private. However, in some cases, it's
possible. See Changing a ticket from public to
private.
To create a ticket on an end user's behalf

Hover over the +Add tab in the top toolbar, then select Ticket.

If private ticket creation is enabled, click Public Reply so the end user can
access the ticket immediately. If private ticket creation is not enabled, the ticket is
accessible by default, and no action is necessary.

If the requester is an existing user, begin entering the user's name, email domain,
phone number, or organization name in the Requester field, and the relevant results
appear. Select a user.
Note: Alternatively, you can open the user's profile, then click
User options in the bottom toolbar and select New ticket. The user's name
automatically appears in the Requester field.
If the requester does not
yet have an account, add them by clicking +Add user at the bottom of the search
results.


Enter the ticket data, then click Submit as New. The requester receives the
new ticket email notification, if you have a trigger enabled for this
action.





Creating a private ticket for an end user

Agents can open a private ticket that is not visible to the end user for whom they are
creating it, and can choose when (or if) to allow the end user to access the ticket. You can
create private tickets in the ticket interface or through a create event using the Tickets API. Private tickets cannot be created
through an inbound email message.
When a private ticket is created for an end user, the end user is included as the ticket
requester; however, some notifications and other ticket-related events are not triggered.
For instance:

The end user is not notified that a ticket has been created on their behalf.
Private tickets do not appear in the end user's My Activities list or help center
searches.

These events are triggered when the ticket is made public.

Note: If you don't have the option to create a private ticket, and your account
was created before April 8, 2017, you might need to ask an admin to turn on private ticket creation.
To create a private ticket on an end user's behalf

Hover over the +Add tab in the top toolbar, then select Ticket.
The Internal note option
should be selected by default.


If the requester is an existing user, begin entering the user's name, email domain,
phone number, or organization name in the Requester field, and the relevant results
appear. Select a user.
Note: Alternatively, you can open the user's profile and click
New ticket. The user's name automatically appears in the Requester
field.
If the requester does not yet have an account, add them by clicking
+Add user at the bottom of the search results.


Enter the ticket data, then click Submit as New.

All comments default to Internal note (private) from then on, including comments added via
email, voice recordings, and the like, until you make the
ticket public.


Using private tickets internally

There are a number of internal uses for private tickets. You can:

Make records of calls and meetings with your customers. These can be stored as
tickets, meaning you get a more accurate picture of your Support team's effort, without
bothering your customer.
Take action on issues that you can't share. Sometimes tasks need to be carried out on
behalf of a customer account -- investigations or corrective actions -- that might be
sensitive. With a private ticket, it can remain internal.
Prepare for an interaction before communications open up. Because private tickets can
be shared just by adding a public comment, you can use the ticket to gather materials,
prepare, or take notes, then make the ticket public when you're ready to address it with
the end user.
Send someone else a task. Throw together a private ticket, record some steps or
actions that need to be taken, and assign it to someone else, or set it in a queue for
the next available person.

You can associate a private ticket with a customer, meaning the record is there for
future reference. You get the value of reporting, whether that's accurate accounting of
what your team is doing, or the amount of work you're doing on behalf of a particular
customer or organization, without involving the end user until you're ready.



Changing a ticket from private to public

Private tickets can be made accessible to the requester and any newly added CC'd end
users. Once a ticket is made public, it cannot be made private again. However, internal
notes remain hidden from end users, as usual.
To change a ticket from private to public

Above the comment entry box, click Public reply.
Enter your comment, then click Submit.




Changing a ticket from public to private

If a public ticket has only one comment, you can make the ticket private by changing the
Public reply to an Internal comment. This works only on
tickets where there is a single public comment.
Note that when you change a Public reply to an Internal comment, you cannot make it
public again.




//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//

