Gift processing in On-Line Express

Options
We recently conducted a campaign to young alumni using social media (including Givalanche).  The happy result is that, because of social media connections, some of our "lost" young alumni (i.e., those with no valid address on file) were contacted and gave.  But a problem arose...  If an alumnus who was flagged as "no valid addresses" made a gift, we process that gift and capture that new address. But at no point in the OLX gift processing do we get a notification that this alumnus is flagged as "no valid addresses."  The result?  We now have a correct address on file for this young alum, but he is STILL marked as "no valid addresses."  We have to do an extra step of querying to find these folks and fix this.  


Is there a setting somewhere (perhaps in Batch?) that would generate a notification when adding a gift to a record marked "no valid addresses"?  If not, shouldn't there be?  
Tagged:

Comments

  • Maybe someone else will chime in with a better answer, but Annotations come to mind as a possible solution. If you add an Annotation to the records of all Constituents with an invalid address, you can then set up Batch to notify you that a given record has an Annotation. It won't automatically bring up the Annotation, and you'd still need to open the record to verify what the Annotation says, but it's a start. Getting the Annotations set up on all of the required Constituents would be a bit of a project, but maybe it would be worth it.


    Here's a link to a KB article on how to set up the Business Rule to let you know in Batch when a Constituent has an Annotation:


    https://kb.blackbaud.com/articles/Article/52830
  • It's a good point to bring up. I think the best way to handle this would be by creating another daily "maintenance" query, to check for any "Invalid Address" constituents who have made a gift in the past day/week. You know, to run along with all the other data maintenance queries like "Invalid Address and Send Mail is still checked" or "Deceased yet still receiving newsletters" .... etc.
  • We use a business rule to indicate when a record has 'no valid' address.  This works better than annotation as you can have an annotation for anything, whereas the business rule can be setup specifically for no valid addresses.
  • Thanks, Tina.  That is the best answer.  Should have thought of that myself!  
  • Actually, in testing this, we find that it does not work.  It works in regular batches, but not in OLX batches.  In a regular batch, when you first enter the constituent name or ID into the next open line in the batch, the business rule is applied and a warning pops up.  But with OLX, the batch is automatically populated with all the names, and the business rule does not seem to work.  Am I missing something?

Categories