By default, the Service Desk is configured to use an internal SMTP server for sending ticket-related emails. You have an option to use an external SMTP server, however, you must configure it in the appliance network settings. For more information, see Change appliance network settings.
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
2. |
On the Service Desk Email Preferences page that appears, in the Outbound Email tab, select the Include "Reply above this line" text on outbound email communications check box. |
a. |
In the Inbound Email tab, in the Ignore emails with following text in the subject field, type the words that you want to detect. You can specify multiple entries, using a semi-colon as a separator. For example: Out of Office;Mail Delivery Failure. |
To disable this restriction, you can set to a high number such as 99999. |
6. |
Next, you can configure POP3 email accounts for specific Service Desk queues. For more information, see Configure queue-specific email settings.
The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.
The following email events trigger the appliance to send email immediately:
• |
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. |
• |
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page. |
3. |
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event. |
The person who can approve or reject the ticket for processing. | |
One or more email addresses that are stored in the CC field of the ticket. | |
One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories. | |
One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events. |
When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.
The ticket's Owner field is changed. | |
The ticket's Status field is changed. | |
Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. | |
The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey. | |
A user sends an email message to the Service Desk and a ticket is created. | |
A ticket is created through the User Console. |
4. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page. |
3. |
◦ |
To edit all email templates, click Customize All Emails. |
◦ |
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click . |
The following email template are available:
Used to notify senders that the ticket could not be created for reasons other than unknown email address. |
||
The email address associated with the Service Desk queue. This address is configured on the Queue Detail page. | |
The name of the Service Desk queue. This name is configured on the Queue Detail page. | |
A link to the User Console. Access to the User Console requires login credentials. |
The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types. | |||
The email address of the ticket approver. Having this address is especially useful for Comments email notifications. | |||
The name of the ticket approver. | |||
The label and value used for a custom field, where X represents the index number of the custom field. For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque. | |||
The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications. | |||
Include all the ticket fields that are visible for the user who is forwarding the ticket by email.
| |||
The complete history of the ticket.
| |||
A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent. | |||
A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets. | |||
The email address of the Service Desk administrator assigned to the ticket. | |||
The name of the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
The priority assigned to the ticket. Default values include High, Medium, and Low. | |||
Information about what was done to resolve the ticket as described in the ticket’s Resolution field. | |||
| |||
The title of the ticket as it appears on the Ticket Detail page. | |||
A link to the ticket in the User Console. Access to the User Console requires login credentials. | |||
A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials. | |||
A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly. | |||
A link to the home page of the User Console. Access to the User Console requires login credentials. |
The title of the merged ticket as it appears on the Ticket Detail page. | |
A link to the merged ticket in the User Console. Access to the User Console requires login credentials. |
Used to identify a problem processing the submitted tokens. This error appears when: | |
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today. |
5. |
Optional: For each email template, create HTML-based content instead of using plain text. |
a. |
▪ |
To add images, click , and provide the URL to the image file, a local file path, or simply drop the image into the indicated area. |
▪ |
Deleting an image from the text field does not remove the associated file attachment. You can manage file attachments in the Attachments section of the ticket page. For more information, see Add or delete screen shots and attachments from Service Desk tickets. |
◦ |
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send: |
▪ |
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update. |
▪ |
Last uploaded: Include the last uploaded file attachments. |
▪ |
All: Include all file attachments. |
◦ |
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box. |
7. |
For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.
The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.
The following email events trigger the appliance to send email immediately:
• |
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. |
• |
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page. |
3. |
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event. |
The person who can approve or reject the ticket for processing. | |
One or more email addresses that are stored in the CC field of the ticket. | |
One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories. | |
One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events. |
When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.
The ticket's Owner field is changed. | |
The ticket's Status field is changed. | |
Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. | |
The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey. | |
A user sends an email message to the Service Desk and a ticket is created. | |
A ticket is created through the User Console. |
4. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page. |
3. |
◦ |
To edit all email templates, click Customize All Emails. |
◦ |
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click . |
The following email template are available:
Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. |
||||
Used to acknowledge that a ticket has been created through email. |
||||
Used to acknowledge that a ticket has been created through the User Portal. |
||||
Used to notify recipients when ticket information is changed or added. |
||||
Used to notify recipients that comments are added to tickets. |
Owners, submitters, approvers, the ticket CC list, and the ticket Category CC list | |||
Used to present a Satisfaction Survey to submitters when tickets are closed. See Using the Satisfaction Survey. |
||||
Used to for messages that are forwarded using the Email Ticket action on Ticket Detail pages.
|
||||
None. Configurable on the Queue Detail page |
Used to notify senders that the ticket could not be created for reasons other than unknown email address. |
||
The email address associated with the Service Desk queue. This address is configured on the Queue Detail page. | |
The name of the Service Desk queue. This name is configured on the Queue Detail page. | |
A link to the User Console. Access to the User Console requires login credentials. |
The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types. | |||
The email address of the ticket approver. Having this address is especially useful for Comments email notifications. | |||
The name of the ticket approver. | |||
The label and value used for a custom field, where X represents the index number of the custom field. For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque. | |||
The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications. | |||
Include all the ticket fields that are visible for the user who is forwarding the ticket by email.
| |||
The complete history of the ticket.
| |||
A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent. | |||
A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets. | |||
The email address of the Service Desk administrator assigned to the ticket. | |||
The name of the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
The priority assigned to the ticket. Default values include High, Medium, and Low. | |||
Information about what was done to resolve the ticket as described in the ticket’s Resolution field. | |||
| |||
The title of the ticket as it appears on the Ticket Detail page. | |||
A link to the ticket in the User Console. Access to the User Console requires login credentials. | |||
A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials. | |||
A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly. | |||
A link to the home page of the User Console. Access to the User Console requires login credentials. |
The title of the merged ticket as it appears on the Ticket Detail page. | |
A link to the merged ticket in the User Console. Access to the User Console requires login credentials. |
Used to identify a problem processing the submitted tokens. This error appears when: | |
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today. |
5. |
Optional: For each email template, create HTML-based content instead of using plain text. |
a. |
▪ |
To add images, click , and provide the URL to the image file, a local file path, or simply drop the image into the indicated area. |
▪ |
Deleting an image from the text field does not remove the associated file attachment. You can manage file attachments in the Attachments section of the ticket page. For more information, see Add or delete screen shots and attachments from Service Desk tickets. |
◦ |
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send: |
▪ |
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update. |
▪ |
Last uploaded: Include the last uploaded file attachments. |
▪ |
All: Include all file attachments. |
◦ |
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box. |
7. |
For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.
The Email on Events section determines which actions trigger an email to the various appliance users. Email templates determine the content of the messages.
The following email events trigger the appliance to send email immediately:
• |
Comment: The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. |
• |
Ticket Closed: If the Satisfaction Survey is enabled, an email that describes the Satisfaction Survey is sent immediately when tickets are closed. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click [edit] link to display the Service Desk Queue Email Settings page. |
3. |
On the Service Desk Queue Email Settings page, in the Email on Events tab, select the options for sending email when the specified events occur. Each column represents a type of Service Desk user (role) and each row represents a ticket event. |
The person who can approve or reject the ticket for processing. | |
One or more email addresses that are stored in the CC field of the ticket. | |
One or more email addresses that are stored in the CC List of the Category Value of the ticket. See Configure CC lists for ticket categories. | |
One or more owners of the ticket queue, as specified by the Owner label. This only applies to the New Ticket Via Email and New Ticket via Portal events. |
When a ticket event occurs, email is sent to the selected roles or users. For example, if you select the Any Change box in the Owner column, email is sent to the ticket owner whenever the ticket is changed. For the Comment and Ticket Closed triggers, email is sent immediately. For other ticket changes, however, email is sent every few minutes to prevent email overload.
The ticket's Owner field is changed. | |
The ticket's Status field is changed. | |
Information, attachments, or screen shots are added to the ticket's Comments section. The system sends email notifications for comments when users add comments and click Submit on the ticket form. When users add comments and click Save on the ticket form, however, only the Any Change notification is sent. | |
The ticket's Status field is changed to Closed. This event is used to present a Satisfaction Survey to submitters. See Using the Satisfaction Survey. | |
A user sends an email message to the Service Desk and a ticket is created. | |
A ticket is created through the User Console. |
4. |
1. |
a. |
Log in to the appliance Administrator Console, https://appliance_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
c. |
d. |
▪ |
2. |
On the Queue Detail page, under Email Address, click Configure Queue Email Settings link to display the Service Desk Queue Email Settings page. |
3. |
◦ |
To edit all email templates, click Customize All Emails. |
◦ |
To edit a specific email template, in the Events area, in the row containing the email template you want to edit, in the Customize Email column, click . |
The following email template are available:
Used to send periodic notifications according to the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. |
||||
Used to acknowledge that a ticket has been created through email. |
||||
Used to acknowledge that a ticket has been created through the User Portal. |
||||
Used to notify recipients when ticket information is changed or added. |
||||
Used to notify recipients that comments are added to tickets. |
Owners, submitters, approvers, the ticket CC list, and the ticket Category CC list | |||
Used to present a Satisfaction Survey to submitters when tickets are closed. See Using the Satisfaction Survey. |
||||
Used to for messages that are forwarded using the Email Ticket action on Ticket Detail pages.
|
||||
None. Configurable on the Queue Detail page |
Used to notify senders that the ticket could not be created for reasons other than unknown email address. |
||
The email address associated with the Service Desk queue. This address is configured on the Queue Detail page. | |
The name of the Service Desk queue. This name is configured on the Queue Detail page. | |
A link to the User Console. Access to the User Console requires login credentials. |
The type of the process. In a default installation, only the Service Desk process type is included. You can create new process types, as required. For example, you can create a process type for accessing a specific application, or a group of applications. For more information, see Define process types. | |||
The email address of the ticket approver. Having this address is especially useful for Comments email notifications. | |||
The name of the ticket approver. | |||
The label and value used for a custom field, where X represents the index number of the custom field. For example, if a queue has a ticket field labeled, CUSTOM_5, and that field is configured with the label Location Name, the system replaces $ticket_custom_5_label with the text, Location Name. The token, $ticket_custom_5_value is replaced with the ticket value that was saved for the Location Name field, such as, Topeka or Albuquerque. | |||
The time, in minutes, between periodic notifications. This time is determined by the Escalation Time configured for the ticket priority in the queue. For example, if tickets with the priority of High have an Escalation Time of 30 minutes, this email is sent every 30 minutes for High priority tickets until the ticket priority changes or until the ticket is closed. This token is typically used in the Ticket Escalated email template, to inform recipients of the frequency of email notifications. | |||
Include all the ticket fields that are visible for the user who is forwarding the ticket by email.
| |||
The complete history of the ticket.
| |||
A specified number of records in the ticket history. X indicates the number of records to include, beginning with the most recent. | |||
A formatted version of the ticket ID. This version begins with TICK followed by a minimum of five digits. For example, a ticket with ID 4321 is displayed as TICK:04321. This format is especially useful in email Subject lines to make sure that email replies link to the correct tickets. | |||
The email address of the Service Desk administrator assigned to the ticket. | |||
The name of the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
Contact information for the Service Desk administrator assigned to the ticket. | |||
The priority assigned to the ticket. Default values include High, Medium, and Low. | |||
Information about what was done to resolve the ticket as described in the ticket’s Resolution field. | |||
| |||
The title of the ticket as it appears on the Ticket Detail page. | |||
A link to the ticket in the User Console. Access to the User Console requires login credentials. | |||
A link to the ticket in the User Console. This format is used for backward compatibility on older systems. Access to the User Console requires login credentials. | |||
A secure link to the ticket in the User Console. Use this token if SSL is enabled on your appliance. This ensures that links sent through email work correctly. | |||
A link to the home page of the User Console. Access to the User Console requires login credentials. |
The title of the merged ticket as it appears on the Ticket Detail page. | |
A link to the merged ticket in the User Console. Access to the User Console requires login credentials. |
Used to identify a problem processing the submitted tokens. This error appears when: | |
NOTE: Tokens that are invalid are ignored and they are not replaced in email messages. For example, if you add an unknown token such as $today, it is ignored, and it appears in the email message as $today. |
5. |
Optional: For each email template, create HTML-based content instead of using plain text. |
a. |
▪ |
To add images, click , and provide the URL to the image file, a local file path, or simply drop the image into the indicated area. |
▪ |
Deleting an image from the text field does not remove the associated file attachment. You can manage file attachments in the Attachments section of the ticket page. For more information, see Add or delete screen shots and attachments from Service Desk tickets. |
◦ |
To allow Service Desk to send file attachments, select Include attachments. Then, indicate which attachments you want to send: |
▪ |
Most recent change (if applicable): Include only the file attachments that are added with the most recent ticket update. |
▪ |
Last uploaded: Include the last uploaded file attachments. |
▪ |
All: Include all file attachments. |
◦ |
To prevent Service Desk from sending file attachments with ticket-related email, clear the Include attachments check box. |
7. |
For instructions on how to configure the appliance to use SMTP email, see Configuring SMTP email servers.
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center