Fraudulent constituents

Howard Marmorstein:

Just asking how you mark constituent records that turn out to be Fraudulent. We're thinking of a constituent code instead of an attribute.

And then we'll probably have a business rule that will have a message when someone opens the record or possibly attempts to do gift entry (in batch). 

Howard Marmorstein:

We sometimes get online credit card transactions that turns out to be fraudulent - stolen cards, for example. We do create the record for the constituent. We even have checks written from one account that keep getting bounced so we assume they were stolen.

I would definitely make a business rule that gives warning whenever you open the record or enter a gift!

As to whether you use attributes or constituent codes to mark them as fraudulent, I would look at how you use both those codes in normally. Generally, I avoid adding a new const code, since those tend to multiply themselves all too easily. Whether you use an attribute or const code, I would also add a solicit code (or attribute if you use those for solicit codes) of "DO NOT Contact for any reason" - or whatever code your org uses to mark constituents who should never receive any communication.