<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>In this guide we will cover:</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- </strong><strong>Default Closure Procedures</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- Enabling End-User Closure Confirmation Procedures</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- Closure Settings on Ticket Type</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- Email Templates</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- Configuring the Worked Example</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>- Additional Features per Ticket Type</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><span style="box-sizing: inherit; font-size: 11pt;"><strong>-Closure Confirmation Procedures for Project tickets</strong></span></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><br></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em;"><br></p><p><span style="font-size: 14pt;"><strong>Default Closure Procedures</strong></span></p><p><span style="font-size: 11pt;">Within Halo, the standard practice for closing tickets, is that the end-user will communicate to the agent that the resolution they have received is correct and then the agent will communicate to the user that their ticket has been closed, with the end-user being able to respond to the closure email. </span></p><p><br></p><p><span style="font-size: 11pt;">This will instantly place the ticket into a closed state when the agent uses the "Resolve Ticket" action and it can normally be re-opened by an end-user via an email sent into the ticket. If the following setting "Emails on closed Tickets" is set to "Keep Ticket Closed", this will mean that emails from users into closed tickets will result in the ticket staying closed:</span></p><p><br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJmY2Q4ODY3LWY3OTctNDc4My1iZDc3LTUyOTI5MTc0NWRmYyJ9.Gf31i8SxbjW_qOecRidXk6Tyz2QULWu50x2M193msF4" class="fr-fic fr-fil fr-dib" width="705" height="378"></p><p><strong><span style="font-size: 10pt;">Fig 1. Closure Procedures on the Settings Tab of a Ticket Type</span></strong></p><p><br></p><p>When closure confirmation is enabled the "Pending Closure" settings shown in <strong>Fig 1</strong> will also apply, and when using the action "Resolve Ticket" the status of the ticket will go to "Resolved" instead of "Closed" which is a pending closure status that will only apply to that action if the end-user closure confirmation checkbox has been enabled.</p><p><br></p><p><strong><span style="font-size: 12pt;">Example</span></strong></p><p>The following example will cover where the desired behaviour is for the ticket to re-open when the ticket is in the pending closure state but stay closed after the actual closure of the ticket, which is triggered after a set number of hours have passed with no response from the end-user. </p><p><br></p><p id="isPasted"><strong><span style="font-size: 14pt;">Enabling End-User Closure Confirmation Procedures</span></strong></p><p>To enable end-user closure procedures navigate to Configuration > Tickets > General Settings. For a full list of ticket general settings along with descriptions check out this system settings guide on <a href="https://usehalo.com/haloitsm/guides/1341/" rel="noopener noreferrer" target="_blank"><strong>Tickets General Settings</strong></a>.</p><p><br></p><p>With this enabled, when a Ticket is closed it will go to a Pending Closure Status (Status: Resolved). The End-User will then need to confirm that the Ticket is ok to close. Reminder emails will be sent on a recurring schedule defined by the set number of hours inputted to the "Number of hours between reminder emails" box:</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg4MTE1NjRiLTBiMGYtNGYzMC04ZTU2LWNkMzU2YzVlNTA4MSJ9.K5sS6T42PeSUGHJUtn1LWthEA2nTVam95hOGwujBCS4" class="fr-fic fr-fil fr-dib" width="978" style="width: 980px; height: 518.353px;" height="518"></p><p><strong><span style="font-size: 10pt;">Fig 2. Closure Procedure Settings</span></strong></p><p><br></p><p>You will see from the above screenshot that the frequency of closure reminders, along with the duration of time before the ticket automatically closes, is fully configurable. If you would like to disable the closure reminders/automatic closure functionality, simply set the duration to '0'.</p><p><br></p><p>If there are workdays being used against the SLA's you have configured (Configuration > Service Level Agreements > Service Level Agreements > *Click onto an SLA*):<br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJiZDEzNTlhLWU0OGQtNGQ3Yi1iY2JkLTc1YWI0NjJiM2NhMCJ9._E5McMuh4sCS5LMxaAEdU-U8HrM-xOr6q-VcUyamfQQ" class="fr-fic fr-fil fr-dib" width="569" style="width: 571px; height: 515.787px;" height="516"></p><p><strong><span style="font-size: 10pt;">Fig 3. Work Days Against an SLA (Workdays are created within Configuration>Teams & Agents>Workdays)</span></strong></p><p><br></p><p>Then the frequency in hours will correlate to hours in the workday, i.e. if your agents work from 09:00 - 18:00 then 9 hours in the frequency of reminder emails would equal to an entire workday, and it will account for weekends as well. This means if a closure email is scheduled to go out 9 hours later, those 9 hours are only counted towards during work hours.</p><p><br></p><p>Beneath these settings are options to further configure the end-user closure confirmation emails; this includes the option to use the "$-ConfirmClosureWithFeedback" variable, which will prompt end-users to provide feedback in order to close the ticket. Surveys can also be sent out on the ticket closure email template, and can be configured by clicking on the relevant button found at the bottom of the screenshot above (For more information on Surveys, check out this guide: <a href="https://usehalo.com/haloitsm/guides/1945" target="_blank" rel="noopener noreferrer"><strong>Surveys</strong></a>).</p><p><br></p><p><strong><span style="font-size: 14pt;">Closure Settings on Ticket Type</span></strong></p><p>Closure Settings Can also be configured Per Ticket Type:</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI2MDJhZWNiLWIwOTYtNGVmZi04YzAyLTUwNTY0YTRkY2JkNiJ9.0c_MPQqIyJjMruCtYVsghwUD3tr_NQJ1HySNMILJVXo" class="fr-fic fr-fil fr-dib" width="975" style="width: 977px; height: 780.432px;" height="780"></p><p><strong><span style="font-size: 10pt;">Fig 4. Status after end-users reopen a closed ticket</span></strong></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNlYmQzM2Y1LWUzMjctNGE2Zi1iYWRiLTE2OGM4MDIyMGExYSJ9.tEJVofyCj-5xhvoarHNSytwBbfCFZsuQQqwNjjnWRBw" class="fr-fic fr-fil fr-dib" width="961" height="893"></p><p><strong><span style="font-size: 10pt;">Fig 5. Closure Settings on Ticket Types</span></strong></p><p><br></p><p>If the "Emails on Closed Tickets" is set to "Re-open the ticket" then the status set on the field shown in <strong>Fig 4 </strong>will be the status that the updated ticket goes to. </p><p><br></p><p>The outcome of the End User Closure Confirmation can be used to direct the Workflow. To do this, add the action type "End-User Closure Outcome" on the relevant step of the Workflow. You can then set which step of the workflow you would like to move to depending on the End-User Closure Result. This allows the Workflow to move back a step if the User rejects the confirmation. For more information see the guide on <a href="https://usehalo.com/halopsa/guides/1922/" target="_blank" rel="noopener noreferrer">Workflows</a>.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg5YmJiMTQ1LWE1MTAtNDg1Yi1hZDA2LWJkOTQ2YmE2MjI1NSJ9.kZEvmPlRWmYyJCDr8ahyRyMKUYBaK0uq2_rJDCUWJ-k" class="fr-fic fr-fil fr-dib" width="771" style="width: 773px; height: 493.955px;" height="494"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 6. Closure Settings on a Workflow</span></strong></p><p><br></p><p id="isPasted"><span style="font-size: 14pt;"><strong>Email Templates</strong></span></p><p>The email templates associated to the "Closure Reminder" template for end-user closure confirmation is found in Configuration > Email > Email Templates:</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijg0MGRiMmJjLTQzOGItNGYxYi1iZjkwLTA4NDkzNGM0YWQ3ZCJ9.YEYs1TyGiOZYTytaGjCNm6cG0bWYjER2wbkT2Pzxs3w" class="fr-fic fr-fil fr-dib" width="975" style="width: 977px; height: 233.692px;" height="234"><strong><span style="font-size: 10pt;">Fig 7. Closure Reminder Email Template</span></strong></p><p><br></p><p>The actual default closure reminder template:</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI3ZGVkOTU4LWY3YjEtNGRiMC05YmJhLTBhYzkzYzE3YzhkYiJ9.FU2xkV6hTW_E1UWw0y4923DDdLzD52EuOlfu5VJcB2c" class="fr-fic fr-fil fr-dib" width="979" style="width: 981px; height: 751.045px;" height="751"><strong><span style="font-size: 10pt;">Fig 8. The Default Closure Reminder Template<br></span></strong></p><p><br></p><p>The ticket closure email template can be set in the dropdown as shown in Figure 2, this can be a custom created templated, that will work across all message groups.</p><p><br></p><p><strong><span style="font-size: 14pt;">Configuring the Worked Example</span></strong></p><p>To set the closure confirmation so that the ticket will not re-open when fully closed, but will when in pending state. We must do the following:</p><p><br></p><ol><li>Enable end-user closure confirmation</li><li>Set the email template for ticket closure (This can be the default closure template, or a custom template that you create)</li><li>Add to the number of hours before automatic closure of the ticket i.e. 30 hours where a workday is 08:00 - 18:00 (10 hours) so 3 full workdays until automated ticket closure</li><li>Tick on the checkbox "Send email to End-User when Ticket is automatically closed" which will use the email template set above</li><li>Set the reminder emails to every i.e. 10 hours</li><li>Within the ticket type you are configuring this for, set the "Emails on closed Tickets" to "Keeps the Ticket closed"</li><li>Within the ticket type you are configuring this for, set the "Emails on Tickets pending closure" to "Re-open the Ticket"</li><li>"Status after End-Users reopen a closed Ticket" - This setting will not apply, as the closed ticket is configured to not re-open from end-user updates. The emails back into a closed ticket will still show on the ticket, but the status will still be closed.</li></ol><p><strong><span style="font-size: 14pt;">Additional Features per Ticket Type</span></strong></p><p>Within the Closure settings dropdown of a ticket type, there are many options to choose from on the settings "Emails on closed Tickets" and "Emails on Tickets pending closure".</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQyNjYzMmI5LWI2MGEtNDI2MC04YzU3LTk2YWFiODIwYjc3OSJ9.ds8_nlwzyuZawXV9NlmVHM-NiV8k9c0MM3p4X791zao" class="fr-fic fr-fil fr-dib" width="615" height="265"></p><p><strong><span style="font-size: 10pt;">Fig 9. Dropdown options for Tickets Closed or Tickets Pending Closure</span></strong></p><p><br></p><p>"Emails on closed Tickets" has been split into "User Emails on closed Tickets" and "Agent Emails on closed Tickets" to be able to configure different behaviours for each.</p><p><br></p><ul><li><strong>Re-open the Ticket </strong>- Ticket will reopen with the status set on the ticket type ("Status after End-Users reopen a closed Ticket").</li><li><strong>Keeps the Ticket closed</strong> - Ticket will remain closed.</li><li><strong>Reply with an Email </strong>- Ticket will remain closed and an email template sent.</li><li><strong>Open a new Ticket</strong> - Ticket will remain closed and a new ticket will be opened.</li><li><strong>Reply with an email if a set number of hours have passed</strong> - Ticket will reopen if before the set number of hours, but remain closed and send an email template if after.</li><li><strong>Open a new Ticket if a set number of hours have passed</strong> - Ticket will reopen if before the set number of hours, but remain closed and create a new ticket if after.</li><li><strong>Reply with an email a set number of times and then ignore afterwards</strong> - Ticket will remain closed and an email template will be sent a certain number of times.</li></ul><p><br></p><p>You can configure whether the "Reply with an Email" options send the email to either just the user who replied to the closed ticket, or everyone in the ticket's email list. Within the ticket type > Settings tab, enable "Email replies on closed or pending closure Tickets will only send to the sender" to have this only send to the email that replied to the ticket.</p><p><br></p><p id="isPasted">Emails set to open a new ticket will also automatically link the previously closed one as a related ticket. <strong><em>Note: If using "many-to-many" Ticket relationships, the "Related to" section will not show.</em></strong></p><p><br></p><p>The user email and the closure email it is in reply to will be added as the first action of the ticket, showing it came from the previous ticket ID, and relating the two tickets.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM1NzY2OWM5LTVjZjMtNDFkYS1hNWJiLTY0MDQwMWJlMjViZCJ9.8gEZU7ckIlEH18hjwxB5yiBbMvcxOTYgsq7gtt2y6rM" class="fr-fic fr-fil fr-dib" width="1215" style="width: 1217px; height: 625.663px;" height="626"></p><p><strong><span style="font-size: 10pt;">Fig 10. Opening a new ticket from a closed ticket.</span></strong></p><p><br></p><p>The same settings exist for the "Emails on Tickets pending closure" dropdown. When "Open a new Ticket if a set number of hours have passed" is used, the number of hours can be specified here:<br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjEyNjIzYzgxLTJhMTgtNDU5MS1hYjMxLTAyYzMwYTYzZGFjMiJ9._zI87muIHkyjFLj3SaPkbFv1Y4LQ_h9SZrUf51L9hlg" class="fr-fic fr-fil fr-dib" width="905" height="138"></p><p><strong><span style="font-size: 10pt;">Fig 11. Option for Open a new Ticket if a set number of hours have passed</span></strong></p><p><br></p><p>If the checkbox "Emails on closed Tickets setting applies to Tickets pending closure" is enabled, then the settings configured for emails on closed tickets will also apply to tickets pending closure. Any option shown in<strong> Fig 8</strong> that pertains to sending an email, will give the choice of email template to use:<br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImYzNDZmOTI3LTVhZTctNDFhMi05MjUxLTZkY2RkZWJmOGJjNiJ9.AOhiZTOpymoZH_dSVUlYL2LRXELlpVaAnmj9uG9xydE" class="fr-fic fr-fil fr-dib" width="987" style="width: 989px; height: 69.2379px;" height="69"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 12. "Reply with an Email" Option for Closed Tickets</span></strong></p><p><br></p><p>From v2.238+, "User Emails on closed Tickets with open child Tickets" can be set to determine the behaviour when a user emails on a closed ticket has open child tickets. This includes the option to route the update to any open child tickets while keeping the parent ticket closed. If the parent has no open child tickets, the update is added using the existing "Updates on closed tickets" setting on the parent instead.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImZkMDRhOTQwLWMyZDUtNDYxNS1iYWM3LWIyYWNhYjNjZTI0YiJ9.xx__q9OhzNG0w0POkoz4VNOKpANz7S52GMMXqNCQW4g" class="fr-fic fr-fil fr-dib" width="741" height="284"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig13. "User Emails on closed Tickets with open child Tickets" Option for Closed Tickets </span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Closure Confirmation Procedures for Project tickets</span></strong></p><p><span style="font-size: 11pt;">Closure confirmation for project tickets will function in the same way as closure confirmation for other tickets, using the same setup under Configuration > Tickets > General Settings. But this must be enabled separately for project tickets. </span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 12pt;"><strong>Enabling Closure Confirmation for project tickets</strong></span></p><p><span style="font-size: 11pt;">To enable this functionality, head to Configuration > Project Management > General Settings and enable 'Enable End-User Closure Confirmation for Projects'. </span></p><p><br></p><p><span style="font-size: 11pt;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJiOWRlMjA5LWQzMzctNDcyZC04Nzk0LWVmN2VhMGQ5NTYxNCJ9.ppMr8xFwSmOXAl0uMoYJyeP6ZdFEvr8s8CCjfVjhcFo" class="fr-fic fr-fil fr-dib" width="833" height="354"></span></p><p><span style="font-size: 10pt;"><strong>Fig 14. Enable End-User Closure Confirmation for Projects</strong></span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 11pt;">Once enabled you will need to enable closure confirmation for each of your project ticket types. To do this head to Configuration > Tickets > Ticket Types > select a ticket type used for projects > Settings tab and enable 'Enable pending closure procedures'. </span></p><p><br></p><p><span style="font-size: 11pt;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjUzODc3ODg2LTU2OTUtNDgzNC1iMTZhLTA0MTk5NDZiZjJiMiJ9.EgdtIl5Dc-97Ulfx40YUTWHh9mGHynCqwTaz1zSTHAA" class="fr-fic fr-fil fr-dib" width="848" style="width: 850px; height: 642.311px;" height="642"></span></p><p><span style="font-size: 10pt;"><strong>Fig 15. Enable pending closure against ticket type</strong></span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 11pt;"><em><strong>Note: If the global setting in figure 11 is not enabled you will not be able to enable pending closure procedures against project ticket types. </strong></em></span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 11pt;">Once this is enabled closure confirmation procedures will take place for this project ticket type in line with the closure confirmation settings you have configured in tickets > general settings. For example the same interval between reminder emails and the same email template for reminder emails will be used. </span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 11pt;">However, some of the closure confirmation settings can be overridden against the project ticket type.</span></p><p><br></p><p data-pasted="true"><span style="font-size: 11pt;">You should note that, if you have the setting on in Configuration > Tickets > General Settings to "not close Ticket with SLA procedures when open Appointments, Tasks and To-do items exist", the Ticket will fail to close automatically.</span></p><p><span style="font-size: 11pt;"><br></span></p><p><span style="font-size: 11pt;">If the Ticket fails to close due to the above mentioned setting, an action will add to the Ticket stating the reason for automatic closure failure:</span></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQzYTkxMzE4LWM1YTktNDAxYi04NTRjLWUxYTRmNGU1OGYyZCJ9.KoLPpHalMG3UyD2t0_DHJ8-TVUkHLCQ3bplg69e3Xc0" class="fr-fic fr-fil fr-dib" width="882" style="width: 884px; height: 146.584px;" height="147"></p><p><strong><span style="font-size: 10pt;">Fig 16. The action that will add to the Ticket if automatic closure fails due to outstanding Appointments, Tasks or To-do items</span></strong></p><p><br></p>
