{"id":4242,"date":"2023-05-16T05:47:32","date_gmt":"2023-05-16T05:47:32","guid":{"rendered":"https:\/\/blog.osmosys.co\/?p=4242"},"modified":"2024-02-09T06:03:05","modified_gmt":"2024-02-09T06:03:05","slug":"configure-sla-in-dynamics-365","status":"publish","type":"post","link":"https:\/\/osmosys.co\/ca\/configure-sla-in-dynamics-365\/","title":{"rendered":"Configure SLA in Dynamics 365"},"content":{"rendered":"
<\/div>\n

What exactly are SLAs?<\/h2>\n\n\n\n

SLAs, or Service level Agreements, establish the level of service provided to clients in many businesses. Using SLAs in Dynamics 365<\/a> Customer Service, we can define the level of service or support an organization agrees to provide a customer. Providing help based on service levels guarantees that you deliver measurable and predictable results. SLAs provide advantages such as tracking service level performance and goals, prioritization of cases, and reminders to customer service employees.<\/p>\n\n\n\n

To configure SLAs, we must first construct SLA KPIs and SLA items, and then apply the SLA via entitlements or a default SLA, as discussed in this blog.<\/p>\n\n\n\n

Steps to Get Started<\/strong><\/h2>\n\n\n\n

To begin building SLA for an entity, we must first ensure that SLA is enabled for that entity.<\/p>\n\n\n\n

    \n
  1. Open Custom Solution for this.<\/li>\n\n\n\n
  2. Select the entity from the left pane.<\/li>\n\n\n\n
  3. Check the Enable for SLA check box under Communication & Collaboration.<\/li>\n\n\n\n
  4. Save and publish your work<\/li>\n<\/ol>\n\n\n\n
    \"\"<\/figure>\n\n\n\n

    Additionally, we must ensure that SLAs are not disabled because of this.<\/p>\n\n\n\n

    Open the Service Configuration Settings window.<\/p>\n\n\n\n

    Ensure Disable SLA is configured to No<\/u><\/strong>.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Setting up Holiday and Customer Service Schedule<\/strong><\/h2>\n\n\n\n

    We can avoid our SLAs being affected and recorded on the days when service organization is closed by creating a Holiday Schedule Calendar.<\/p>\n\n\n\n

      \n
    1. Open Holiday Schedule<\/strong> in Service Management<\/li>\n<\/ol>\n\n\n\n
      \"\"<\/figure>\n\n\n\n
        \n
      1. Click New, Add Name and Description then click Create<\/li>\n<\/ol>\n\n\n\n
        \"\"<\/figure>\n\n\n\n
          \n
        1. Select New in Holiday Grid<\/li>\n<\/ol>\n\n\n\n
          \"\"<\/figure>\n\n\n\n
            \n
          1. Add details<\/li>\n<\/ol>\n\n\n\n

            We need to associate this Holiday schedule with a Customer Service Schedule later.<\/p>\n\n\n\n

            Customer Service Schedule store details of business hours of each day and weekly off. These details are used in the time tracking of SLAs by customer service. For Creating Customer Service Schedule,<\/p>\n\n\n\n

              \n
            1. Open Customer Service Schedule<\/strong> in Service Management<\/li>\n\n\n\n
            2. Click New, Add Name and Description then click Create<\/li>\n<\/ol>\n\n\n\n
              \"\"<\/figure>\n\n\n\n
                \n
              1. Under Weekly Schedule select the work hours for day by using Set Work Hours<\/strong> and days of the week when customer service is available.<\/li>\n\n\n\n
              2. In Holiday Schedule<\/strong> select Observe and select the created Holiday Schedule.<\/li>\n<\/ol>\n\n\n\n
                \"\"<\/figure>\n\n\n\n

                Creating SLA KPIs<\/strong><\/h2>\n\n\n\n

                SLA KPIs are the performance indicators that we want to track. It holds the data for the KPI field, entity and which field the KPI is applicable from.<\/p>\n\n\n\n

                  \n
                1. Open SLA KPIs<\/strong> in Service Management and select new, here we can add the required data:
                  Name: The name of the SLA KPI.
                  Entity Name: Select the entity for which the KPI will be measured.
                  KPI Field: Select the respective KPI field.
                  Applicable From: Select a value based on which the warning and failure time will be measured<\/li>\n<\/ol>\n\n\n\n
                  \"\"<\/figure>\n\n\n\n
                    \n
                  1. KPI Fields define N:1 relationship between the entity and the SLA KPI Instance entity. We can create our own by creating a lookup field for the SLA KPI Instance Entity on the required entity.<\/li>\n\n\n\n
                  2. We can define Pause Conditions<\/strong> for the SLA KPI. For example, if we want the KPI to pause if the Status Reason of the entity  is set to either On Hold or Waiting for Details<\/li>\n<\/ol>\n\n\n\n
                    \"\"<\/figure>\n\n\n\n

                    Creating SLA<\/strong><\/h2>\n\n\n\n
                      \n
                    1. On Service Management, Select SLA then NEW<\/li>\n\n\n\n
                    2. Enter the Name, Description, and Primary Entity<\/li>\n\n\n\n
                    3. Save the form to view SLA Item section<\/li>\n<\/ol>\n\n\n\n
                      \"\"<\/figure>\n\n\n\n

                      Creating an SLA Item<\/strong><\/h2>\n\n\n\n

                      A SLA can have multiple SLA items associated with it. A SLA item determines the Warning and Failure Time based on the Applicable from field on the SLA KPI and gives us features to specify conditions and actions. To add SLA Item to SLA:<\/p>\n\n\n\n

                        \n
                      1. Open SLA record and select New SLA Item to open dialogue<\/li>\n<\/ol>\n\n\n\n
                        \"\"<\/figure>\n\n\n\n
                          \n
                        1. Enter the required details:
                          Name: Item name
                          KPI: Select the KPI to be associated
                          Allow Pause and Resume: Enable this option if you want the SLA to be paused during the time the record is on hold.
                          Business Hours: Select the Customer Service Schedule entity to be associated<\/li>\n<\/ol>\n\n\n\n
                          \"\"<\/figure>\n\n\n\n
                            \n
                          1. In the Applicable When section, we can define the conditions for the entity when the SLA can be applied.<\/li>\n<\/ol>\n\n\n\n
                            \"\"<\/figure>\n\n\n\n
                              \n
                            1. In the Success Conditions section, we define the success criteria for our SLA<\/li>\n<\/ol>\n\n\n\n
                              \"\"<\/figure>\n\n\n\n
                                \n
                              1. In the Pause Configurations section we can add conditions to pause SLA item. Select Yes in Override Criteria to override settings defined at entity, Service Configuration or SLA KPI level. <\/li>\n<\/ol>\n\n\n\n
                                \"\"<\/figure>\n\n\n\n
                                  \n
                                1. In Warn and Fail Duration section, add time after which warning and failure notifications are sent.<\/li>\n<\/ol>\n\n\n\n
                                  \"\"<\/figure>\n\n\n\n

                                  Configuring Actions<\/strong><\/h2>\n\n\n\n

                                  In an SLA Item, we can also configure actions to be triggered based on SLA success, failures, or for warnings. For this,<\/p>\n\n\n\n

                                    \n
                                  1. Select Configure Actions, in the action pane of the SLA item to open Power Automate.<\/li>\n<\/ol>\n\n\n\n
                                    \"\"<\/figure>\n\n\n\n
                                      \n
                                    1. Select Continue to confirm the connection.<\/li>\n\n\n\n
                                    2. A predefined flow specific to SLA appears.<\/li>\n\n\n\n
                                    3. We can see the Switch step in the flow which has three conditions
                                      Is Nearing Non-Compliance: Will run when the warning time is reached for the SLA
                                      Is Succeeded: Will run when the SLA succeeds
                                      Is Non-compliant: Will run when the SLA fails<\/li>\n<\/ol>\n\n\n\n
                                      \"\"<\/figure>\n\n\n\n
                                        \n
                                      1. Under each condition we can add an action to be executed such as send a warning email based on SLA conditions.<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

                                        What exactly are SLAs? SLAs, or Service level Agreements, establish the level of service provided to clients in many businesses. Using SLAs in Dynamics 365 Customer Service, we can define the level of service or support an organization agrees to provide a customer. Providing help based on service levels guarantees that you deliver measurable and […]<\/p>\n","protected":false},"author":26,"featured_media":235281,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[51],"tags":[22,67,68],"class_list":["post-4242","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dynamics-365","tag-crm","tag-dynamics365","tag-sla"],"modified_by":null,"jetpack_featured_media_url":"https:\/\/osmosys.co\/ca\/wp-content\/uploads\/sites\/5\/2023\/05\/configure-sla-crm.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/4242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/comments?post=4242"}],"version-history":[{"count":3,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/4242\/revisions"}],"predecessor-version":[{"id":235471,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/posts\/4242\/revisions\/235471"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media\/235281"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/media?parent=4242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/categories?post=4242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/ca\/wp-json\/wp\/v2\/tags?post=4242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}