"Warn About Potential Matching Gifts" in Preferences

Former Member
Former Member $organization

Hi all,

I'm curious if anyone frequently uses the "Warn About Potential Matching Gifts" checkbox in User Preferences (see the screencap below), and how they've used it. We've been looking for a built-in way to find patrons who could potentially give matching gifts, and I'm wondering if this checkbox functions in this manner or has some other useful qualities. Any and all info is appreciated!

Thanks,

Max Williams

Parents
  • Never checked it off; during gift entry training I have asked staff to review every tab. An employee set up for a match will have that potential match filled in on the Matching/Credit screen so the additional reminder never seemed necessary.

    To find potential matching gifts, in the past I have created lists of non-matching donors/ticket buyers who have e-mail addresses of matching companies (EAddress LIKE "%@tessituranetwork.com") for potential engagement campaigns, but never actually sent anything to them. We didn't affiliate them to their companies, either, but I guess we could have! This can also be used to quantify for corporate sponsors regarding employee discounts/programs/etc.

    -- Mike

  • Mike that is cool.  Your post has got me thinking...  And this is maybe a bit tangential to this thread.  But has anyone else considered creating relationships between individual accounts and corporations based on an individual using their work address to buy tickets and the like?  That is to say, if a individual who works for say IBM.  Uses their @ibm.com email address for a ticket purchase,  Has anyone created or considered automatically creating an employee relationship or even a special “potential employee” relationship for that person back to IBM?

    If I were doing this I imagine I would create an attribute of the corporation that defines the valid domains for that corporation. And then run a job to create the affiliations potential employee relationships. 

    I could see this sort of thing adding information signal to some records that might upgrade get memberships and the like. I also agree that sponsorship groups might also find this useful when arranging and reporting back on employee programs.

Reply
  • Mike that is cool.  Your post has got me thinking...  And this is maybe a bit tangential to this thread.  But has anyone else considered creating relationships between individual accounts and corporations based on an individual using their work address to buy tickets and the like?  That is to say, if a individual who works for say IBM.  Uses their @ibm.com email address for a ticket purchase,  Has anyone created or considered automatically creating an employee relationship or even a special “potential employee” relationship for that person back to IBM?

    If I were doing this I imagine I would create an attribute of the corporation that defines the valid domains for that corporation. And then run a job to create the affiliations potential employee relationships. 

    I could see this sort of thing adding information signal to some records that might upgrade get memberships and the like. I also agree that sponsorship groups might also find this useful when arranging and reporting back on employee programs.

Children
No Data