nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Address Finder and Seasonal Addresses

JoAnn Strommen

We have been using the automatic NXT address finder process. Just had a call from someone saying they didn't know how their address got changed to AZ. They live in SD.

Well, looking at their record is was easy to see why. They have a seasonal address 12/1 to 3/31 in Arizona on their record. On March 12, the AZ record was marked as preferred by AddressFinder. I don't know why on the June run of AddressFinder that the SD address was not marked as preferred. It should have been.

Anyone have any suggestions or experience with seasonal addresses being updated to preferred addresses? Is there a setting that addresses this? How do you filter to find them? Manually change them back? Just a headache I really don't need or have time for. LOL We have a good # of snowbirds.

Find more posts tagged with

Comments

Faith Murray

Goodness! Hmm… Run a query immediately following Addressfinder, looking for any addresses marked seasonal with date last changed = today? Do you include any new Address Source data with your Addressfinder uploads?

To tell you the truth, we never just download address data from the plugin. I run the service in database view and then download the excel file of address results. Then manually import. It allows me better ability to scan the results for “high-risk” individuals, and then confirm the move before uploading, because we have a number of pastors, student alumni, etc. who move around a lot. ?

Kelly Wepsiec

We specific only HOME preferred addresses when we send data in. That would prevent this from happening most of the time I think. But if the constituent sent in a mail forwarding form it might not help at all. A lot of the data returned gets reviewed manually because of this.