Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cmsmasters-content-composer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookie-law-info domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mailpoet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the the-events-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the startup-company domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/billezya/public_html/lpm.backup/wp-includes/functions.php on line 6260
How to configure Service Level Agreements - BIlletterie LPM

How Can We Help?

How to configure Service Level Agreements

Created On
Last Updated On
byBilletterie
← All Topics
  • On the Admin panel, click on the SLA icon
  • Enter a unique name to identify the SLA in the name field
  • Provide a brief description for the SLA
  • Click on the Services field, and from the drop down list, select the service to be linked to the SLA
  • Define the SLA by clicking on Days to Accept or reject SLA field and enter the SLA values
  • Click on the SLA Responses table to set the priorities relevant to the SLA
  • Click on Save