Set Up an IT Help Desk with Spiceworks

Configure a real IT help desk, manage tickets, and automate routing rules.

Introduction

30 Second Summary

Every time you call IT support or submit a request to fix your Wi-Fi, reset a password, or get new software installed, your request enters a ticketing system. That system is how IT teams track every issue from the moment it comes in to the moment it gets resolved.

In this project, you will set up a real IT help desk using Spiceworks Cloud Help Desk, configure it from scratch, and work through realistic support tickets from submission to resolution.

What You'll Build

You will configure a professional ticketing system, simulate common IT support scenarios, and practice the full ticket lifecycle that hiring managers expect entry-level IT candidates to know.

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

A configured help desk with custom categories, priorities, and canned responses ready for incoming tickets.
Multiple resolved tickets demonstrating the full support workflow: triage, prioritization, documentation, and resolution.
A knowledge base article that documents a recurring IT issue and its solution for end users.
Secret Mission: Set up automated ticket routing rules that assign tickets to the right technician based on category.

Are there any prerequisites?

None. You only need a web browser (Google Chrome recommended) and an email address to sign up for a free Spiceworks account. This project walks you through everything from scratch.

Create Your Spiceworks Account

Every IT support team needs a central place to receive, track, and resolve user issues. Without a ticketing system, requests arrive via email, chat, hallway conversations, and sticky notes. Things get lost.

In this step, you will create a free Spiceworks Cloud Help Desk account. This gives you a fully functional ticketing system that professional IT teams use to manage support requests.

In this step, get ready to:

Create your free Spiceworks Cloud Help Desk account.
Complete the initial setup wizard with your organization details.
Explore the main dashboard areas.

Sign up for Spiceworks Cloud Help Desk

Spiceworks offers a free Cloud Help Desk plan with unlimited tickets and end users. You will create an account on their website and verify your email to get started.

Open Google Chrome.
Navigate to spiceworks.com.
Look for the option to join or log in (typically in the top right corner of the page).
Enter your email address and create your account.
Check your email inbox for a verification message from Spiceworks.
Click the activation link in the email to verify your account.

Why a free plan?

The Spiceworks Cloud Help Desk Core plan is completely free. It includes ticketing, incident tracking, alerts, reporting, and unlimited end users. The free plan supports 1-5 admin or technician seats, which is more than enough for this project.

Not receiving the verification email?

Check your spam or junk folder. The email may take a minute or two to arrive. If it still does not appear, try re-entering your email address on the signup page.

help me troubleshoot why I'm not receiving my Spiceworks verification email

Complete the initial setup wizard

After verifying your email, Spiceworks walks you through a setup wizard to configure your help desk. This is where you define your organization name and admin details.

After activating your account, log in to Spiceworks.
Navigate to the Help Desk tool from the left-side menu.
When prompted to set up your help desk, enter your organization name (this can be a fictional company name like NextWork IT Department).
Enter your domain name if prompted (you can use a placeholder like nextwork.local).
Complete the remaining prompts to finish the setup wizard.

What is the organization name for?

The organization name identifies your company or team in the help desk system. When end users submit tickets, they see this name. In a real job, this would be your actual company name.

For this project, any name works. You are simulating a real IT environment, so pick something that feels professional.

Having trouble accessing the Help Desk tool?

After logging in, look for a left-side navigation menu with tools listed. If you do not see the Help Desk option immediately, look for an IT Tools section or explore the navigation panel on the left side of the screen.

help me find and access the Help Desk tool in Spiceworks after logging in

Explore the main dashboard areas

Now that your help desk is set up, take a few minutes to explore the main areas you will be working in throughout this project.

Click on Help Desk in the left-side menu. This is where all your support tickets live. You will spend most of your time here.
Click on Device Inventory in the left-side menu. This area tracks the hardware and devices in your organization.
Look for the reporting or dashboard area that shows ticket statistics. This is where you will review metrics later in the project.

What are these three areas?

The Tickets area (inside Help Desk) is your command center for managing support requests. Every issue a user reports becomes a ticket here.

The Inventory area tracks the devices and software in your organization. Knowing what hardware a user has helps you troubleshoot faster.

The Reporting area shows you metrics like how many tickets are open, average response times, and which categories get the most requests. IT managers use these metrics to spot patterns and allocate resources.

Your help desk is live and ready for action. In the next step, you will configure it with custom categories and priorities that mirror how real IT teams organize their support workflow.

Configure Your Help Desk Categories and Priorities

Your help desk is live, but right now every ticket that comes in lands in the same pile with no structure.

In a real IT support environment, teams sort tickets by type and urgency so nothing falls through the cracks. In this step, you will set up the categories, priorities, and custom fields that make this possible.

In this step, get ready to:

Create ticket categories that match real IT support environments.
Configure priority levels with a clear escalation matrix.
Add custom attributes to capture device type and location.

Set up ticket categories

Categories are the first layer of organization for incoming tickets. When an employee reports a problem, the category tells your team whether it is a hardware failure, a software bug, a network outage, or something else entirely.

In the Spiceworks sidebar, click the gear icon to open Settings.
Look for a drop-down menu labeled with your organization's name.
Click on your organization's name to expand the section where you can manage ticket categories.
You will see some default categories already listed (such as email, hardware, and software).

You need five categories that cover the most common IT support scenarios. Add or rename categories until you have the following:

Add a category called Hardware.
Add a category called Software.
Add a category called Network.
Add a category called Account Access.
Add a category called Other.

Remove any default categories you do not need so your list stays clean.
Save your changes.

Why these five categories?

These categories mirror what you will find in most corporate IT environments. Hardware covers physical devices (laptops, monitors, printers). Software covers application crashes, installation requests, and licensing. Network covers Wi-Fi, VPN, and connectivity issues. Account Access covers password resets and permission requests. Other is a catch-all for anything that does not fit neatly elsewhere.

Having clean categories lets you spot patterns later. If 40% of your tickets are Account Access, that tells the team to invest in a self-service password reset tool.

Can't find the categories area?

Spiceworks hides category management behind a drop-down labeled with your organization's name inside the Settings page. Click on your organization's name to reveal the option.

If you still cannot locate it, make sure you are logged in as an admin. Only admin accounts have access to all settings.

Help me find the ticket categories section in Spiceworks Settings.

Configure priority levels

Not all tickets are equal. A company-wide email outage is more urgent than one person's request for a second monitor. Priority levels tell your team which tickets to tackle first.

Spiceworks includes built-in priority levels that you can assign to each ticket. Here is the priority matrix you will use throughout this project:

Critical = company-wide impact. Multiple departments or the entire organization cannot work. Example: email server is down for everyone.
High = department impact. A team or department is blocked. Example: the finance team's shared printer has stopped working.
Medium = individual user impact. One person is affected but can still do some work. Example: a single user's laptop is running slow.
Low = minor request. No immediate impact on productivity. Example: a request for a new desk lamp.

Navigate to the ticket management area by clicking the Tickets icon in the sidebar.
Open any existing ticket (or create a quick test ticket) to view the ticket sidebar on the right.
In the ticket sidebar, locate the Priority field. Click it to see the available priority options.
Confirm that you can select different priority levels from the dropdown.

What is a priority matrix?

A priority matrix is a framework that maps the urgency and scope of an issue to a priority level. IT teams use it to make consistent, objective decisions about which tickets to work on first.

Without a matrix, priority becomes subjective. One technician might mark a slow laptop as Critical while another marks it Medium. The matrix removes guesswork.

Create custom attributes for device type and location

Categories and priorities tell you what the problem is and how urgent it is. Custom attributes capture additional context that helps you troubleshoot faster.

Go back to Settings using the gear icon in the sidebar.
Look for a section related to custom attributes or ticket fields. Spiceworks supports custom attributes in the form of dates, lists, numbers, phone numbers, and text fields.
Create your first custom attribute with the name Device Type.
Set it as a list type so users can choose from predefined options.
Add list values: Laptop, Desktop, Mobile Device, Printer, Other.

Create your second custom attribute with the name Location.
Set it as a text field so users can type their office, floor, or remote location.
Save both custom attributes.

What do custom attributes do?

Custom attributes appear on the ticket submission form. When a user submits a ticket, they fill in these fields alongside the subject and description. Your team sees the extra data immediately, which means fewer back-and-forth messages asking "What device are you using?" or "Which office are you in?"

You can also use custom attributes in ticket rules for automated routing. You will explore this in the Secret Mission.

Verify your attributes are saved by navigating to the ticket submission form and confirming that Device Type and Location appear as fields.

Custom attributes not showing on the ticket form?

Make sure you saved the attributes after creating them. Try refreshing the page and checking the ticket submission form again.

If the attributes still do not appear, double-check that you created them as ticket attributes (not inventory attributes). The same Settings area can manage attributes for both tickets and devices.

Help me troubleshoot why my custom attributes are not appearing on the Spiceworks ticket form.

Your help desk now has structure. Every incoming ticket can be sorted by category, ranked by urgency, and tagged with the device and location. Next up, you will put this system to work by creating and resolving realistic support tickets.

Create and Manage Your First Tickets

Your help desk is now configured with categories, priorities, and custom attributes. The system is ready to receive tickets.

In a real IT environment, tickets arrive from end users who are stuck on something. Your job as a support technician is to receive each ticket, figure out what is happening, document your troubleshooting steps, and communicate the resolution back to the user. In this step, you will simulate that entire process by creating and resolving three realistic support tickets.

In this step, get ready to:

Create three realistic support tickets that simulate common IT scenarios.
Practice the full ticket lifecycle from receiving a ticket to closing it.
Document troubleshooting steps using internal notes on each ticket.

Create your first support ticket

Your first ticket simulates a common network issue: a user who cannot connect to Wi-Fi. This is one of the most frequent requests IT support teams handle.

Click the New Ticket button in the top-right area of your dashboard.
In the Summary field, enter Cannot connect to Wi-Fi.
In the Description field, enter a realistic problem description. For example: User reports that their laptop cannot detect any wireless networks since this morning. Other users on the same floor are connected without issues. User has already tried restarting the laptop.
Set the Category to Network.
Set the Priority to High.
Click Submit to create the ticket.

Why High priority?

This ticket gets High priority because a user cannot work without a network connection. It affects their entire department's productivity. Critical priority would be reserved for a scenario where the entire company loses connectivity.

Your ticket now appears in the tickets area. You should see it listed with the summary, category, and priority you just set.

Work through the full ticket lifecycle

Now you will simulate the process of an IT technician receiving this ticket, investigating the issue, documenting their work, and resolving it. This is the ticket lifecycle that every IT support role follows.

Open the Cannot connect to Wi-Fi ticket by clicking on it in your tickets list.
In the ticket sidebar, confirm the Category is set to Network and Priority is set to High.
Assign the ticket to yourself using the Assignee field in the sidebar.

Next, add an internal note to document your troubleshooting process. Internal notes are visible only to your IT team, not the end user.

In the ticket's comment area, select Internal Note.
Type your troubleshooting notes. For example: Checked with network team - no outages reported on Floor 3. User's laptop Wi-Fi adapter may be disabled. Asking user to check network adapter settings in Device Manager.
Save the internal note.

What are internal notes for?

Internal notes create a paper trail of your troubleshooting process. If the ticket gets escalated to another technician, they can see exactly what you already tried. This prevents duplicated effort and speeds up resolution.

In a real IT environment, hiring managers look for technicians who document their work clearly. Good internal notes show you can communicate technically and think systematically.

Now send a public response to the end user with your findings and resolution.

Switch from Internal Note to Public Response in the comment area.
Type a professional response to the user. For example: Hi, I checked with the network team and there are no outages on your floor. Please open Device Manager, expand Network Adapters, and confirm your Wi-Fi adapter is enabled. If it shows a down arrow, right-click it and select Enable. Let me know if this resolves the issue.
Save the public response.

Finally, close the ticket to mark it as resolved.

Add one more internal note confirming resolution: User confirmed Wi-Fi adapter was disabled after a Windows update. Re-enabled the adapter and connectivity restored. Closing ticket.
Change the ticket Status to Closed using the status option on the ticket.

What is the ticket lifecycle?

You just completed the full lifecycle: receive the ticket, triage it (assign category and priority), investigate the issue, document your work with internal notes, communicate with the end user, and close the ticket once resolved.

Every IT support role follows this exact pattern. The tools may differ (ServiceNow, Jira Service Management, Freshdesk), but the workflow is identical.

Create and resolve two more tickets

Now repeat the process for two more common IT scenarios. Each ticket gives you practice with a different category and troubleshooting approach.

Start with a password reset request, one of the most common tickets in any IT department.

Click New Ticket in the top-right area.
Set the Summary to Need password reset.
Set the Description to: User locked out of Active Directory account after too many failed login attempts. Cannot access email or shared drives. Needs password reset to resume work.
Set Category to Account Access.
Set Priority to Medium.
Click Submit.

Open the ticket and assign it to yourself.
Add an internal note: Verified user identity via phone. Reset password in Active Directory. Unlocked account. Instructed user to change password on next login.
Add a public response: Hi, your password has been reset and your account is now unlocked. You will be prompted to create a new password when you next log in. Please use at least 12 characters with a mix of letters, numbers, and symbols.
Change the Status to Closed.

Why is this Medium priority?

A password reset affects one individual user. They cannot work until it is resolved, which makes it more urgent than a Low request. However, it does not affect an entire department or the company, so it stays at Medium.

Now create the third ticket for a hardware performance issue.

Click New Ticket in the top-right area.
Set the Summary to Laptop running slow.
Set the Description to: User reports laptop takes over 5 minutes to boot and applications freeze frequently. Laptop is 3 years old, Dell Latitude model. User has not restarted in over two weeks.
Set Category to Hardware.
Set Priority to Medium.
Click Submit.

Open the ticket and assign it to yourself.
Add an internal note: Laptop has not been restarted in 14+ days. Likely memory leak or excessive startup programs. Recommended full restart and cleanup of startup items. If issue persists after restart, will check disk health and RAM usage.
Add a public response: Hi, based on the symptoms, your laptop needs a full restart to clear temporary files and release memory. Please save your work and restart now. If performance does not improve after the restart, let me know and I will schedule a time to check your hardware directly.
Add a final internal note: User confirmed restart resolved the slowness. Advised user to restart at least once per week to maintain performance. Closing ticket.
Change the Status to Closed.

Write notes like a professional

Notice how each internal note follows a pattern: what you checked, what you found, what you did, and what the outcome was. This structured approach to documentation is exactly what hiring managers look for when they ask about your troubleshooting process in interviews.

Check your tickets list. You should see all three tickets listed with a Closed status.

Ticket not showing as closed?

Make sure you changed the status on the ticket itself, not just added a comment saying it was resolved. The status dropdown is separate from the comment area.

If you cannot find the closed tickets, check whether your ticket list is filtered to show only open tickets. Look for a filter or view option that includes closed tickets.

Help me find my closed tickets in Spiceworks.

You now have three resolved tickets covering network, account access, and hardware issues. Next up, you will build canned responses and a knowledge base to speed up handling common issues like these.

Build Canned Responses and a Knowledge Base

You have resolved three realistic support tickets. Now it is time to build the tools that make handling future tickets faster and more consistent.

In this step, you will create canned responses for common issues and write a knowledge base article that end users can reference on their own. These two tools are how professional IT teams reduce repetitive typing and empower users to solve simple problems without submitting a ticket at all.

In this step, get ready to:

Create three canned responses for common IT scenarios.
Build a knowledge base article documenting a recurring issue.
Link the knowledge base article to a ticket category.

Create your first canned response

A canned response is a pre-written reply that you can insert into any ticket with a couple of clicks. IT teams use them to keep responses consistent and save time on questions they answer every day.

In Spiceworks Cloud Help Desk, open any one of your existing tickets (for example, the "Need password reset" ticket).
Look for a Canned Responses option in the ticket reply area. This may appear as a dropdown, a button, or a link near the response text field.
Click the option to create or manage canned responses.
Create a new canned response with the title Password Reset Instructions.
In the body of the response, type step-by-step instructions that walk a user through resetting their password. For example:

Hi there,

Here are the steps to reset your password:

1. Go to the company login page and click "Forgot Password."
2. Enter your work email address.
3. Check your inbox for a reset link (also check spam).
4. Click the link and enter a new password (at least 8 characters, one uppercase letter, one number).
5. Log in with your new password.

If you are still having trouble after following these steps, reply to this ticket and I will assist you further.

Thanks,
IT Support

What is a canned response?

Think of it as a saved template. When you get the same question for the fifth time today, you select your canned response instead of retyping the same instructions. The response appears instantly in the reply field and you can edit it before sending if needed.

This is especially valuable for password resets, which are the single most common ticket type in most IT environments.

Save the canned response.
You should see your new Password Reset Instructions response listed and available for future use.

Can't find where to create canned responses?

The canned responses feature in Spiceworks Cloud Help Desk is accessible from within the ticket reply interface. If you do not see it immediately, look for a small icon or dropdown near the text editor toolbar when composing a response.

help me find the canned responses feature in Spiceworks Cloud Help Desk

Create two more canned responses

A useful canned response library covers the questions your team answers most frequently. You will create two more responses to round out your library.

Create a second canned response with the title VPN Setup Guide.
In the body, type instructions for connecting to VPN. For example:

Hi there,

Here is how to connect to the company VPN:

1. Download and install the VPN client from the company software portal.
2. Open the VPN client application.
3. Enter the server address provided by IT (check your onboarding email).
4. Log in with your regular company username and password.
5. Click "Connect" and wait for the green status indicator.

If you see a connection error, make sure you are not on a restricted public network (airports, hotels sometimes block VPN traffic). Try switching to a mobile hotspot.

Thanks,
IT Support

Save the VPN Setup Guide response.
Create a third canned response with the title Printer Troubleshooting Steps.
In the body, type common printer troubleshooting steps. For example:

Hi there,

Here are some steps to troubleshoot your printer issue:

1. Check that the printer is powered on and shows a ready/green light.
2. Confirm the printer is connected to the network (check the Wi-Fi or Ethernet indicator).
3. On your computer, go to Settings > Printers and check that the correct printer is selected as default.
4. Try printing a test page from the printer settings menu.
5. If the test page fails, restart the printer by powering it off for 30 seconds, then turning it back on.
6. Try printing again after the restart.

If none of these steps resolve the issue, reply to this ticket with the printer model and location, and I will come take a look.

Thanks,
IT Support

Save the Printer Troubleshooting Steps response.

Why these three scenarios?

Password resets, VPN issues, and printer problems are consistently the top three ticket categories in most IT support environments. Having canned responses ready for these means you can respond to the majority of incoming tickets in seconds instead of minutes.

Confirm all three canned responses are saved by checking your canned response list. You should see Password Reset Instructions, VPN Setup Guide, and Printer Troubleshooting Steps available.

Build a knowledge base article

Canned responses help technicians reply faster. A knowledge base article goes one step further by letting end users find the answer themselves, before they even submit a ticket.

In Spiceworks Cloud Help Desk, navigate to the Knowledge Base section. Look for it in the main navigation or under a support portal area.
Click the option to create a new article.
Set the article title to How to Reset Your Password.
In the article body, write a user-friendly guide. Structure it with a clear problem statement, step-by-step solution, and a note about when to contact IT. For example:

How to Reset Your Password

Problem:
You cannot log in because you forgot your password or your account is locked.

Solution:
1. Go to the company login page.
2. Click "Forgot Password" below the login fields.
3. Enter your work email address and click Submit.
4. Check your inbox for an email from IT (check your spam folder if you do not see it within 2 minutes).
5. Click the password reset link in the email.
6. Create a new password. It must be at least 8 characters long and include one uppercase letter and one number.
7. Log in with your new password.

Still having trouble?
If the reset link does not arrive, or if your account remains locked after resetting, submit a help desk ticket and include:
- Your username
- The error message you see (if any)
- When the problem started

An IT technician will respond within 1 business hour.

What makes a good knowledge base article?

A strong article has three sections: a clear problem description (what the user is experiencing), step-by-step instructions (how to fix it), and an escalation path (what to do if the fix does not work). This structure matches how professional IT teams write documentation.

Writing for end users means avoiding technical jargon. Describe what they see on screen rather than what is happening behind the scenes.

Before saving, look for an option to assign a category or tag to the article. Select or type Account Access to link this article to your Account Access ticket category.
Save and publish the article.
Verify the article appears in your knowledge base by navigating back to the Knowledge Base section. You should see "How to Reset Your Password" listed and associated with the Account Access category.

Why link articles to categories?

When a knowledge base article is linked to a ticket category, the system can suggest it to end users when they start creating a ticket in that category. This deflects tickets before they even reach a technician. Fewer tickets in the queue means faster response times for the issues that truly need human attention.

Can't find the knowledge base section?

The knowledge base in Spiceworks Cloud Help Desk may be labeled as "KB" or appear under a portal or self-service section. Check the main navigation bar at the top of the dashboard.

help me find where to create knowledge base articles in Spiceworks Cloud Help Desk

You now have a canned response library and a self-service knowledge base article. Next up, you will review your help desk dashboard and explore the reporting metrics that real IT teams use to track performance.

Review Your Help Desk Dashboard and Metrics

You now have a fully operational help desk with canned responses and a knowledge base article. The next question any IT manager asks is: how is the help desk performing?

In this step, you will explore the reporting dashboard to understand key metrics, export a report of your resolved tickets, and interpret the data the same way a real IT support team does.

In this step, get ready to:

Explore the reporting dashboard and identify key metrics.
Export a report showing your resolved tickets.
Interpret your help desk data to identify category patterns.

Explore the reporting dashboard

Every IT support team uses metrics to spot trends and improve service. The dashboard gives you a quick snapshot of how your help desk is performing without digging through individual tickets.

In your Spiceworks Cloud Help Desk, click the Dashboard tab in the top navigation bar.
Look at the summary widgets on the page. Note the count of open tickets, unassigned tickets, and any response time metrics displayed.
Identify which ticket categories appear in the breakdown. Based on the three tickets you created (Network, Hardware, Account Access), you should see each category represented.

What are these metrics telling you?

The dashboard shows you the health of your help desk at a glance. In a real environment with hundreds of tickets, these numbers help you answer questions like: Are tickets piling up? Is the team responding quickly enough? Which categories generate the most work?

For your three-ticket setup, the numbers are small. In production, IT managers check these metrics daily to make staffing and training decisions.

What is a ticketing metric?

A ticketing metric is a measurable data point that shows how well a help desk is performing. Common metrics include average response time (how quickly the team replies), resolution time (how long it takes to close a ticket), and ticket volume by category.

Export a report of your resolved tickets

Exporting reports is how IT teams share performance data with managers and stakeholders. You will now create and export a report showing all your resolved tickets.

Click the Reports tab in the top navigation bar.
Click New report to create a new report view.
Name the report Resolved Tickets.
Set the filter to show only tickets with a closed or resolved status.
Confirm you can see all three of your resolved tickets listed in the report view.

Why filter by status?

Filtering by resolved status lets you isolate completed work from active tickets. In a busy help desk, this is how you produce end-of-week reports that show what the team accomplished.

Click the Export as... button to export the report.
Select CSV as the export format. The file downloads to your computer containing the tickets and columns in your current view.
Open the downloaded CSV file in a spreadsheet application (Google Sheets, Excel, or similar) to confirm your three tickets appear with their category, priority, and status information.

JSON is also available

Spiceworks also supports exporting reports as JSON. CSV is the more common choice for sharing with managers because it opens directly in spreadsheet tools.

Export button not appearing?

Make sure you are on the Reports tab and have a report view open (not the Dashboard tab). The export option is only available within a report view.

Help me find the export button in Spiceworks

Interpret the data like a real IT support team

Raw data means nothing until you ask questions about it. Real IT teams review their ticket data to make decisions about staffing, training, and process improvements.

Look at your report and identify which categories received the most tickets. With three tickets across Network, Hardware, and Account Access, each category has one ticket.
Consider what would happen if you had 100 tickets instead of 3. If 40% were Network issues, that would signal a need for infrastructure investment or a dedicated network specialist.
Look at the priority levels across your tickets. You have one High (Wi-Fi) and two Medium (password reset, slow laptop). In a real environment, a high proportion of Critical tickets would indicate systemic problems.

How do IT managers use this data?

Category distribution reveals where users struggle most. If Account Access tickets spike every Monday, maybe the password policy is too aggressive. If Hardware tickets dominate, it might be time for a hardware refresh cycle.

This pattern-recognition skill is what separates a reactive technician from a proactive IT professional. Hiring managers look for candidates who can read trends and suggest improvements.

Write a brief observation (2-3 sentences) summarizing what patterns you notice in your ticket data. Think about what you would recommend to a manager if this data represented a full month of activity.

Your help desk is now fully operational with resolved tickets, documentation, and reporting under your belt. Next up is the Secret Mission, where you will take your skills further by configuring automated ticket routing rules.

Secret mission

Set Up Automated Ticket Rules

So far, you have been manually managing every ticket that comes in. But what if your help desk could automatically route tickets to the right person, escalate critical issues, and send instant responses without you lifting a finger? That is what ticket rules do. This challenge takes you from using the system to configuring the system.

Clean Up Your Resources

This project runs entirely on Spiceworks Cloud Help Desk's free Core plan, so there are no ongoing costs. Decide whether to keep your help desk active for future practice, leave it idle, or request account deletion.

Resources you used:

Spiceworks Cloud Help Desk account (tickets, knowledge base articles, canned responses, ticket rules).

Keep everything running

No action needed. Choose this if you plan to keep practicing or want to reference your resolved tickets and knowledge base articles later.

Your Spiceworks account is free with no expiration date, so there is nothing to pay or shut down.
Your tickets, canned responses, knowledge base articles, and ticket rules all remain accessible whenever you log back in.

Pause - I'll come back to this later

Since the Core plan is free, there is nothing to pause or shut down. Your account stays available at no cost.

Log out of Spiceworks Cloud Help Desk.
Your data remains intact. Log back in anytime to pick up where you left off.

Delete - I don't want to use this again

Remove your Spiceworks Cloud Help Desk account and all associated data.

Send an email to community@spiceworks.com requesting that your account be deactivated and deleted.
In the email, mention that you want to fully close your Spiceworks Cloud Help Desk account and remove all associated data (tickets, knowledge base articles, and settings).
Spiceworks support will process the request and confirm when your account has been removed.

Nice Work!

You just built and operated a professional IT help desk from scratch. You now have hands-on experience with the exact ticketing workflow that entry-level IT support roles require.

Here's what you accomplished:

Set up Spiceworks Cloud Help Desk with custom categories, priorities, and attributes to mirror a real IT support environment.
Created and resolved realistic support tickets through the complete ticket lifecycle: triage, prioritize, document, respond, and resolve.
Built a canned response library and a knowledge base article to enable faster resolutions and self-service support.
Secret Mission: Set up automated ticket routing rules that assign tickets to the right technician based on category and priority.

Ready to quiz yourself?