Hello, Does anyone have experience managing their non member/ non donor mailing list via Raiser's Edge??? If so please contact me..

I am also looking for advice on this exact topic, so if you have found any useful info. pls contact me as well!

We use RE to manage friends of the university who are not donors, but want to be involved in different ways. Is this the scenario you are asking about? If so, what are your questions? Elaine Tucker [Email Removed] Texas Lutheran University

my question is how do you code them and do you give them attributes? Do their constituency codes have dates? If one of them asks to be removed from the mailing list, do you delete the constituent or just mark them as inactive?

We have many records in RE who have a relationship with TLU, but are not donors. I'll use the main group that we have and give examples of their coding. We follow this guideline for all the other groups Constituent Code = Jackson Subscriber Solicit Code = Do Not Solicit, No Phonathon Selected Mail = Cultural Arts Calendar, Jackson Events The only constituents who have begin and end dates on their constituency code are board members. (Reporting gets a little tricky otherwise). If someone asks to be removed from the mailing list we change their record: Solicit Code = Do Not Solicit, No Phonathon, No Mail Send Mail? = NO Add an attribute of Special Mailing type of "No Mail" that has today's date and comment of "Per request of Subscriber". In theory we will mark them as inactive, I'm still training staff in that regard... Normally we would not remove them from the db, because we want to know that they have/had a relationship with the university. If you have further questions that I have not covered by the above example, please let me know. Thanks, Elaine Tucker [Email Removed] Texas Lutheran University

We are looking at mananging our mailing list thru raiser's edge. IE: Tracking interest specific lists, and other information.

If you have the prospect module you can keep interests there. However if you do not I would suggest setting up a constituent attribute table, adding codes to the non-donor records and then maybe creating specific solicit codes for them, ie for our Jackson Subscriber I may create a solicit code for "Events Only". Create a new constituent attribute: Special Interests, base the codes on a table. Then create a new table called Special Interests. Some entries to the table could be generic such as Sports, Literature, etc, or specific Photography, Water Color,. We have an gallery in the fine arts building and during the year we send a notices to those interested the specific type of showing that is occurring, we have those codes as an attribute on the constituent record. The other nice thing about attributes is you can use them to include/exclude from queries and mailings. Hope this makes sense, I feel a little long-winded here LOL. Elaine Elaine Tucker [Email Removed] Texas Lutheran University