Overview
This setting in SalesExec controls the order in which leads are “pulled” from a pull queue by your sales team. You can prioritize by how many times a lead has been pulled (Pull Count) or by when the lead was added (Date Added). This helps you strike a balance between contacting new leads and giving older or less-pulled leads another chance.
Key Functionality
Pull Count Priority
Lowest Pull Count First: Prioritizes leads that have been pulled the fewest times — useful if you want to ensure every lead gets a minimum number of contact attempts.
Highest Pull Count First: Prioritizes leads that have already been pulled many times — useful if you want to concentrate effort on “hot” leads that haven’t converted yet.
Date Added Priority
Newest First: Prioritizes the most recently added leads — helps maximize speed-to-lead for fresh inbound leads.
Oldest First: Prioritizes older leads in your queue — useful for recycling leads that may still be valuable or were never contacted.
Drag-and-Drop Priority Ordering
Allows admins to visually reorder priority types if you have multiple priority tiers or want to combine logic.
How to Use This Feature
A common question asked is how to determine the order in which leads are pulled by your sales teams. ClickPoint Pull Distribution allows an administrator to dictate silos of leads which are worked, in order, by sales teams. This article will overview configuring Pull Priorities to help maximize your speed to lead goals.
Pull Distribution Priorities
Navigate to More > Settings > Lead Distribution located under the header Setup Lead Routing. Edit a distribution strategy and from here, you will find Pull Priorities. As an administrator, you have the ability to adjust the order in which leads are pulled, based on the number of times they have already been pulled and also by the date they were added.
Adjusting Priorities
By Default, when a new distribution is created, the order is set FIFO (first in, first out) order. For a vast majority of your leads, this will be the method in which you work your leads. However, you can create multiple distribution strategies that target very specific leads based on when they were worked and when they were added. Below is all the possible combinations so that you can make a decision that best fits your business needs.
Priority Combination Options
Pull Count: Lowest First
Date Added: Newest First
Note: This is the default order when creating a new distribution strategy and this is likely the best option to use for most business situations.
Pull Count: Newest First
Date Added: Lowest First
Pull Count: Newest First
Date Added: Newest First
Date Added: Lowest First
Pull Count: Lowest First
Date Added: Lowest First
Pull Count: Newest First
Date Added: Newest First
Pull Count: Newest First
Best Practices
Use Lowest Pull Count First when you want to make sure each lead gets multiple contact opportunities.
Use Highest Pull Count First when focusing on leads that show recurring interest or engagement.
Use Newest First to maximize speed-to-contact for brand-new leads — especially for high-intent campaigns.
Use Oldest First to rework leads that were never contacted or didn’t convert previously.
Combine priority logic smartly: for example, use Pull Count as your primary priority, then Date Added as a tiebreaker.
Rebuild the queue whenever you change priority rules to ensure the lead order reflects your new logic.
Troubleshooting
Priority change didn’t take effect → Make sure you saved your strategy settings and rebuilt the queue.
Leads are still being pulled in an unexpected order → Double-check the priority logic you configured (pull count + date) and confirm the ranking/order is correct.
Queue is empty after rebuild → There may be no leads matching your pull criteria; review filters and criteria.
Too many old leads being pulled first → If you prioritized “Oldest First,” consider switching to “Newest First” or adjusting your mix logic.
Lead count feels imbalanced across reps → Revisit your Pull Count priority to avoid letting a few leads dominate the queue repeatedly.