Interpreting the Information in the SLA-M Dashboard

Sub Banner

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

The SLA-M Dashboard provides a number of alternative dynamically configurable views of all your open tickets, interpreting the information pertaining to the progress and status of the SLA metric for each event modeled in your SLA process as follows.

*Note: please see Introduction to the SLA-M Dashboard for more detailed on the purpose and types of operational mode.

Working in Destination Board (Events) Mode

Working in Destination Board (Events) Mode

When using the SLA-M Dashboard in Events mode the Destination Board will only ever include information about ticket events that either:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

i.e., once the criteria to determine completion the event or associated task has been met (e.g. an initial response has been given) the event will no longer appear in this destination board.

*Note: See Identify when a timer has paused or stopped for circumstances under which an event will also not be included in the SLA-M Dashboard.

The following information available when using this operating mode:

(1) The ticket Subject

The subject of the ticket associated with the event.

Hover over the subject to pop-up additional information about the associated ticket such as the Status, ID, system priority, description and latest comment.

Select the subject link to drill down into the ticket form for the associated ticket from where full SLA details can be viewed using the SLA Assistant.

(2) The Organization and Requester of the associated ticket

If your SLA-M Dashboard has been configured to include this information (see Configuring and Customizing the SLA-M Dashboard) then the name of the ticket organization and requester are displayed against each event.

Select the organization or requester links to drill down into the respective forms to see full details.

(3) The name or label given to the event for the SLA Plan specification

The label can be different for each type of event depending upon the configurations for the associated SLA Plan.

Select the subject link to drill down into the ticket form for the associated ticket from where a description of the SLA Plan and event can be viewed using the SLA Assistant.

(4) The criteria for completing the event has NOT yet been met, but the timer is still running

If the event or task has NOT been completed but the due date time (7) has yet to be reached, then the SLA-M Dashboard will indicate that the timer is still running through the presence of a green box and the number of days/hours/mins remaining to complete the task.

*Note: the figure displayed in the green box is the number of actual or calendar days/hours/mins elapsed before a violation will occur, not the number of business hours used to calculate the due date/time, which might be significantly less.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(5) The warning timer has fired for this event since the due date/time for completion is imminent

If your CloudSET SLA Management setup has been configured to make use of warning timers, then the SLA-M Dashboard will indicate when a warning timer has fired through the presence of an amber box.

Also depending upon your setup, a warning notification will have been emailed to the assigned agent and/or other groups and individuals.

Your Zendesk administrator will have configured the number of minutes before the due date/time that the warning timer should fire in the SLA Plan specifications.

(6) The SLA has been violated and the criteria for completing the event has NOT yet been met

If the due date/time (7) is now in the past and the event or task has still yet to be completed, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red box and the number of days/hours/mins overdue.

*Note: the figure displayed in the red box is the number of actual or calendar days/hours/mins elapsed since the violation occurred, not the number of business hours used to calculate the due date/time.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(7) The time for the event has been paused

If your setup has been configured to pause any event timers on Pending or On-hold then these are displayed with a black background and the number of business hours remaining on the timer.

*Note: your SLA-M Dashboard must configured to include tickets in a status of Pending and On-Hold

(8) The due date/time by when the event criteria must have been met in order to pass the agreed SLA

Hover over the countdown value to display the due date/time by when the event or task should be or should have been completed.

Regardless of the time-zone associated with the ticket (see Regions), the due date/time will always be displayed using the time-zone configured in the Zendesk profile for the current user.

(9) The amount of time remaining before the SLA-M Dashboard will be automatically refreshed

This counter indicates the amount of time remaining before the contents of the SLA-M Dashboard will be refreshed with the latest information.

*Note: see Refreshing Information in the SLA-M Dashboard for full details.

Working in Destination Board (Tickets) Mode

Working in Destination Board (Tickets) Mode

As described in Introduction to the SLA-M Dashboard the SLA-M Dashboard provides an alternative operating mode that is more akin to a standard Zendesk view, with added benefits.

The Tickets destination board provides a tabular list of all tickets that have at least one of the following:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

However, unlike when working in the Events mode, so long as at least one event has yet to be completed, this destination board will also provide information about events that have met the criteria to determine completion the associated task.

In addition to the information available when working in Events mode (see above), when using the SLA-M Dashboard in Tickets mode the Destination Board will also provide the following:

(1) Sorting Tickets

Just like a standard Zendesk view it is possible to sort the list of tickets in the table by selecting any of the column headings.

(2) The Next Event due for the associated ticket

Regardless of the number of running events the ticket will only appear once in the list and this column will always display the event or task that has the earliest due date/time and so is due for completion next to avoid an SLA breach.

Hover over the countdown value to see the name of the event and the due date/time by when the associated task must be completed.

(3) Information about system ticket fields

If your SLA-M Dashboard has been configured to include one or more system ticket fields (see Configuring and Customizing the SLA-M Dashboard) then these values are displayed as columns.

(4) Custom Status and Custom Priority

If your SLA solution is making use of a Custom Status and/or Custom Priority and your SLA-M Dashboard has been configured to make use of these fields, then the values will be displayed as columns in this destination board.

(5) Information about SLA Events

It is possible to show or hide columns to display information about each of the SLA events in use by your CloudSET SLA Management setup and configuration.

This can include events that have met the criteria to determine completion the associated task.

Having done so it is then possible to sort the tickets using the column heading to bring the events of most interest or importance to the current user to the top of the queue.

(6) The criteria for completing the event has been met within the agreed SLA

If the event or task is completed before the due date time, then the timer will be stopped and the SLA-M Dashboard will indicate an SLA pass through the presence of a green tick.

(7) The criteria for completing the event has been met, but NOT within the agreed SLA (violated)

If the event or task has been completed but only after the due date time, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red tick.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Interpreting the Information in the SLA-M Dashboard

Sub Banner

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

The SLA-M Dashboard provides a number of alternative dynamically configurable views of all your open tickets, interpreting the information pertaining to the progress and status of the SLA metric for each event modeled in your SLA process as follows.

*Note: please see Introduction to the SLA-M Dashboard for more detailed on the purpose and types of operational mode.

Working in Destination Board (Events) Mode

Working in Destination Board (Events) Mode

When using the SLA-M Dashboard in Events mode the Destination Board will only ever include information about ticket events that either:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

i.e., once the criteria to determine completion the event or associated task has been met (e.g. an initial response has been given) the event will no longer appear in this destination board.

*Note: See Identify when a timer has paused or stopped for circumstances under which an event will also not be included in the SLA-M Dashboard.

The following information available when using this operating mode:

(1) The ticket Subject

The subject of the ticket associated with the event.

Hover over the subject to pop-up additional information about the associated ticket such as the Status, ID, system priority, description and latest comment.

Select the subject link to drill down into the ticket form for the associated ticket from where full SLA details can be viewed using the SLA Assistant.

(2) The Organization and Requester of the associated ticket

If your SLA-M Dashboard has been configured to include this information (see Configuring and Customizing the SLA-M Dashboard) then the name of the ticket organization and requester are displayed against each event.

Select the organization or requester links to drill down into the respective forms to see full details.

(3) The name or label given to the event for the SLA Plan specification

The label can be different for each type of event depending upon the configurations for the associated SLA Plan.

Select the subject link to drill down into the ticket form for the associated ticket from where a description of the SLA Plan and event can be viewed using the SLA Assistant.

(4) The criteria for completing the event has NOT yet been met, but the timer is still running

If the event or task has NOT been completed but the due date time (7) has yet to be reached, then the SLA-M Dashboard will indicate that the timer is still running through the presence of a green box and the number of days/hours/mins remaining to complete the task.

*Note: the figure displayed in the green box is the number of actual or calendar days/hours/mins elapsed before a violation will occur, not the number of business hours used to calculate the due date/time, which might be significantly less.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(5) The warning timer has fired for this event since the due date/time for completion is imminent

If your CloudSET SLA Management setup has been configured to make use of warning timers, then the SLA-M Dashboard will indicate when a warning timer has fired through the presence of an amber box.

Also depending upon your setup, a warning notification will have been emailed to the assigned agent and/or other groups and individuals.

Your Zendesk administrator will have configured the number of minutes before the due date/time that the warning timer should fire in the SLA Plan specifications.

(6) The SLA has been violated and the criteria for completing the event has NOT yet been met

If the due date/time (7) is now in the past and the event or task has still yet to be completed, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red box and the number of days/hours/mins overdue.

*Note: the figure displayed in the red box is the number of actual or calendar days/hours/mins elapsed since the violation occurred, not the number of business hours used to calculate the due date/time.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(7) The time for the event has been paused

If your setup has been configured to pause any event timers on Pending or On-hold then these are displayed with a black background and the number of business hours remaining on the timer.

*Note: your SLA-M Dashboard must configured to include tickets in a status of Pending and On-Hold

(8) The due date/time by when the event criteria must have been met in order to pass the agreed SLA

Hover over the countdown value to display the due date/time by when the event or task should be or should have been completed.

Regardless of the time-zone associated with the ticket (see Regions), the due date/time will always be displayed using the time-zone configured in the Zendesk profile for the current user.

(9) The amount of time remaining before the SLA-M Dashboard will be automatically refreshed

This counter indicates the amount of time remaining before the contents of the SLA-M Dashboard will be refreshed with the latest information.

*Note: see Refreshing Information in the SLA-M Dashboard for full details.

Working in Destination Board (Tickets) Mode

Working in Destination Board (Tickets) Mode

As described in Introduction to the SLA-M Dashboard the SLA-M Dashboard provides an alternative operating mode that is more akin to a standard Zendesk view, with added benefits.

The Tickets destination board provides a tabular list of all tickets that have at least one of the following:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

However, unlike when working in the Events mode, so long as at least one event has yet to be completed, this destination board will also provide information about events that have met the criteria to determine completion the associated task.

In addition to the information available when working in Events mode (see above), when using the SLA-M Dashboard in Tickets mode the Destination Board will also provide the following:

(1) Sorting Tickets

Just like a standard Zendesk view it is possible to sort the list of tickets in the table by selecting any of the column headings.

(2) The Next Event due for the associated ticket

Regardless of the number of running events the ticket will only appear once in the list and this column will always display the event or task that has the earliest due date/time and so is due for completion next to avoid an SLA breach.

Hover over the countdown value to see the name of the event and the due date/time by when the associated task must be completed.

(3) Information about system ticket fields

If your SLA-M Dashboard has been configured to include one or more system ticket fields (see Configuring and Customizing the SLA-M Dashboard) then these values are displayed as columns.

(4) Custom Status and Custom Priority

If your SLA solution is making use of a Custom Status and/or Custom Priority and your SLA-M Dashboard has been configured to make use of these fields, then the values will be displayed as columns in this destination board.

(5) Information about SLA Events

It is possible to show or hide columns to display information about each of the SLA events in use by your CloudSET SLA Management setup and configuration.

This can include events that have met the criteria to determine completion the associated task.

Having done so it is then possible to sort the tickets using the column heading to bring the events of most interest or importance to the current user to the top of the queue.

(6) The criteria for completing the event has been met within the agreed SLA

If the event or task is completed before the due date time, then the timer will be stopped and the SLA-M Dashboard will indicate an SLA pass through the presence of a green tick.

(7) The criteria for completing the event has been met, but NOT within the agreed SLA (violated)

If the event or task has been completed but only after the due date time, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red tick.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Interpreting the Information in the SLA-M Dashboard

Sub Banner

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

The SLA-M Dashboard provides a number of alternative dynamically configurable views of all your open tickets, interpreting the information pertaining to the progress and status of the SLA metric for each event modeled in your SLA process as follows.

*Note: please see Introduction to the SLA-M Dashboard for more detailed on the purpose and types of operational mode.

Working in Destination Board (Events) Mode

Working in Destination Board (Events) Mode

When using the SLA-M Dashboard in Events mode the Destination Board will only ever include information about ticket events that either:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

i.e., once the criteria to determine completion the event or associated task has been met (e.g. an initial response has been given) the event will no longer appear in this destination board.

*Note: See Identify when a timer has paused or stopped for circumstances under which an event will also not be included in the SLA-M Dashboard.

The following information available when using this operating mode:

(1) The ticket Subject

The subject of the ticket associated with the event.

Hover over the subject to pop-up additional information about the associated ticket such as the Status, ID, system priority, description and latest comment.

Select the subject link to drill down into the ticket form for the associated ticket from where full SLA details can be viewed using the SLA Assistant.

(2) The Organization and Requester of the associated ticket

If your SLA-M Dashboard has been configured to include this information (see Configuring and Customizing the SLA-M Dashboard) then the name of the ticket organization and requester are displayed against each event.

Select the organization or requester links to drill down into the respective forms to see full details.

(3) The name or label given to the event for the SLA Plan specification

The label can be different for each type of event depending upon the configurations for the associated SLA Plan.

Select the subject link to drill down into the ticket form for the associated ticket from where a description of the SLA Plan and event can be viewed using the SLA Assistant.

(4) The criteria for completing the event has NOT yet been met, but the timer is still running

If the event or task has NOT been completed but the due date time (7) has yet to be reached, then the SLA-M Dashboard will indicate that the timer is still running through the presence of a green box and the number of days/hours/mins remaining to complete the task.

*Note: the figure displayed in the green box is the number of actual or calendar days/hours/mins elapsed before a violation will occur, not the number of business hours used to calculate the due date/time, which might be significantly less.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(5) The warning timer has fired for this event since the due date/time for completion is imminent

If your CloudSET SLA Management setup has been configured to make use of warning timers, then the SLA-M Dashboard will indicate when a warning timer has fired through the presence of an amber box.

Also depending upon your setup, a warning notification will have been emailed to the assigned agent and/or other groups and individuals.

Your Zendesk administrator will have configured the number of minutes before the due date/time that the warning timer should fire in the SLA Plan specifications.

(6) The SLA has been violated and the criteria for completing the event has NOT yet been met

If the due date/time (7) is now in the past and the event or task has still yet to be completed, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red box and the number of days/hours/mins overdue.

*Note: the figure displayed in the red box is the number of actual or calendar days/hours/mins elapsed since the violation occurred, not the number of business hours used to calculate the due date/time.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(7) The time for the event has been paused

If your setup has been configured to pause any event timers on Pending or On-hold then these are displayed with a black background and the number of business hours remaining on the timer.

*Note: your SLA-M Dashboard must configured to include tickets in a status of Pending and On-Hold

(8) The due date/time by when the event criteria must have been met in order to pass the agreed SLA

Hover over the countdown value to display the due date/time by when the event or task should be or should have been completed.

Regardless of the time-zone associated with the ticket (see Regions), the due date/time will always be displayed using the time-zone configured in the Zendesk profile for the current user.

(9) The amount of time remaining before the SLA-M Dashboard will be automatically refreshed

This counter indicates the amount of time remaining before the contents of the SLA-M Dashboard will be refreshed with the latest information.

*Note: see Refreshing Information in the SLA-M Dashboard for full details.

Working in Destination Board (Tickets) Mode

Working in Destination Board (Tickets) Mode

As described in Introduction to the SLA-M Dashboard the SLA-M Dashboard provides an alternative operating mode that is more akin to a standard Zendesk view, with added benefits.

The Tickets destination board provides a tabular list of all tickets that have at least one of the following:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

However, unlike when working in the Events mode, so long as at least one event has yet to be completed, this destination board will also provide information about events that have met the criteria to determine completion the associated task.

In addition to the information available when working in Events mode (see above), when using the SLA-M Dashboard in Tickets mode the Destination Board will also provide the following:

(1) Sorting Tickets

Just like a standard Zendesk view it is possible to sort the list of tickets in the table by selecting any of the column headings.

(2) The Next Event due for the associated ticket

Regardless of the number of running events the ticket will only appear once in the list and this column will always display the event or task that has the earliest due date/time and so is due for completion next to avoid an SLA breach.

Hover over the countdown value to see the name of the event and the due date/time by when the associated task must be completed.

(3) Information about system ticket fields

If your SLA-M Dashboard has been configured to include one or more system ticket fields (see Configuring and Customizing the SLA-M Dashboard) then these values are displayed as columns.

(4) Custom Status and Custom Priority

If your SLA solution is making use of a Custom Status and/or Custom Priority and your SLA-M Dashboard has been configured to make use of these fields, then the values will be displayed as columns in this destination board.

(5) Information about SLA Events

It is possible to show or hide columns to display information about each of the SLA events in use by your CloudSET SLA Management setup and configuration.

This can include events that have met the criteria to determine completion the associated task.

Having done so it is then possible to sort the tickets using the column heading to bring the events of most interest or importance to the current user to the top of the queue.

(6) The criteria for completing the event has been met within the agreed SLA

If the event or task is completed before the due date time, then the timer will be stopped and the SLA-M Dashboard will indicate an SLA pass through the presence of a green tick.

(7) The criteria for completing the event has been met, but NOT within the agreed SLA (violated)

If the event or task has been completed but only after the due date time, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red tick.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Interpreting the Information in the SLA-M Dashboard

Sub Banner

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

Interpreting the Information in the SLA-M Dashboard

The SLA-M Dashboard provides a number of alternative dynamically configurable views of all your open tickets, interpreting the information pertaining to the progress and status of the SLA metric for each event modeled in your SLA process as follows.

*Note: please see Introduction to the SLA-M Dashboard for more detailed on the purpose and types of operational mode.

Working in Destination Board (Events) Mode

Working in Destination Board (Events) Mode

When using the SLA-M Dashboard in Events mode the Destination Board will only ever include information about ticket events that either:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

i.e., once the criteria to determine completion the event or associated task has been met (e.g. an initial response has been given) the event will no longer appear in this destination board.

*Note: See Identify when a timer has paused or stopped for circumstances under which an event will also not be included in the SLA-M Dashboard.

The following information available when using this operating mode:

(1) The ticket Subject

The subject of the ticket associated with the event.

Hover over the subject to pop-up additional information about the associated ticket such as the Status, ID, system priority, description and latest comment.

Select the subject link to drill down into the ticket form for the associated ticket from where full SLA details can be viewed using the SLA Assistant.

(2) The Organization and Requester of the associated ticket

If your SLA-M Dashboard has been configured to include this information (see Configuring and Customizing the SLA-M Dashboard) then the name of the ticket organization and requester are displayed against each event.

Select the organization or requester links to drill down into the respective forms to see full details.

(3) The name or label given to the event for the SLA Plan specification

The label can be different for each type of event depending upon the configurations for the associated SLA Plan.

Select the subject link to drill down into the ticket form for the associated ticket from where a description of the SLA Plan and event can be viewed using the SLA Assistant.

(4) The criteria for completing the event has NOT yet been met, but the timer is still running

If the event or task has NOT been completed but the due date time (7) has yet to be reached, then the SLA-M Dashboard will indicate that the timer is still running through the presence of a green box and the number of days/hours/mins remaining to complete the task.

*Note: the figure displayed in the green box is the number of actual or calendar days/hours/mins elapsed before a violation will occur, not the number of business hours used to calculate the due date/time, which might be significantly less.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(5) The warning timer has fired for this event since the due date/time for completion is imminent

If your CloudSET SLA Management setup has been configured to make use of warning timers, then the SLA-M Dashboard will indicate when a warning timer has fired through the presence of an amber box.

Also depending upon your setup, a warning notification will have been emailed to the assigned agent and/or other groups and individuals.

Your Zendesk administrator will have configured the number of minutes before the due date/time that the warning timer should fire in the SLA Plan specifications.

(6) The SLA has been violated and the criteria for completing the event has NOT yet been met

If the due date/time (7) is now in the past and the event or task has still yet to be completed, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red box and the number of days/hours/mins overdue.

*Note: the figure displayed in the red box is the number of actual or calendar days/hours/mins elapsed since the violation occurred, not the number of business hours used to calculate the due date/time.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.

Once the event or task has been completed then the event will no longer be displayed when using the SLA-M Dashboard in Events mode.

(7) The time for the event has been paused

If your setup has been configured to pause any event timers on Pending or On-hold then these are displayed with a black background and the number of business hours remaining on the timer.

*Note: your SLA-M Dashboard must configured to include tickets in a status of Pending and On-Hold

(8) The due date/time by when the event criteria must have been met in order to pass the agreed SLA

Hover over the countdown value to display the due date/time by when the event or task should be or should have been completed.

Regardless of the time-zone associated with the ticket (see Regions), the due date/time will always be displayed using the time-zone configured in the Zendesk profile for the current user.

(9) The amount of time remaining before the SLA-M Dashboard will be automatically refreshed

This counter indicates the amount of time remaining before the contents of the SLA-M Dashboard will be refreshed with the latest information.

*Note: see Refreshing Information in the SLA-M Dashboard for full details.

Working in Destination Board (Tickets) Mode

Working in Destination Board (Tickets) Mode

As described in Introduction to the SLA-M Dashboard the SLA-M Dashboard provides an alternative operating mode that is more akin to a standard Zendesk view, with added benefits.

The Tickets destination board provides a tabular list of all tickets that have at least one of the following:

  • Have running timers because the criteria to determine completion the event or associated task has yet to be met
  • The timers have finished but the criteria to determine completion the event or associated task has yet to be met

However, unlike when working in the Events mode, so long as at least one event has yet to be completed, this destination board will also provide information about events that have met the criteria to determine completion the associated task.

In addition to the information available when working in Events mode (see above), when using the SLA-M Dashboard in Tickets mode the Destination Board will also provide the following:

(1) Sorting Tickets

Just like a standard Zendesk view it is possible to sort the list of tickets in the table by selecting any of the column headings.

(2) The Next Event due for the associated ticket

Regardless of the number of running events the ticket will only appear once in the list and this column will always display the event or task that has the earliest due date/time and so is due for completion next to avoid an SLA breach.

Hover over the countdown value to see the name of the event and the due date/time by when the associated task must be completed.

(3) Information about system ticket fields

If your SLA-M Dashboard has been configured to include one or more system ticket fields (see Configuring and Customizing the SLA-M Dashboard) then these values are displayed as columns.

(4) Custom Status and Custom Priority

If your SLA solution is making use of a Custom Status and/or Custom Priority and your SLA-M Dashboard has been configured to make use of these fields, then the values will be displayed as columns in this destination board.

(5) Information about SLA Events

It is possible to show or hide columns to display information about each of the SLA events in use by your CloudSET SLA Management setup and configuration.

This can include events that have met the criteria to determine completion the associated task.

Having done so it is then possible to sort the tickets using the column heading to bring the events of most interest or importance to the current user to the top of the queue.

(6) The criteria for completing the event has been met within the agreed SLA

If the event or task is completed before the due date time, then the timer will be stopped and the SLA-M Dashboard will indicate an SLA pass through the presence of a green tick.

(7) The criteria for completing the event has been met, but NOT within the agreed SLA (violated)

If the event or task has been completed but only after the due date time, then the timer will previously have been stopped and the SLA-M Dashboard will indicate an SLA violation through the presence of a red tick.

Also depending upon your setup, a violation notification will have been emailed to the assigned agent and/or other groups and individuals.