Bad Addresses

Is there a way to "inactivate" a primary address?  We have mail come back due to bad addresses.  Because the system requires a primary address, is there a way to inactivate it so we do not continue to pull an incorrect address into lists?  If not, how do others handle this problem?  Thank you!

 

Parents
  • Our work-around has been working really well for us!

    When we realize an address in Tessitura is incorrect, we update the primary address to read:
    Needs Address
    Austin, TX 99999

    The "Needs Address" is an easy visual flag for users to update addresses whenever pulling up an account for any transactions. And the "99999" zipcode is an easy suppression in Extraction Manager.

    Greg Garcia
    ZACH Theatre
    Senior Ticketing Services Manager

Reply
  • Our work-around has been working really well for us!

    When we realize an address in Tessitura is incorrect, we update the primary address to read:
    Needs Address
    Austin, TX 99999

    The "Needs Address" is an easy visual flag for users to update addresses whenever pulling up an account for any transactions. And the "99999" zipcode is an easy suppression in Extraction Manager.

    Greg Garcia
    ZACH Theatre
    Senior Ticketing Services Manager

Children
  • We use the 9999 Unknown framework and bad address types too. I run the Manage Attribute utility nightly as a scheduled job to update anyone with an unknown or bad address to have a control-grouped Invalid Address attribute, which makes suppression in list manager a piece of cake. Every so often, I'll review the patrons with the Invalid Address attrbute to see if it should be removed (someone else in the consortium updated the address or our staff forgot to remove it when updating the address).