Managing service request types
SECURITY Security level with Admin permission to configure Client Portal & Taskfire. Refer to Admin security settings.
NAVIGATION > Admin > Admin Categories > Extensions & Integrations > Client Portal & Taskfire > Service Request Types
About Client Portal request types
A service request type is the Client portal equivalent of a ticket category: a template your clients will use when submitting tickets from the Client Portal. It controls how the ticket appears in the Client Portal, specifically:
- The fields displayed on the ticket
- Which fields are required
- The default values for fields on the Client Portal New Ticket page
- The picklist values available on the Client Portal New Ticket page
- The background questions that appear on tickets with this request type
- How the ticket priority is set (directly or by answering pre-configured questions)
- The ticket category applied to tickets with this request type in your Autotask instance
For information on configuring a request type, refer to Adding or editing Client Portal request types.
Managing request types
To open the page, use the path(s) in the Security and navigation section above. Autotask comes with the following service request types:
- One default active service request type called General Request your clients can start to use immediately. Tickets of this type are created with a status of New and will go to your Client Portal queue. You cannot edit these settings, but you can add or edit background questions.
- A request type for tickets that are created by you, the service provider, but displayed in the Client Portal, called Created by Service Provider. This request type is set to inactive and has no default values or custom available list values chosen for any fields. However, we do not prevent you from activating the request type, configuring field default values, or configuring field available list values. If you choose default values, they will only be applied if the request type is used when your customer contacts create a ticket in the Client Portal, not when you create a ticket in your Autotask instance.
- Sample inactive service request types. These are provided as examples but will not appear on the request type drop-down list for clients creating tickets until you activate them. These samples can be deleted if you choose not to use them.
To add a request type, click New Request Type. Refer to Adding or editing Client Portal request types.
How Autotask ticket categories and Client Portal request types interact
Ticket categories (Autotask) and request types (Client Portal) do much the same thing: they control if a field is visible or required, as well as default values and available list values.
In the Client Portal, the field properties of the request type override the field properties of the ticket category that is assigned to display such tickets in your Autotask instance.
Field Type | Visible on the request type layout | Default configured on the request type layout? | Uses the defaults on the ticket category layout |
---|---|---|---|
Editable | yes | yes | never |
no | yes | never | |
no | no | yes | |
Read-only | yes or no | yes | never |
yes or no | no | yes | |
UDF | globally visible | yes | never |
globally visible | no | yes | |
globally not visible | N/A | yes |
EXAMPLE If the Client Portal request type Due Date defaults to two days from the Create Date and the ticket category's defaults to five days, the Due Date will be two days from the Create Date. The ticket category's Due Date default is applied only if the request type has no Due Date default setting AND the Due Date field is hidden.