In this article, we will cover the Capping and Fallback Owner features in Distro and how to use them to ensure a smooth distribution among your Team Members!

Table of Contents

• Capping
  • How can I configure the Capping for Team Members?
  • What happens when the whole team reaches their Capping?
• Fallback Owner
  • How can I configure the Fallback for Team Members?

Capping

The Capping feature in Distro is a powerful tool that allows you to manage workload distribution and ensure fairness among team members. It does this by capping the number of records that can be assigned to a particular Assignee within a specified timeframe.

This feature is particularly useful in managing workload distribution and ensuring fairness among Team Members.

How can I configure the Capping for Team Members?

The process should be pretty simple!

1. Create a Router and add on a route the node "Assign & Update Ownership"
   
   
   
2. Click on Fairness, and then click on Capping Cycle on the right:
   
   
   
3. Set the Capping Reset Cycle (Daily, Weekly, or Monthly) and the Time Zone. If weekly is selected, we ask for the first day of the week.
   
   
   
4. Cap the whole team with the same number of records by updating the box in the Capping column:
   
   
   Or Cap team members individually.
   
   
   If no value is provided in the Capping-related boxes (Team or individual-wise), there will be no limit of records that can be assigned within the selected timeframe.
   
   Also, if you need to start from scratch, the Clear button at the top clears the Team's capping all at once, or you can remove the capping from each Team Member individually.
   
   
5. Do not forget to Publish Changes once you are done!
   
   

What happens when the whole team reaches their Capping?

Supposing that your Team had a cap of 20 records to be distributed Weekly, and this number was reached, we assign the record to a Fallback Owner, which will be explained in the next section!

Fallback Owner

The Fallback Owner feature in Distro refers to a functionality that helps assign a record in case the initial Assignee selected by Distro is either:

• Unavailable
• Already reached the cap of records assigned to them, as explained in the Capping section.

This feature is particularly useful if the record matches an Ownership Rule and the assignee is not available because, for example, their Salesforce License does not authorize it.

How can I configure the Fallback for Team Members?

1. Create a Router and add an "Assign & Update Ownership" node:
   
   
   
2. If not completed before, set the Capping for your Team Members as explained in the Capping section here. If you already did it, proceed to the next step (3).
   
   
3. Within the "Assign & Update Ownership" node, you can select a Fallback Owner for two use cases: If Team Member is Unavailable and If Capping Limit is reached.
   
   
   
4. Over there, you can select among the following options. Before covering them in more detail, it's important to mention that you can use different options in the Unavailable and Capping-related sections.
   
   For example, you can set No Fallback in the Unavailable-related section and User in the Capping-related section.

• No Fallback: If the user is unavailable or has reached their Capping, there will be no Fallback, and this user will not receive more records until they are available or the Capping is reset (Daily, Weekly, or Monthly basis).
  
  
• User: Here, you can assign one specific user to receive the Fallback records when someone is Unavailable or has reached their Capping.
  
  
• Team via Round Robin: Within this option, you can assign a Team to receive these Fallback records in a Round Robin distribution among the Team Members.