On this page
Options configured through Service Desk Settings are global and affect your entire instance of SolarWinds Service Desk. Global settings establish the foundation of how your Service Desk will look, feel, and behave. Only administrators can make changes in Setup.
Setup > Global Settings > Service Desk Settings.
Service Desk Name
Enter a service desk name for your company. This name appears in the FROM field in email notifications and in the service portal.
Image - Sign In
This image will only show on the native SWSD sign-in page. If you redirect to a Single Sign On (SSO) login page, no image will display. The recommended size for the image is 1400 px width X 1050 px height. Larger images will be cropped.
Default Landing Page
This is where administrators can establish the default landing page for all licensed administrators and service agent users. This can be set per user on the User edit page or by the users themselves when Allow agent to change their default landing page is enabled.
Custom Resolution Codes
Custom Resolution Codes are used to define the way your team reached a resolution on an incident. You can customize these codes to match your business logic, add new custom codes, delete existing ones, and even make this field mandatory for your technicians.
Examples for helpful resolution codes include:
Change Types Values
Define the types of changes used in your organization. The values, and their order, will be seen in the Change Management module, as part of the Type field dropdown list. The first value in the list will be the default type.
- Auto Tagging - Used in SWSD to add additional search terms to your Incidents. You can check this box if you want SWSD to automatically generate tags.
Inherit Tags From Service Catalog - Toggle On to automatically pass Service Catalog tags to Service requests.
Inherit Tags From Change Catalog - Toggle On to automatically pass Change Catalog tags to Change requests.
Required Mandatory Fields On Resolution
Required fields must be updated prior to resolving an incident. There is important:
To ensure accurate reporting. If all mandatory fields are not completed, reports you run that measure and monitor your service desk metrics can be affected because of incomplete data.
To drive a consistent resolution, ensuring you are collecting the mandatory data points associated with an incident.
Mandatory Change Fields
You can configure distinct fields to be mandatory for incidents, for example: Category/Subcategory, Custom Fields, and Resolution Codes. When activated, this feature creates a popup window on the Incident Page that shows you all editable fields, marking the mandatory ones with a red asterisk.
To ensure you are getting all the necessary data points you desire when an incident is resolved, and that processes you have in place automating incident resolutions are not broken, SWSD allows for certain exceptions to the rules. The Mandatory fields are not required:
When Incidents are auto-resolved due to requester inactivity.
When Incidents are resolved via an automation rule.
When Incidents are resolved via an integration or API call.
Toggle to On to allow service requests to complete even if incomplete tasks exist.
Toggle to On to allow changes to complete even if incomplete tasks exist.
Inline Edit on records
Toggle to On so that inline edit will display a pop-up window to process dynamic form rules and dependencies.
Toggle to On for SWSD to completely override ticket cc lists with the cc list in the most recent email response and make all comments made via email become private comments.
When the toggle is set to on, all comments are flagged as private. After comments are made private, from within an incident ticket requesters can change the visibility of comments from private to public if comments should be visible to both end users and agents. See Change incident comments from private to public for instructions.
When the feature is toggled to Off, comments made via email remain public and anyone added to the cc list via email or via the application remain on the ticket's cc list until they are removed via the application.
Inline Edit On Service Catalog Items
Toggle to On to enable the use of inline editing on service catalog items. Turn off the feature so all service catalog items can be saved before they are rolled out to all employees. When the toggle is in the Off position, you can click Edit to make any changes.
Any update to the values or default text in a custom field will be reflected in all places where that custom field is used.
This feature lets you predefine a duration after which inactive incidents will be changed from a Resolved state to a Closed state. An incident is considered inactive when no new comments or changes have been made to the incident over a specified period of time. SolarWinds typically recommends anything from 5 to 14 days, depending on your organization's needs.
Close Inactive Resolved Incidents
Select a duration after which inactive incidents will be moved from Resolved state to Closed. Note that an incident is considered inactive when it has no new comments and no changes are made to the incident's fields.
Resolve Inactive Incidents
This feature allows you to select a state and duration of inactivity on an incident that then changes the incident's state to Resolved.
Reopen Resolved/Closed Incidents
This feature allows you to reopen any closed or resolved incidents when a new Incident index table is entered. If you opt to disable this feature, technicians can still be made aware of new comments made on resolved incidents based on your Notification settings or Automation rules settings.
Default Priority For New Incidents
This feature allows you to set the default priority for new incidents. You can adjust the default priority to Low, Medium, High, or Critical.
Live view of new incidents
By enabling the live view provides a real-time indication of new incidents.
Toggle to On to enable the direct communication between requesters and agents via the portal and an inbound chat queue for agents.
See Chat for administrators for more information and instructions on settings up roles and permissions for Chat.
Default Comments Visibility
Set the visibility of comments added to SWSD incidents by Administrators and Service Agent users, establishing the default setting for any new comments added in the incident view. Public comments will be visible to both Service Agent Users and requesters, while Private comments are only visible to Service Agents. When Incident index tableing, the Administrator and Service Agent users can toggle the visibility of the Incident index table.
Toggle to On to display the newest comments first in the incident view. To reverse the order, switch the toggle to Off.
Customer Satisfaction Surveys
Customer Satisfaction surveys (CSat surveys) are a great way to find out what your end users think of the level of service you are providing.
Default survey delivery settings
You can choose default survey delivery settings. For example:
- If you do not wish to send surveys, you can disable them.
- You can send surveys for all incident categories.
- You can choose a selection of categories to send surveys for.
Default Notification Timing
If you enable surveys, you can also establish default notification timing. This includes:
When surveys will be sent.
The frequency at which surveys are sent.
You can also set whether surveys should be sent for first touch resolution or you would prefer to use an external survey.
Default Widget Threshold Limit
CSat responses can be reported on and viewed from a widget within your SWSD Dashboard. You can set the threshold for the customer satisfaction widget. When the percentage of satisfied customers drops below the value you set, the widget appears with red colors.
Enabling this option will always set the associated request/incident record's status to Resolved after the final workflow process has been completed or is manually stopped via the Stop Process option. When this option is disabled, the record's state will not be modified at process completion.
Enable sentiment analysis to quickly identify incidents with negative sentiment. Take action by prioritising incidents which need attention. Sentiment data is gathered from the time this feature is enabled.
Just-in-Time workflow processing
When this option is disabled, the entire process (including conditions and task assignments) will be evaluated for each workflow, before the workflow process starts. Enabling this option will result in evaluating each workflow step when it is reached at workflow execution time. As a result, the outcome of each such evaluation will depend on variable and field values at execution time vs. their values at workflow start time.