Classify technicians into groups so that incoming requests are categorized and distributed to technicians based on their expertise.
By configuring group emails, you can manage multiple groups with specific email addresses. For example, hardware@domain.com and network@domain.com can be linked to two different groups in the same site. Emails sent to these addresses are automatically assigned to the respective groups.
You can also restrict technicians to view only requests within their own group. Refer to the
Roles for more details.
Create a Technician Group
- Go to Setup > Users & Permissions > Technician Groups.
- Select the customer from the filter in the header.
- On the list view, select the site from the Filter by Site drop-down.
- Click New Group.
- Enter a name for the group and add a brief description in the respective fields.
- The site will be auto-populated based on the filter selected in the list view. This field cannot be edited.
- Select the technicians that you wish to add to this group from the Available Technicians list box and click
to move them to Selected technicians in this Group.
- Under the Select technician(s) for notifications section, you can choose to notify technicians in the group when a request is added, updated, or left unpicked. To do this,
- Select the corresponding check box of the required notification.
- Choose the technicians to be notified from the Select Technician drop-down.
- For notifications on unpicked requests, specify the duration after request creation when the notification should be sent.

These notification settings only allow you to select the technicians who should receive the notifications. To send the notification, you need to enable the following under Setup > Automation > Notification Rules:
- Notify Group technician by mail when a request is added to Group.
- Notify technician by mail when a request is unpicked in Group.
- If you wish to assign the incoming requests to the group automatically, enter the Group Email. Each group can have multiple email IDs. Specify the email ID separated by commas or semicolons.
- Specify the Sender's Name and the Sender's Email. The sender's name will be mentioned in outgoing emails.
- You can also assign group-level organization roles to technicians in the group. Under Assigned Organization Roles, select the role and user from the drop-downs.
- Finally, click Save.
Edit/Delete Groups
You can edit/delete technician groups from the list view.
- Click
against the group to edit it.
- To delete groups, select the groups using the check boxes and click Delete.
If you delete a group that is being used in a request, the group will be inactivated. You can view these groups under the Inactive Groups tab. To activate inactive groups, select the groups in the list view and click Mark as Active.
Related Articles
Configure Holiday Groups
Bundle holidays into holiday groups and apply them to various sites or technician groups. You can create holidays in each holiday group and also import holidays across holiday groups. Holiday groups are used to calculate request completion time, SLA, ...
Assign Technician or Group to Requests
Each technician owns a request and handles it from the time assigned to the time it is closed. Role Required: SDAdmins; Technicians with Assigning Technician permission To assign a technician to a request, Go to the Requests module and click the ...
User Groups
Classify users in your help desk instance into various groups based on certain criteria. You can allow/restrict users to access certain items in the instance via user groups. To configure user groups, go to Setup > Users and Permissions > User ...
Technician Auto Assign Use Cases
Technician Auto Assign Pointers The Technician Auto Assign setting is applicable for incident and service requests only. You can assign requests to technicians automatically on the following basis: Round Robin: Technicians are assigned to the request ...
Asset Groups
Asset Groups Organize assets by grouping them manually or based on certain asset properties. Role Required: SDAdmin, SDSiteAdmin Use case: Zylker is planning to update a patch on their assets. Using asset groups, they can pinpoint assets with 500GB ...