Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Web Help Desk (WHD) > Web Help Desk (WHD) Documentation > Web Help Desk Getting Started Guide > Tech groups and request types > Plan tech groups and request types

Plan tech groups and request types

Created by Melanie Boyd, last modified by Melanie Boyd on Oct 10, 2016

Views: 1,161 Votes: 0 Revisions: 10

Before you begin creating Web Help Desk  request types and tech groups, consider what types you will need and which group will service each type.

Considerations for planning request types

As you plan request types for your organization, consider the following guidelines:

  • Hide internal request types from clients.

    Some request types are used only by techs (for example, a request for a system to be shut down for maintenance). Hide these types from clients to avoid confusion.

  • Client-facing request types should reflect the client's point of view (not the tech's point of view).

    Name request types to reflect the problem or symptoms that the client sees, not the solution or the underlying technical cause. Be sure to void specialized terms that clients would not know.
  • Use nested request types to subdivide broad parent categories.

    Request types can have multiple levels. Nested request types can be used to:

    • Provide more specific categories for reporting or categorizing FAQs.

    • Route tickets to different tech groups. For example, "Facilities > Plumbing" and "Facilities > Landscaping" could be routed to different tech groups.

    • Hide technical subcategories from clients. For example, a parent request type "Computer Problem" could have nested request types to describe specific types of problems (such as "VPN Connection Issue"). These nested types are hidden from clients to avoid confusion. Techs can use them to provide more accurate reporting on the types of issues users encounter.

  • Do not make your system too complicated or granular. Create only the types you need to route and categorize requests. Users can have difficulty selecting a type when there are too many, and can be more likely to choose a generic type such as “Other.” If in doubt, start with fewer types and add more if needed.

  • Before deploying the request types and tech groups in a production environment, test all request types in a QA or development environment. Verify that each request type is routed to the correct group.

Map request types to tech groups

Create a list of your organization's request types, and map them to the tech groups who can support them. The following table provides an example of groups mapped to request types.

Tech Group Request Types
Building Maintenance
  • Facilities > General
  • Facilities > Installation
  • Facilities > Clean Up
  • Facilities > Fixture / Office / Cubicle Repair
  • Facilities > Heating or Cooling Issue
  • Facilities > Light Bulb Replacement
  • Facilities > Plumbing Issue
Grounds Maintenance
  • Facilities > Landscaping Issue
Human Resources
  • HR > Benefits
  • HR > Benefits > 401K
  • HR > Benefits > Insurance
  • HR > Benefits > PSIP
  • HR > Employee Complaint
  • HR > New Hire Paperwork
  • HR > Personal Records


Last modified