Lesson 1: From support requests to tickets Follow

From Request to Ticket (1 of 6)

Lesson 1: From support requests to tickets

Regardless of the type of customer support you provide, the one constant for all support organizations is that customers seek you out to help them resolve their issues. Here are some of the options that your customers have for contacting you:

  • Send an email
  • Fill out a support request form in your Zendesk Support portal
  • Fill out a support request form on your own web site
  • Call you on the telephone
  • Text chat with you
  • Send you a tweet
  • Post on your Facebook wall

All of these communication options are referred to as channels. You decide what channels you want to enable in your Zendesk and how your customers can reach you.

You can open even more ways of communicating with your customers by adding Apps to your Zendesk. These give you additional functionality and connect you to many popular internet products and services such as Salesforce, JIRA, and SugarCRM.

All support requests, from all channels, become Zendesk Support tickets. Tickets capture your customer's initial request for support and all the conversations your agents have with the customer along the way to solving their support issue.

Zendesk Chat

One of the most popular channels, and a favorite with customers, is live text chat. Your customers can either initiate a new chat session and create a new support request or chat about one of their existing unsolved tickets. The entire chat conversation between the agent and the customer is captured as a ticket in your Zendesk Support instance (or as an update to an existing ticket).


From Request to Ticket (2 of 6)

Try it yourself: Create a ticket now

If you've already set up your trial account, you can create a test ticket right now and start testing out Zendesk Support and see what a typical ticket looks like.

  1. Imagine you've just purchased a new product and something's not working correctly. You’re going to ask for help by requesting support using your email account. Send an email from an email account that you did NOT use to set up your Zendesk Support trial to your Zendesk account. You do this by simply addressing an email to support@thenameofyouraccount.zendesk.com. When you send the email, a new ticket will be created. 
  2. Log in to your Zendesk, then click the Views icon () in the sidebar.
  3. You'll find your new ticket in the Unassigned Tickets view. Click the title of that view.

  4. Click the title of the new ticket to open it.

We'll take a look at all the components of a ticket on the next page.

From Request to Ticket (3 of 6)

Anatomy of a ticket

With your new ticket open in front of you, you can see that the support request you submitted earlier is the first comment on this ticket. Above that you see that a new empty comment is open and ready for you (as the agent) to enter a response.

By default, a comment you enter as a Public Reply will be public and visible to everyone who views this ticket, including the person who requested support.

You can also add private comments (referred to as an Internal Note). The requester never sees these notes, they are used for internal communication only. For example, an agent may need to get advice from another agent to solve the requester's support issue. If you want to add an internal note, just click that tab.

Just below the title of the support request, you see the date and time the ticket was created and where the ticket originated from. In this case, the request was sent via email. Zendesk shows you what channel was used to generate the support request.

To the left of the ticket conversation you'll see the ticket fields. For now, we're only concerned with the Assignee field (we'll explain the others in another lesson). 

All tickets need to be assigned to an agent so that they can be solved and closed. Assuming you've just started your trial account, you're the only user in your Zendesk Support instance so in the next step you'll assign the ticket to yourself.


Ticket user roles

Every ticket contains the name of the person who requested support, referred to as the requester.

Once an agent is assigned to the ticket, the agent becomes the assignee.

If an agent opens a ticket for a customer, the agent is the submitter.

From Request to Ticket (4 of 6)

Try it yourself: Assigning a ticket to yourself

To see how to assign and open a ticket, take a look at this video: 

Assigning a Ticket to Yourself (0:44)

Try it yourself

If you'd like to try assigning and opening a ticket, follow these steps:

  1. Open the ticket you created, then click the down arrow next to the Assignee field and select your name.
  2. You can also set the Type and Priority fields. Each are drop-down lists with pre-defined options. Set Type to Problem and Priority to Normal.
  3. To save these changes click the down arrow next to the Submit button on the bottom right of the page. When you assign a ticket to an agent, it is automatically set to Open

After a ticket is assigned to an agent, they'll work to solve the ticket and ensure that the customer is happy. Some tickets can be solved with a simple standard response for a common issue such as resetting a password. Other issues that are more complex may require research, collaborating with other agents or people within your company, or gathering more information from the customer.

On the next page you'll see the typical journey a ticket takes from arriving in Zendesk Support to being solved.

From Request to Ticket (5 of 6)

The ticket life cycle

Each ticket has a life cycle. In other words, the stages it goes through as it arrives in Zendesk Support until it is solved.

Here are the typical stages:

  • When a Zendesk Support request first arrives, it becomes a ticket and is automatically set to New.
  • When an agent is assigned to the ticket, the agent will set it to Open.
  • If the agent has a follow up question for the customer, the agent will set the ticket to Pending, which means that the agent is waiting for more information from the customer.
  • When the agent resolves the issue, they will set the ticket to Solved.
  • Finally, after a certain number of days, the ticket is automatically Closed and archived for later reference. Agents will never manually set a ticket to closed (which is why you don't see it as an option on the Submit button).

Agents expect that when they set a ticket to solved the customer's issue has been resolved and the conversation around that particular issue is over. However, if the customer doesn't feel the same way, they can respond back to the agent by replying to the "ticket solved" email notification. When this happens, the ticket is reopened and it's the agent's job to follow up and go through the ticket lifecycle again.

In the next lesson, we'll show you how you can view your tickets using any number of criteria. For example, you can quickly see all the tickets that have been set to Solved, all the tickets assigned to a particular agent, and so on.

Knowing if your customers are happy

The final stage in the ticket lifecycle is understanding your customer's happiness with the support you provided. In Zendesk Support, you can enable a brief customer satisfaction survey to be sent after the ticket is solved. The customer is asked one simple question with two possible answers.

At Zendesk we've found this simple approach to customer satisfaction very effective because it requires very little time from the customer to respond and provide feedback on the support you provided.

From Request to Ticket (6 of 6)

A quick tour of the Zendesk Support agent interface

Before we move on to the next lesson, let's take a quick tour of Zendesk Support so you know where to find all the tools you'll use to manage your tickets and users and configure Zendesk Support.

Navigating the Agent Interface (1:15)
Have more questions? Submit a request

Please sign in to leave a comment.

Powered by Zendesk