Build an IT Help Desk with Zendesk

Configure a professional IT ticketing system with automation in Zendesk.

Introduction

30 Second Summary

Every company has employees who forget passwords, need software installed, or deal with hardware that stops working. Someone has to track all those requests, prioritize them, and make sure nothing falls through the cracks.

In this project, you will set up a complete IT Help Desk ticketing system using Zendesk for a fictional 50-person tech startup called NovaTech. You will configure custom fields, automated responses, and ticket routing from scratch.

What You'll Build

A fully configured Zendesk IT Help Desk instance with custom ticket categories, organized views, canned response macros, and automated triggers that handle ticket routing for a fictional company.

By the end of this project, you'll have:

A Zendesk trial instance configured as an IT Help Desk with custom ticket fields that categorize common IT issues like password resets, software requests, and hardware problems.
Organized views and macros that let you manage your ticket queue by priority and respond to common requests with professional canned responses.
Automated triggers that route and prioritize tickets based on their properties, plus resolved test tickets demonstrating the full ticket lifecycle.
Secret Mission: Build a self-service Knowledge Base with help articles for your most common IT issues, reducing ticket volume.

Are there any prerequisites?

None. You only need a web browser and a personal email address. This project walks you through setting up a free Zendesk trial account that lasts 14 days with no credit card required.

Set Up Your Zendesk Trial Account

Every IT Help Desk needs a central system for tracking support requests. Zendesk is the most widely recognized ticketing system in the industry, and hands-on experience with it translates directly to job interviews for entry-level IT roles.

In this step, you will create a free Zendesk trial account for your fictional company (NovaTech), skip the AI setup wizard, and get familiar with the two main areas of the platform: the Agent Workspace and Admin Center.

In this step, get ready to:

Register for a Zendesk free trial account.
Skip the AI setup wizard and land on the Agent Home dashboard.
Explore the Admin Center and Agent Workspace.

Register for the Zendesk free trial

Zendesk offers a 14-day free trial that does not require a credit card. You will register using your personal email and configure the account as if you are the IT administrator at NovaTech, a fictional 50-person startup.

Open your web browser and go to https://www.zendesk.com/register/.
Enter your personal email address in the email field.
Enter your first and last name.
Enter your phone number.
For company name, type NovaTech.
For company size, select 1-9.
Choose a subdomain. Type novatech-it (or add numbers if it is already taken, e.g. novatech-it-123). This becomes your Zendesk URL.
Create a password and click Get started.

What is a subdomain?

Your subdomain is the unique address for your Zendesk instance. If you chose novatech-it, your full URL becomes novatech-it.zendesk.com. Every Zendesk account gets its own subdomain so teams can access their workspace from anywhere.

Check your email inbox for a message from Zendesk.
Click Verify my email in the verification message.

Don't see the verification email?

Check your spam or junk folder. The email comes from Zendesk and may take a minute to arrive. If it still does not appear, return to the registration page and request a new verification email.

Help me troubleshoot my Zendesk verification email.

Complete the initial setup wizard

After verifying your email, Zendesk drops you into an onboarding wizard that wants to set up an AI agent for you. You will skip this because configuring the system manually gives you deeper understanding of how each piece works.

When the AI agent setup wizard appears, click Not now to skip it.
You will land on the Agent Home dashboard.

Why skip the AI agent setup?

The AI agent automates ticket handling, but configuring everything manually first teaches you what each component does. Understanding the manual workflow is essential for IT Help Desk roles where you troubleshoot and customize the system.

You can always enable AI features later once you understand the foundation.

Take a moment to look around Agent Home. Notice the sidebar on the left with icons for Home, Views, and the Admin Center gear icon at the bottom.

Access Admin Center and explore the Agent Workspace

Zendesk has two main areas you will use throughout this project. The Agent Workspace is where you handle tickets day-to-day. Admin Center is where you configure the system (fields, views, macros, triggers).

Click the Admin Center icon (the gear/cog) in the sidebar.
Look at the sidebar sections: People, Channels, Workspaces, Objects and rules. You will use these in later steps to build your ticketing system.
Navigate back to the main Support interface by clicking the Zendesk logo or Go to Zendesk Support.
On the Home dashboard, find and click the sample ticket called Meet the ticket.

What am I looking at in this sample ticket?

This is the Agent Workspace. It is where agents read customer messages, write replies, and update ticket properties (like status and priority). The left side shows the conversation thread. The right side shows ticket fields and customer details.

Every ticket you create later in this project will open in this same workspace layout.

Your Zendesk instance is live and ready. Next up, you will create custom ticket fields that categorize the types of IT issues employees submit.

Create Custom Ticket Fields for IT Issues

Your Zendesk instance is live and ready for configuration. Now it is time to customize it for NovaTech's IT team.

Every IT Help Desk handles specific types of requests: password resets, software installs, hardware problems, network issues. Without a structured way to categorize these, tickets pile up in one undifferentiated list. Custom fields solve this by letting agents tag each ticket with its issue type, which powers everything you will build later (views, macros, and automation).

In this step, get ready to:

Create an "Issue Category" dropdown field with six IT issue types.
Create an "Affected System" text field for agents to note which system is impacted.
Verify both fields appear on tickets in the Agent Workspace.

Create an "Issue Category" dropdown field

The Issue Category field is the backbone of your Help Desk organization. Every ticket that comes in will be tagged with one of six categories, making it possible to route tickets, build filtered views, and measure which issues consume the most IT time.

Switch back to Admin Center using the gear/cog icon in the sidebar.
Click Objects and rules in the sidebar.
Select Tickets, then Fields.
Click Add field.
Select Drop-down as the field type.
Set Display name to Issue Category.
Under Permissions, select Agents can edit.
Under Field values, add the following six options (one per line):

Password & Account Access
Software Installation & Licensing
Hardware Issue
VPN & Network Connectivity
Email & Communication Tools
General IT Question

Check the Required to solve a ticket checkbox so agents must categorize every ticket before marking it solved.
Click Save.

Why make this field required?

Marking a field as "Required to solve a ticket" means agents cannot close a ticket without filling it in. This guarantees every resolved ticket has a category, which is critical for accurate reporting and for your views and triggers to work reliably.

Create an "Affected System" text field

Sometimes knowing the category alone is not enough. A text field lets agents note which specific system is affected (like "Outlook" or "MacBook Pro 2023"), giving you richer context when reviewing tickets.

Still on the Fields page, click Add field again.
Select Text as the field type.
Set Display name to Affected System.
Under Permissions, select Agents can edit.
Click Save.

Keep it simple for now

You are not marking this field as required. Not every ticket needs an affected system noted (for example, a general IT question). Making only the essential fields required keeps the agent workflow fast.

Verify your custom fields appear on tickets

Custom fields only matter if agents can see and use them. Let's confirm both fields show up in the ticket sidebar where agents work.

Navigate back to Support by clicking the Zendesk products icon (the four squares) and selecting Support.
Click + Add in the top toolbar, then select Ticket.
In the ticket sidebar on the left, scroll down to find your Issue Category and Affected System fields.
Click the Issue Category dropdown to confirm all six options appear.

Don't see your custom fields?

Make sure you clicked Save after creating each field. If you navigated away before saving, the field was not created.

Try refreshing the page. Custom fields sometimes take a moment to appear in the ticket sidebar after creation.

If neither works, go back to Admin Center > Objects and rules > Tickets > Fields and check that both fields are listed there.

Help me figure out why my custom fields aren't showing up on tickets.

Your tickets now carry structured data about every IT issue that comes in. Next up, you will build filtered views that use this Issue Category field to organize your ticket queue so nothing gets lost.

Build Views to Organize Your Ticket Queue

In the last step, you created custom ticket fields so every IT request gets properly categorized. Now you need a way to see those categorized tickets at a glance.

Right now, all tickets land in a single default queue. As NovaTech's IT admin, you need to spot urgent issues instantly and filter by category so nothing falls through the cracks. Views in Zendesk solve this by creating filtered lists that update automatically based on ticket properties.

In this step, get ready to:

Create a priority-based view that surfaces urgent and high-priority tickets.
Create category-specific views for password and hardware tickets.
Verify all three views appear in the Support sidebar.

Create an "Urgent & High Priority" view

Your first view surfaces any ticket marked as Urgent or High priority, regardless of category. This is the view you will check first every morning.

In Admin Center, click Workspaces in the sidebar.
Select Agent tools > Views.
Click Create view.
Set the Title to Urgent & High Priority.
Under Who has access, select Any agent.
Under Tickets must meet all of these conditions to appear in the view, click Add condition.
Set the condition to: Status category | Is not | Solved.
Under Tickets can meet any of these conditions to appear in the view, click Add condition.
Set the first condition to: Priority | Is | Urgent.
Click Add condition again and set it to: Priority | Is | High.
Under Group by, select Priority, then select Descending.
Under Order by, select Date created, then select Ascending.
Click Save.

Why two condition sections?

The "must meet all" section acts like AND logic. Every ticket in this view must be unsolved.

The "can meet any" section acts like OR logic. A ticket appears if it is Urgent OR High priority. Together, these two sections mean: show me any unsolved ticket that is either Urgent or High priority.

Create a "Password & Account Requests" view

Password resets are the most common IT request at any company. A dedicated view helps you batch-process these quickly.

Back on the Views page, click Create view.
Set the Title to Password & Account Requests.
Under Who has access, select Any agent.
Under Tickets must meet all of these conditions to appear in the view, click Add condition.
Set the first condition to: Status category | Is not | Solved.
Click Add condition again and set it to: Issue Category | Is | Password & Account Access.
Under Order by, select Date created, then select Ascending.
Click Save.

Why Ascending order?

Ascending order by date created means the oldest tickets appear first. This ensures no request gets stuck at the bottom of the queue while newer ones get handled.

Create a "Hardware Issues" view

Hardware problems often require ordering parts or scheduling desk visits. A separate view lets you plan these longer-turnaround items without losing them in the general queue.

Click Create view once more.
Set the Title to Hardware Issues.
Under Who has access, select Any agent.
Under Tickets must meet all of these conditions to appear in the view, click Add condition.
Set the first condition to: Status category | Is not | Solved.
Click Add condition again and set it to: Issue Category | Is | Hardware Issue.
Under Order by, select Date created, then select Ascending.
Click Save.

Navigate back to the main Support interface by clicking the Zendesk products icon and selecting Support.
In the left sidebar, click the Views icon.
Confirm that Urgent & High Priority, Password & Account Requests, and Hardware Issues all appear in the views list.
Click any of your new views to confirm it loads an empty ticket list.

Don't see your new views in the sidebar?

Make sure you selected Any agent under Who has access when creating each view. Views set to "Only you" appear under a separate "Your views" section, not in the shared list.

If a view is missing entirely, return to Admin Center and check that you clicked Save after configuring it. Unsaved views are not created.

Why aren't my Zendesk views showing up in the Support sidebar?

Your ticket queue is now organized into focused lists that update themselves automatically. Next up, you will create macros that let you respond to common IT requests in a single click.

Create Macros for Common IT Responses

Your views are set up and ready to organize incoming tickets. But what happens when you open a ticket and need to respond?

Many IT issues have the same solution every time. Password resets, VPN problems, and software requests all follow a predictable pattern. Typing the same response over and over wastes time and introduces inconsistency. Macros solve this by letting you save pre-built responses that fill in both the reply text and ticket fields with a single click.

In this step, get ready to:

Create a password reset macro that resolves tickets instantly.
Create a software request macro that acknowledges the request and sets expectations.
Create a VPN troubleshooting macro that walks users through common fixes.

Create the "Password Reset Instructions" macro

Password resets are the single most common IT request in any company. This macro gives you a one-click response that sends instructions and immediately marks the ticket as solved.

In Admin Center, click Workspaces in the sidebar.
Select Agent tools > Macros.
Click Create macro.
Set Macro name to Password Reset Instructions.
Under Available for, select All agents.

Now you will add the actions that this macro performs when applied. Each action changes something on the ticket.

Click Add action.
Select Comment/description as the action type.
Paste the following response text into the text field:

Hi there, I can help you reset your password. Please follow these steps: 1) Go to the company password portal at passwords.novatech.com 2) Click 'Forgot Password' 3) Enter your work email address 4) Check your email for the reset link 5) Create a new password following our security policy (minimum 12 characters, one uppercase, one number, one special character). If you are still having trouble after following these steps, please reply to this ticket and I will assist further.

Click Add action again. Select Comment mode and set it to Public.
Click Add action again. Select Status and set it to Solved.
Click Add action again. Select Issue Category and set it to Password & Account Access.
Click Create.

What does this macro do?

When you apply this macro to a ticket, it does three things at once. It posts a public reply with step-by-step password reset instructions. It sets the ticket status to Solved (because password resets are self-service). It tags the Issue Category so reporting stays accurate.

One click replaces what would normally take a minute of typing and two field updates.

You should see Password Reset Instructions listed on the Macros page.

Don't see your macro listed?

Make sure you clicked Create at the bottom of the form. If the button was grayed out, check that you have a macro name entered and at least one action added.

If the macro appears but shows the wrong actions, click the macro name to edit it and update the action settings.

help me fix my macro creation in Zendesk

Create the "Software Request - Received" macro

Software requests need a different approach. Instead of solving the ticket immediately, this macro acknowledges the request and sets a turnaround expectation while you review it.

On the Macros page, click Create macro.
Set Macro name to Software Request - Received.
Under Available for, select All agents.
Click Add action, select Comment/description, and paste the following:

Hi, thank you for submitting your software request. I have received it and will review it against our approved software list. Expected turnaround time is 1-2 business days. If this is urgent and blocking your work, please reply to let me know and I will prioritize it.

Click Add action. Select Comment mode and set it to Public.
Click Add action. Select Priority and set it to Normal.
Click Add action. Select Issue Category and set it to Software Installation & Licensing.
Click Create.

Why doesn't this macro set Status to Solved?

Unlike password resets, software requests require IT to take action (checking the approved list, purchasing licenses, installing software). The macro acknowledges the request and sets priority, but leaves the ticket open so you remember to follow up.

You should now see Software Request - Received listed alongside your first macro.

Create the "VPN Troubleshooting Steps" macro

VPN issues are tricky because they have many possible causes. This macro sends a standard set of troubleshooting steps and asks the user for diagnostic information if the steps do not help.

Click Create macro.
Set Macro name to VPN Troubleshooting Steps.
Under Available for, select All agents.
Click Add action, select Comment/description, and paste the following:

Hi, I understand you are having VPN connectivity issues. Let us try these troubleshooting steps: 1) Disconnect from VPN completely 2) Restart your computer 3) Ensure you are connected to the internet (try loading a website) 4) Reconnect to VPN using your credentials 5) If it fails, try switching between Wi-Fi and a wired connection. If none of these steps resolve the issue, please reply with: your operating system, the error message you see, and whether you are on home Wi-Fi or a public network.

Click Add action. Select Comment mode and set it to Public.
Click Add action. Select Issue Category and set it to VPN & Network Connectivity.
Click Create.

Why does this macro ask for diagnostic info?

The troubleshooting steps resolve most VPN issues on their own. But when they do not work, you need specific details (OS, error message, network type) to diagnose the problem further. Asking for these upfront in the macro saves a back-and-forth reply cycle.

All three macros should now be visible on the Macros page.

Verify your macros work by navigating back to Support.
Open any existing ticket or create a new one by clicking + Add > Ticket.
Click the Apply macro button in the bottom toolbar of the ticket.
Select one of your macros and confirm that the comment text and field changes populate correctly.

Apply macros faster with a shortcut

You can also type / directly in the ticket comment field to bring up the macro menu. This is faster than clicking the toolbar button when you already know which macro you need.

Macro not showing the right fields?

If Issue Category does not appear as an action option, make sure the custom field was saved correctly in Step 2. Go back to Admin Center > Objects and rules > Tickets > Fields and confirm the field exists.

If the macro applies but the comment is blank, edit the macro and check that the Comment/description action has text pasted into it.

help me troubleshoot my Zendesk macro actions

Your macros are ready to handle the most common IT requests with a single click. Next up, you will build automated triggers that handle ticket routing and prioritization without any manual action at all.

Automate Ticket Routing with Triggers

Your macros give you pre-built responses, but you still have to manually categorize and prioritize every ticket that comes in. In a real IT Help Desk handling dozens of requests a day, that manual triage eats up time you could spend actually solving problems.

This is where triggers come in. Triggers are automation rules that fire instantly when a ticket is created or updated, setting fields and applying tags without you lifting a finger.

In this step, get ready to:

Create triggers that automatically set priority based on issue category.
Submit test tickets to verify your entire Help Desk system end-to-end.
Apply macros to test tickets and confirm everything routes to the correct views.

Create a trigger to auto-set priority for password issues

Password resets are the most time-sensitive IT requests. If an employee can't log in, they can't work. You'll create a trigger that automatically marks every password ticket as High priority the moment it arrives.

Switch back to Admin Center using the gear icon in the sidebar.
Click Objects and rules in the sidebar.
Select Business rules, then Triggers.
Click the Ticket tab.
Click Create trigger.
Set Name to Auto-prioritize password resets.
Under "Meet ALL of the following conditions", click Add condition.
Set the first condition to: Ticket | Is | Created.
Click Add condition again.
Set the second condition to: Issue Category | Is | Password & Account Access.
Under Actions, click Add action.
Set the action to: Priority | High.
Click Create trigger.

What does this trigger do?

Every time a new ticket is created with the Issue Category set to "Password & Account Access", Zendesk immediately sets its priority to High. This happens before any agent even sees the ticket.

The condition Ticket | Is | Created ensures this trigger only fires on brand-new tickets, not on every update to existing ones.

Create a trigger to auto-set priority for hardware issues

Hardware problems like broken screens or failing laptops need tracking, but they're less urgent than locked accounts. This trigger sets a Normal priority and adds a tag so you can report on hardware requests over time.

Click Create trigger again from the Triggers page.
Set Name to Auto-prioritize hardware issues.
Under "Meet ALL of the following conditions", click Add condition.
Set the first condition to: Ticket | Is | Created.
Click Add condition again.
Set the second condition to: Issue Category | Is | Hardware Issue.
Under Actions, click Add action.
Set the first action to: Priority | Normal.
Click Add action again.
Set the second action to: Add tags | hardware_request.
Click Create trigger.

Why add a tag?

Tags are lightweight labels you can attach to tickets for filtering and reporting. Adding hardware_request automatically lets you later pull reports on how many hardware issues your team handles each month, without relying on agents to remember to tag manually.

You should now see both triggers listed on the Triggers page.

Don't see your new triggers?

Make sure you're on the Ticket tab (not the Messaging tab) on the Triggers page. If you clicked away before clicking Create trigger, your work may not have saved.

Help me figure out why my Zendesk triggers aren't showing up.

Create test tickets to verify your entire system

Now for the satisfying part. You'll create test tickets that simulate real employee IT requests and watch your triggers, views, and macros all work together.

Navigate back to Support by clicking the Zendesk products icon and selecting Support.
Click + Add, then select Ticket.
Set the Subject to Cannot login to my account.
In the ticket sidebar, set Issue Category to Password & Account Access.
Click Submit as New (or Submit as Open) to create the ticket.

After submitting, open Ticket 1 and check the Priority field in the sidebar. Your trigger should have automatically set it to High.

Create a second ticket with Subject Need Adobe Photoshop installed and set Issue Category to Software Installation & Licensing.
Create a third ticket with Subject Laptop screen flickering and set Issue Category to Hardware Issue.
Create a fourth ticket with Subject VPN disconnects every 10 minutes and set Issue Category to VPN & Network Connectivity.

What should I see on the hardware ticket?

Open Ticket 3 ("Laptop screen flickering") and check two things. The Priority field should show Normal, and scrolling down to the Tags section should reveal the hardware_request tag. Both were applied automatically by your trigger.

Now apply your macros to the relevant tickets to see the full workflow in action.

Open Ticket 1 ("Cannot login to my account").
Click the Apply macro button in the bottom toolbar.
Select Password Reset Instructions.
Notice how the macro fills in the response, sets the status to Solved, and updates the Issue Category field all at once.
Click Submit as Solved to save the changes.

Open Ticket 4 ("VPN disconnects every 10 minutes").
Click Apply macro and select VPN Troubleshooting Steps.
Click Submit to save.

Finally, verify that your views are filtering tickets correctly.

Click Views in the sidebar.
Click Password & Account Requests. You should see Ticket 1 listed here (if it hasn't been solved yet) or it may have disappeared since you solved it.
Click Hardware Issues. You should see Ticket 3 ("Laptop screen flickering") listed.
Click Urgent & High Priority. Any unsolved tickets with High or Urgent priority should appear here.

Views exclude solved tickets

Remember that all three views you built filter out solved tickets. If you applied the Password Reset Instructions macro (which sets status to Solved), Ticket 1 will no longer appear in your views. That's correct behavior.

Triggers didn't set the priority?

If your test tickets don't show the expected priority, check that you set the Issue Category dropdown before submitting the ticket. Triggers fire at the moment of creation, so the category must be set when you click Submit.

Also confirm your trigger condition uses "Ticket | Is | Created" (not "Updated"). You can edit an existing trigger from the Triggers page in Admin Center.

Help me troubleshoot why my Zendesk triggers aren't automatically setting priority on new tickets.

Secret mission

Build a Self-Service Knowledge Base

You have built a fully automated ticketing system. But what if employees could solve their own problems before ever submitting a ticket? In this secret mission, you will enable Zendesk's Help Center and publish Knowledge Base articles that reduce ticket volume through self-service.

Clean Up Your Resources

This project runs entirely on a Zendesk free trial with no credit card on file. There are no ongoing costs or charges to worry about.

Decide whether to keep your trial active for experimentation, let it expire naturally, or remove it early.

Resources you used:

One Zendesk trial instance at novatech-it.zendesk.com (free for 14 days, no credit card on file).

Keep everything running

No action needed. Choose this if you are still actively building or want to experiment further with your IT Help Desk setup.

Your trial remains active for 14 days from the date you signed up.
You can continue adding tickets, creating new macros, building triggers, or expanding your Knowledge Base.
Take screenshots of your completed configuration for your portfolio or to reference in job interviews.

Pause - I'll come back to this later

Let your trial expire naturally. Since no credit card was provided, no charges will ever be applied.

After 14 days, the trial simply expires and you lose access to the instance.
Your data is retained by Zendesk for a period in case you decide to purchase a plan later.
Take screenshots of your configuration before the trial ends if you want records for your portfolio.

Delete - I don't want to use this again

Remove your Zendesk trial account before it expires naturally.

Zendesk recommends letting trial accounts expire rather than canceling early. Since no credit card is on file, the trial will end after 14 days with no charges.
If you want to remove the account immediately, contact Zendesk Customer Support through the in-account messaging widget to request early cancellation.
Once expired or canceled, your tickets, custom fields, views, macros, triggers, Help Center articles, and all other configuration will be permanently deleted.

Nice Work!

You just built a fully functional IT Help Desk ticketing system in Zendesk from scratch. NovaTech's IT support workflow is now automated, organized, and ready to handle real employee requests.

You've learned how to:

Configured a Zendesk IT Help Desk instance with custom ticket fields categorizing six types of IT issues.
Built organized views, macros, and automated triggers that route, prioritize, and respond to tickets without manual intervention.
Processed test tickets through the full ticket lifecycle, verifying that automation rules correctly set priorities, apply tags, and populate professional responses.
Secret Mission: Built a self-service Knowledge Base with help articles to reduce ticket volume through employee self-help documentation.

Ready to quiz yourself?