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 invite list

Stephanie Hale

I have a constituent that we need to ensure they DO NOT receive any invitations from us. Does anyone know how we can do that? My best guess is to add a solicit code, but unless we remember to filter out the code while making a list, they will receive an invite. Any suggestions?

Find more posts tagged with

Events

Comments

Damon Rosenthal

@Stephanie Hale
Solicit Code is the way to go. Unless there are other ideas, it sounds like you need to consider changing your processes to include review of “exclusions” and “inclusions” (based on its purpose) in the preparation of lists. The other suggestion is put a note within a key data item necessary in your process to sending invitations. (A manual update maybe to correct for other purposes, but will ensure you don't send invitations. We do this for deceased records to limit the risk of us from accidently sending out something to deceased.) Hope this is helpful!

Austen Brown

@Stephanie Hale - Agree with Damon's assessment. I recommend you create a Standard Exclusions Document. That clearly defines the types of communication lists your department pulls and what codes on a record need to be excluded from the list. That way, you have a central document to reference anyone time someone pulls a list and everyone in your org is on the same page for who is excluded in any given scenario.

For example: “Mailed Solicitations”, anyone with these codes/tags are excluded from the final list

Solicit Code: Do Not Mail
Solicit Code: Do Not Solicit
No Valid Address
Inactive
Deceased
Donors with an active recurring gift
Donors with an open pledge

Dariel Dixon

@Stephanie Hale: If you're not already filtering on solicit codes, you should start now. Like @Austen Brown stated, you should have a list of codes that get excluded from certain things. At some point it will become second nature.

My best guess is to add a solicit code, but unless we remember to filter out the code while making a list, they will receive an invite. Any suggestions?

Jacqueline Sovde

@Stephanie Hale We set up a Solicit Code “RESTRICTED ACCESS” [date + 100], tagged the record Inactive, DNC, No Email, No Valid Address, and just for good measure added a notation that pops up when the record is opened which says something like “Restricted and Confidential Status as of [date]. See record note for additional information.” The record never pops up in a pull.

Jenny McCumiskey

@Stephanie Hale
We have a query built that houses all the codes for people that we want to exclude from our lists. We call it "UA - Event Mailing Invite Rules". ("UA" is for University Advancement.) We also have one for email invites. That way when someone is making a mailing (email) database for invites they can just merge that query with theirs and they can be sure they excluded everyone they needed to. It has been very helpful to not have to rely on memory and reduce human error.