UPDATE 2022-12-05: After some thought, we enhanced the outboundANI CSV upload tool to detect this mistake, and auto-randomize the load order to smooth out problematic geographic clusters...one more benefit to loading your data through the outboundANI app...this is live, effective immediatley... ;-)
This is a very specific type of post, addressing a very specific type of problem, but due to the frequency we're encountering it, I figured it made sense to give little advice here...
When loading your data into the dialer, DO NOT sort that data by state, or by area code, or by phone number!
If you do sort and load in that manner, the dialer typically follows the order, and will absolutely issue tons of dials in a row into certain area codes or localities. And when it does that, too many dials at once will be issued from your outbound ANI's in those area codes and localities, creating high utilization and burst dialing scenarios that will absolutely crush the hygiene of those ANI's...
In outboundANI, this is visible when watching the US map dashboard, as literally one state at a time lights up in the map...
The goal with the data load is to randomize and spread the dials across the country as best you can, keeping the volume of dials into each area code and locality evenly paced and evenly distributed...so sorting by first name, last name, email, or some other non-bundling attribute, is a far better way to go...
It's remarkable that something as seemingly insignificant as the sort order of the spreadsheet or CSV file can make all the difference in the world to your SPAM exposure and contact rate, but trust me - it can...this week alone we've addressed this problem with no less than 7 different customers...
So just be careful...contacting prospects is difficult enough already these days, please keep the self-inflicted wounds to a minimum... :-)