Constituent Codes

Options
Currently in my organization, we have donor surveys that inquire when individuals would like to be solicited for our appeals. There is a constituent code for "solicit one time per year" however is there a way to note when these individuals would like to be solicited and run as a query? 

I understand this can be placed in notes, but is there a way to make the data more readily available? 

Comments

  • Great! I am new to RE and that is what I mean- a "solicit code" although there does not seem to be an option for creating a new attribute other than the ones that are listed, is this a possibility? 
  • JoAnn Strommen
    JoAnn Strommen ✭✭✭✭✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic
    Yes, you can create new attributes. It's done in Configuration. You may need user rights for some functions - don't recall if this is one.  Go the the knowledgebase for help on creating attribute, creating a table (new table is option at bottom of drop down list). Think that's the best place to start.


    Link to knowledgebase:
    https://search.blackbaud.com/#t=All&f:@hproduct=[Raiser%27s%20Edge%7CRE%20Mobile%20App,Raiser%27s%20Edge%7CRE%3A%20Anywhere,Raiser%27s%20Edge%7CRaiser%27s%20Edge%20Event%20App%20for%20iPad,Raiser%27s%20Edge%7CCrystal%20Reports]
  • Lindsey Hemmerlein:

    Great! I am new to RE and that is what I mean- a "solicit code" although there does not seem to be an option for creating a new attribute other than the ones that are listed, is this a possibility? 

    Hi Lindsey,

    If you have supervisor/admin rights you can add an attribute via the Config menu.  If you do not get in touch with your database administrator and they can help you.

    Joanne

  • Melissa Graves:

    If you are using solicit codes I would stick to using solicit codes. Many places use several "solicit once a year" codes. Ones that said "solicit once a year - fall, solicit once a year - winter, solicit once a year - spring". We just excluded fall and winter from the spring mailing, etc.

    I like the idea of seasonal solicit codes. Thanks for that idea!
  • Melissa Graves:

    If you are using solicit codes I would stick to using solicit codes. Many places use several "solicit once a year" codes. Ones that said "solicit once a year - fall, solicit once a year - winter, solicit once a year - spring". We just excluded fall and winter from the spring mailing, etc.

    Yes, that's the easiest way. "Once per year" by itself is just too nebulous to be useful.

  • At a former organization, we had solicit codes that were: 1st Quarter Solicitation Only, 2nd Quarter Solicitation Only, 3rd Quarter Solicitation Only and 4th Quarter Solicitation Only. If their request was as vague as "solicit only once per year," we would choose the current quarter so that they wouldn't get solicited again until next year at that time. We also had people who requested twice per year, so they would be placed on a schedule for alternating quarters (i.e., 1st and 3rd) by selecting both of those solicit codes. The other solicit codes would then be excluded when mailing lists were run.

     

  • We have seasonal solicit codes too - Solicit Once a Year - Spring, Solicit Once a Year - Year End, and so on.
  • Lindsey Hemmerlein:

    Currently in my organization, we have donor surveys that inquire when individuals would like to be solicited for our appeals. There is a constituent code for "solicit one time per year" however is there a way to note when these individuals would like to be solicited and run as a query? 

    I understand this can be placed in notes, but is there a way to make the data more readily available? 

    If I needed to be that specific I would utilize Constituent Attributes
  • Lindsey Hemmerlein:

    Currently in my organization, we have donor surveys that inquire when individuals would like to be solicited for our appeals. There is a constituent code for "solicit one time per year" however is there a way to note when these individuals would like to be solicited and run as a query? 

    I understand this can be placed in notes, but is there a way to make the data more readily available? 

    I agree that if using solicit codes you should keep all the information in one place. If your appeals are always at the same times each year what about a solicit code for each appeal? We send six appeals a year, starting Jaunary and then every second month. Some donors want one appeal a year, but others want two, or three, or four etc. So instead of solcit codes of "Once / twice / three a year" we have solicit codes of "Specific Appeals only: January", "Specific Appeals only: March" etc. Then someone can have multiple codes for two - five appeals a year. They can specify the months or if they do not specify we check their giving history and the time of year they are most likely to make donations. WIth no information our default once a year is our tax appeal, and any more we space evenly through the year.


    When creating my mailing list I merge a query of people with no codes, with one that pulls only the people who have requested that specific appeal and excludes other specific appeal requests.


     

Categories