Mail Preference and Solicit Code Overrides
I am in the midst of a solicit code and communication preferences clean up. My organization currently tracks both solicit codes (opt-out preferences) and mail codes (opt-in preferences) through attributes. When I started, my organization found that the Solicit Code field did not allow for enough information to be captured, such as date of add and comments on why the solicit code was being added and so the move was made to attributes. Now, the solicit codes and mail codes lists seem to have grown somewhat unchecked. We have codes that only pertain to each event and mail/email list that are quite specific (opt-in/out of each of our appeal mailings and emails, opt-in/out of each of our corporate partners/donors/annual report newsletter mailings and emails, opt-in/out of each of our galas and stewardship event invites by mail and email etc.). What are some top level codes that your organizations have used for opt-in or opt-out preferences? I know that a lot of it depends on the organization but I'm trying to get a sense of what a more manageable list of codes would be.
Our list of codes has also led to confusion on which codes take priority. For example, if someone opts-out of all paper mail, but then requests just the Holiday mailing every year or still likes to receive the donor newsletter by mail, how have you coded something like this where one code needs to override another? Or I suppose alternatively, how have you set up queries for mailing lists to account for donors that don't want paper mail, except for X mailing each year?