Last updated: 2025-11-18

Source: https://support.freshservice.com/support/solutions/articles/156457-defining-your-default-sla-policy

Defining your Default SLA policy

``` Note: This feature works the same across all Freshservice products. Some screenshots or articles may reflect older designs, but the functionality remains unchanged. If certain options do not appear in your account, they may not be included in your current plan. ```

The default SLA policy in Freshservice will be applicable to all tickets coming into your helpdesk. It will define the due by time on your ticket based on the priorities of your tickets. Once you have configured it in your system, it will control the way your agents work everyday by telling them what ticket they have to work on next in sequential order.

A quick guide to creating a Default SLA policy:

  • Click on Admin > Service Management > Service Desk Settings > SLA and OLA Policies.

    • If your account has more than one workspace:

    To modify global workflows, navigate to Admin > Global Settings > Service Management > Service Desk Settings > SLA and OLA Policies

    To modify workspace-level workflows, navigate to Admin > Workspace Settings > {Workspace Name} > Service Management > Service Desk Settings > SLA and OLA Policies

    ``` Important Note: Workspace admins can create SLA policies at a workspace level. 1. Global SLA policies apply to tickets across all workspaces 2. Default SLA policy is created and enabled by default at the global level. 3. Order of execution: The SLA policy for the ticket is determined by the local

    SLA policies created for a specific workspace. If the specified conditions in the local SLA policies do not match, then it follows the global policy. If both do not apply, then the default SLA policy becomes applicable to the ticket. ```

  • Under the Default SLA Policy, click on the Edit button.
  • Optionally, rename the Default Policy and provide a brief description.
  • Complete the time-priority matrix.
  • SLA Policies are determined by the ticket priority. You can define what constitutes a high, or low priority ticket manually, or automate it using the Workflow Automator.

  • Remember to choose whether the SLA times must be calculated based on Business or Calendar hours.
  • If you would like to enable escalations when service levels are violated, toggle the Escalation Email button to On.
  • Next, set up your escalation hierarchy by defining when a ticket must be escalated, and to whom. You can set up to four levels of Escalations, for ticket resolution and one level for ticket response.
  • Click on the Save button to finish setting up your SLA Policy.

    • You can also create multiple SLA policies in Freshservice for different customer tiers, products, agent groups, etc. For example, you could have an "Express Support" SLA policy for high-value clients. Click here to know more about setting up Multiple SLA policies.

    Note: Admins can now define internal Operational Level Agreements (OLA) on tickets/problems/changes and release (TPCR) tasks. This will dictate the time within which Agents should complete Tasks inside the TPCR, ensuring continuous service delivery and compliance. More details here.