Best practice for developing email recipient lists In Raisers Edge for BBNC

Options
Hi there,


We utilise our alumnus constituent code as the means to build querys of recipients for email event invitations.  We then segment the query further as needed. An example of this is a Civil Engineering alumni event where the query segments to alumni who have recieved a degree fromt the Department of Civil Engineering.


We would now like to diversify our email distribution list to include staff and individuals into the query. However, not all of our staff and individuals need to be invited only those with a connection to the Department. Staff could be tracked in relationships under the org record for the Department of Civil Engineering, however an individual (not staff or alum) wouldnt have this option.


What is the best practice to develop a distribution list for scenarios such as this - without manually entering individual ID's to the primary query...








 
Tagged:

Comments

  • Cat Battersby:

    Hi there,


    We utilise our alumnus constituent code as the means to build querys of recipients for email event invitations.  We then segment the query further as needed. An example of this is a Civil Engineering alumni event where the query segments to alumni who have recieved a degree fromt the Department of Civil Engineering.


    We would now like to diversify our email distribution list to include staff and individuals into the query. However, not all of our staff and individuals need to be invited only those with a connection to the Department. Staff could be tracked in relationships under the org record for the Department of Civil Engineering, however an individual (not staff or alum) wouldnt have this option.


    What is the best practice to develop a distribution list for scenarios such as this - without manually entering individual ID's to the primary query...








     

    What about using attributes. We don't like to use constituent codes to break down or qualify constituents too much. Attributes are nice because they are searchable including a date. I work with healthcare foundations so I can't address your situation directly. However, we have donors who give to particular health care facilities and have a focus on certain departments or type of care. That is coded in an attribute.


    Hope this helps.


    Mark Guncheon

    Development IT Analyst

    Bon Secours Richmond Healthcare Foundation

  • Hi Mark. Yes, it seem like attributes is the best way to handle it - just wanted to double check before we launched into it that it is in fact the best way - seems like it is. Thanks for taking the time to respond.
  • Cat Battersby:

    Hi Mark. Yes, it seem like attributes is the best way to handle it - just wanted to double check before we launched into it that it is in fact the best way - seems like it is. Thanks for taking the time to respond.

    Glad I could respond. I find attributes are a great way of storing information because they are everywhere in RE: gift attributes, action attributes, etc.


    Mark

Categories