In Freshdesk, you can create multiple SLA policies and enforce a different agreement for each ticket based on various conditions. For example, you might want a different SLA policy for certain customers, or for tickets related to specific products. 



To enforce a new SLA policy, click on the New SLA Policy button on the SLA Policies page. You'll then have to define SLA targets for each ticket priority, just like you did with the default policy.


Next, set up the condition(s) based on when you want this particular policy to be triggered. Here are the various conditions you can use to trigger a specific SLA policy:


Company - you can choose to apply this SLA policy only for the companies you specify here. For example, you might want to trigger a particular SLA policy only for customers who have purchased your Priority Support Subscription.

Group - if you want this policy to apply only for specific Agent Groups, you can select them here. For example, you might want to define a different set of service levels for your finance group which has to process refunds. 

Product - if you're supporting multiple products or brands through a single Freshdesk account, you can define which product(s) this particular policy must be applied to.

Source - you might want to set a different service level target for tickets coming in through Twitter, as compared to those through email. 

Type - you can select the SLA to be enforced based on the type of problem that you are facing; such as a billing problem, or a potentially serious bug, for example.



You will need to defineat least one trigger conditionfor each SLA policy. Remember - the order of your SLA policies is important.If you have multiple SLA policies, the first one with matching conditions will be applied to a ticket. 


For example, let's say that you have a special SLA policy (SLA 1) for tickets from Customer A, and you have another policy (SLA 2) for tickets assigned to Group X; and these are ordered with SLA 1 on top and SLA 2 second. A ticket from Customer A that's assigned to Group X will trigger SLA 1's conditions first and so SLA 1 will be applied.


You can reorder your SLA rules, and organize them in such a way that the most restrictive (strict) rules are higher up in the order.


Quick guide to configuring multiple SLAs:

  • Go to Admin > General Settings > SLA Policies

  • Click on New SLA Policy

  • Choose the SLA Targets for each ticket priority

  • Select the trigger conditions (when this rule must be applied)

  • Enter up to 4 levels of escalation hierarchies
  • Click on Save

In Freshdesk, you can create multiple SLA policies and enforce a different agreement for each ticket based on various conditions. For example, you might want a different SLA policy for certain customers, or for tickets related to specific products. 



To enforce a new SLA policy, click on the New SLA Policy button on the SLA Policies Page. You will have to define SLA targets for each ticket priority, just like you did with the default policy.


Next, setup the condition(s) based on when you want this particular policy to be triggered. Here are the various conditions you can use to trigger a specific SLA policy:


Company: You can choose to apply this SLA policy only for the companies you specify here. For example, you might want to trigger a particular SLA policy only for customers who have purchased your Priority Support Subscription.

Group: If you want this policy to apply only for specific Agent Groups you should mention that here. For example, you might want to define a different set of service levels for your finance group which has to process refunds. 

Product: If you are supporting multiple products or brands through a single Freshdesk account, you can define which product(s) this particular policy must be applied to.

Source: You might want to set a different service level target for tickets coming in through Twitter, as compared to those through email. 

Type: You can select the SLA to be enforced based on the type of problem that you are facing. Be it simple problems in billing or a show-stopping bug, you can decide which SLA policy is to be followed.  



You will need to define at least one trigger condition for each SLA policy. Remember - the order of your SLA policies is important. If you have multiple SLA policies, the first one with matching conditions will be applied to a ticket. 


For example, consider you have a special SLA policy (SLA 1) for tickets from a specific Customer A, and you have another policy (SLA 2) for tickets assigned to Group X ordered with SLA 1 on top and SLA 2 second. A ticket from Customer A, assigned to Group X will match with the rules in SLA 1 (which is on top), and so SLA 1 will be applied. 


You can reorder your SLA rules, and organise them in such a way that the most restrictive (strict) rules are higher up in the order.


Quick guide to configuring multiple SLAs:

  • Go to Admin > SLA Policies

  • Click on New SLA Policy

  • Choose the SLA Targets for each ticket priority

  • Select the trigger conditions (when this rule must be applied)

  • Enter up to 4 levels of escalation hierarchies
  • Click on Save, to save the policy