nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Do Not Solicit Constituent Code

Jennifer Menon

I was wondering if anyone has added a Do Not Solicit Constituent Code. I am trying to weigh the pros and cons about it. I am leaning towards doing it I just was curious if anyone else has done it and how it worked out. Thanks for the information!

Jennifer

Find more posts tagged with

RaisersEdge7 Databaseview

Comments

Dariel Dixon

What would be the main goal of this? Isn't there already a dedicated place for these codes? I'm never a fan of adding codes, and this case may seem to be redundant.

JoAnn Strommen

So agree with Dariel Dixon‍. What would be your purpose for recording it there? What do you gain? Why are you not satisfied with having it as a solicit code?

Crystal Bruce

Discussion moved to Raiser's Edge Forums. Thanks!

Jennifer Menon

I don't want these people to come up in any pulls because if we have an oversight and send to them it could be a problem. I would prefer to have a solid way to avoid pulling them for appeals. This would also make it easy to see who doesn't want to be solicited if anyone ever wanted to see that for some reason.

JoAnn Strommen

My concern would be that if you pull by one of your main constituent codes, It's the same amount of work to pull in a second criteria of CC does not equal Do Not Solicit as it would be to pull Solicit Code into your query criteria. It's a matter of training staff to always include/review solicit code data when pulling data. Oversight can happen either way.

You say "so it's easy to see." So is solicit code (thinking db view). Solicit Code displays right above where you can have Constit Code display on Bio 1. I'm not referring to Consent button which is an entirely different discussion.

I've found it's generally best to stick to original RE intended structure. CCode is why is this record in db/why does this record matter to me and SolicitCode is person's preferences for communication. This has proven to be true as they add things like other modules and NXT.

Dan Snyder

Just chiming in to add to what Dariel Dixon‍ and JoAnn Strommen‍ have mentioned to say that even in NXT this code can be "easy to see" as you can adjust your settings so that the Do Not Solicit solicit code (or any solicit codes you select) will display in a blue bar at the top of the constituent record.

JoAnn Strommen

Dan Snyder‍ - I have the NXT blue bar. Is the blue bar a default and user just choose which codes? Would it display for all our users? How/where are the options for set-up? I want to be sure all users who need this info are seeing it.

I can look in KB, but thought I'd ask to see if you or someone else knows.

Dariel Dixon

JoAnn Strommen‍ You would have to click on the gear on the solicit codes box for set up an alert for the codes you want to have displayed. I totally did not know about this, but that makes so much sense. I'm not sure if you can set it for all users, or if it's user specific.

Thanks for the great idea Dan Snyder‍.

Dan Snyder

JoAnn Strommen‍ and Dariel Dixon‍ those settings are system wide and can only be set by an admin. To set them, click on the gear icon in the upper right hand corner of the Solicit code tile in NXT and you can select what codes are displayed.

Here is the Help topic for official BB instructions.

JoAnn Strommen

Thanks for the info and BB link. As I'm doing db cleanup and getting our consent recording restructured I will definitely need to update this as well.

Great to know. Another example of why these forums are so valuable.

Karen Diener

I would definitely advise against adding this as a constituent code. That code is intended to answer the question "why is this person / organization in my database". Solicit codes explain how to solicit them - or not. You can easily include the solicit code in queries, exports, report, etc. and can easily seem them in database view as well as webview.

This is more of a training issue for your staff than anything else.

Karen

Donna Hren

I would agree with the others and not put it as a constituent code. It is a solicit code and is easy to remove those people from mailings/appeals. With every appeal we send out, subtracting those with that code, is a part of the process for us.

Christine Cooke

Another chime. There are ways to guarantee they do not come into list you pull. On the regular folks use Solicit Codes and Attributes for this purpose. The other layer to this is to mark their record accordingly in regard to their contact info - unchecking Send Mail to this Address, either utilizing Do Not Contact button or relocating their phone number(s) and email(s) to notes or somewhere else in your DB consistently and documented.

If this information on procedure is documented and the entry is consistent - two of my favorite words - then they will not show up in lists for contact.

Joe Moretti

@Jennifer Menon There are reasons why everything should be in it's appropriate place, Last Name on the Last Name Field, Mr. on the Title field, Jr. on the suffix field, solicitation codes on the solicitation fields. When you start putting things where they do not belong, you create a messy database, which like others on here have seen time and time again and wonder “what were they thinking”. You don't put your silverware in the tool box and your tools in the silverware drawer.