Preferred addresses that are actually bad addresses

We just converted to RENXT about six months ago — I don't mean from RE, but from an entirely different system.

We've been getting a lot of returned mail. Users are creating web view lists to generate mailing lists. This means that the preferred, starred, address is always selected.

For some constituents, though, we don't have any good mailable address at all. Their bad address (lost, deceased, omit-from-mailing) is only marked as preferred because the software requires constituents to have a preferred address.

It would be better to see a blank address, rather than a bad address.

So I think I should export all the preferred addresses, using database view so I can include the address type -- That way I can see which constituents should never be sent mail (lost, deceased, omit-from-mailing). For those constituents, I will import new blank addresses that are marked as preferred.

I don't want to delete the bad addresses (for historical purposes). But my aim is to push the bad addresses out of the way, so that the web view's lists won't make it seem like they are mailable addresses.

And this should only take a fraction of the time that would be required to train users to export from database view.

This should work, right?

Answers

  • If the deceased are so marked, then users should be trained to exclude them from their lists (I believe some default settings in NXT/WV already do that).

    There is also the "Mark Do Not Mail" button for an address. And an address can be both preferred and Do Not Mail at the same time. Again, users should be trained to exclude addresses marked "Do Not Mail" from mailings.

    The problem with having a blank preferred address is that inactive addresses are not immediately visible when a user opens the record. One has to actively click on several buttons to check for inactive addresses. And from personal experience, I can tell you that despite the ease of NXT in its WV version, users will not check for inactive addresses. And so you risk addition of duplicates or the same bad address to be added back in as the preferred address or misidentification/non-identification of donors or relationship that should be linked.

    Just my 2 cents.

  • Just read Carlene's post. She's said what needs to be said.

  • Carlene Johnson
    Carlene Johnson Community All-Star
    Tenth Anniversary Kudos 5 PowerUp Challenge: Data Health #3 First Reply

    I'm impressed you made it the whole way through! 🤣

  • Great job, Carlene! Thanks for the shoutout on the resource as well, which to this day is just about as applicable as it was years ago when it was created. Two additional thoughts:

    On your 1. above: mailings should be done from Query + MAIL, not Export. :) Only use Export if Mail truly cannot do what legitimately needs to be done.

    Another reason for not removing bad addresses from the Preferred address is that every copy of NXT comes with an AddressFinder subscription for NCOA. That works on your having and providing the last address you have for that person, and it needs to be the Pref address. If you want to find them, you need to leave the address there.

    Thanks!

  • Carlene Johnson
    Carlene Johnson Community All-Star
    Tenth Anniversary Kudos 5 PowerUp Challenge: Data Health #3 First Reply

    Excellent point, Bill! I've fallen out of the habit of using Mail and tend to export as my default, but Mail has a ton of fantastic features that shouldn't be overlooked.

    It will be interesting to see what, and in what manner, different pieces of Mail functionality are brought over to the Unified View.

  • Wow, thanks for the helpful feedback, everybody. I'm learning! So…

    We could have a static query that selects all living constituents who have a preferred address that is "Home" and doesn't say "do not mail". Then, the training required within our department is twofold:

    1. For me: Run that dang static query once or twice a week. (We are so small that I think this would be often enough)
    2. For a user who doesn't know database view: Anytime your constituent list is going to be used for mailing, build your list off of that static query.

    Now, that should work… right?

    Jumping in as RENXT users while the company is in the middle of moving to unified view is interesting; everything is a moving target. I just hope the unified view will have all of the same filters and columns that are in database view.

  • Among our (dynamic) maintenance queries, we have some that scope for (in)valid addresses, based on e.g. "Address Line1 blank" AND "No Valid Addresses? equals No" and similar combinations, to weed out the non-addresses. Something like that might be easier. You could do one big clean now then just run those maintenance queries once a week.

Categories