#SprintIdea0 debatiendo

I'm looking for input toward a comprehensive resource for helping organizations clean up their donation coding and keeping it clean going forward - particularly in regard to Organizational Giving. I'll post here all the resources I've found, and the pieces I've begun to create. (These NPSP practices are in many cases *adding* records, rather than changing data.)

One of the needs that prompted this inquiry is: an easy way to filter for all givers, whether they give directly or through an Organization (such as via a Donor Advised Fund) in a list view so we can use "Send List Email."

I'm interested in knowing how you have approached all of this with the NPSP:

• What "Account Record Types" do you have?
• What "Related Opportunity Contact Roles" do you have on Affiliation Records?
• What "Roles" do yo have on Affiliation records?
• Do you use a consistent Household Account model or a hybrid and why?
• What automation or other measures have you put in place to keep things consistent?
• What is important to your development staff in terms of constituent and donation coding?

Here are some steps to consider:

• Considering whether to use a strict or hybrid Household Account model: Salesforce/NPSP recommends a consistent practice of putting ALL Contacts in their own Household Accounts, and using Affiliations to connect them to Organizations. Many nonprofits use a "hybrid" model, where those Contact that they have a personal relationship with as individuals are in their own Household, whereas Contacts that they only have a relationship with through their organization live directly on the Organization Account. (The relationship between Contact and Account is shown in the attached diagram in fuscia - Contacts can be directly related either to a Household Account OR an Organization Account). Here are pros and cons as I currently see them:
  • Argument FOR strict Household Model: Consistency is probably good. Organizational givers are found in one way (via Affiliation/Contact Role), rather than two (Contacts who are directly related to Organization Account and Contacts in Households via Affiliation/Contact Role).
  • Possible arguments FOR hybrid model: if we only know someone because of their connection to an Organization, it's more intuitive to add them directly to the Organization account. In order to use a consistent Household model, staff need to be trained and/or systems need to be in place so that all Contacts are created in Households and Affiliated to Organization Accounts. When a Contact is no longer affiliated with an Organization account (e.g., leaves that job or leaves that board of directors), decide whether to remove the Affiliation (and specify the former relationship somehow?) or remove the Contact/Household from Salesforce altogether.

• Deciding on the best way to establish the relationship between Contacts who give via a vehicle such as a Donor Advised Fund. Should the Accounts have Account Record Type=Organization and Type=Donor Advised Fund? What should the Opportunity Contact Role be (Decision Maker? Other?) Changing coding on Account, Contact, Opportunity, Affiliation, and Opportunity Contact Roles accordingly.

• Adding a "Primary Affiliation" on each Contact's record as appropriate (only one, which is also added as an Organization Affiliation record)

• Adding any additional Affiliation records (can be > 1) in the Affiliation object, which connect Contacts to Organizations - we need to add these for both partners in a household, if we want both partners to come up in lists for emailing.

• Specifying the "Related Opportunity Contact Role" in the Affiliation records - then the Contact will automatically have that Contact Role (Soft Credit, if applicable) whenever a Opportunity is entered on the Organization

• Making sure there is a Primary Contact on each Organization, whenever possible. This enables:
  • any new Opportunity created on the Organization to automatically have the Organization's Primary Contact as the Opportunity's Primary Contact
  • Contacts in Households to automatically get a soft credit for new Opportunities created on the Organization Account

• Standardizing whether opportunities are entered on Household Contacts or Household Accounts?

• For existing Opportunities, making sure all relevant Contacts have "Opportunity Contact Role" records, as appropriate. These records connect Opportunities to Contacts and give soft credit to Contacts if the Opportunity Contact Role is specified in NPSP settings to be given soft credit.

• Enabling Customizable Rollups, which allows us to create additional useful rollups, including rolling up all soft credits from all Contacts in a Household up to the Household Account.

Resources:

NPSP Videos: Here are some short NPSP videos on these topics:

• Organization Affiliations: https://www.youtube.com/watch?v=lqg0pgpjOcg&t=21s
• Organizational Primary Contact: https://www.youtube.com/watch?v=BZRZXRyeEI8

(notes that "Primary Contact" person on an Organization is unrelated to the "Primary"

checkbox on an Affiliation record)

• Soft Credits: https://www.youtube.com/watch?v=6HwFzj1MXZk

(create Contact Roles to give soft credit, rollups are calculated overnight in a batch)

• Automatic Soft Credits: https://www.youtube.com/watch?v=_mG8g_V3XO4

(title says "Relationship", but video discusses auto soft credits via both Affiliations and Relationships; shows how the affiliation and "Related Opportunity Contact Role" must be set for each Contact to be soft credited-even if they're in the same household, "Getting all of this right is important. Donors with more complex needs will expect that you are representing their family, businesses, associates, and financial institutions correctly and that your organization is crediting the right people for the donations they help to bring in." Also there is a hierarchy for when a Contact is credited by multiple methods at the same time)

•  Account Soft Credits: https://www.youtube.com/watch?v=F9yJzfR4dLE&t=1s

(notes can be used for DAF-bank OR employee giving/matching Opportunities through an aggregator)

Documentation:

These articles from the NPSP documentation explain how the NPSP's Household Account model intends for Contacts to be in their own households and Affiliated with Organizations, such as Family Funds.

• https://powerofus.force.com/s/article/NPSP-Add-and-Manage-Organization-Accounts
• https://powerofus.force.com/s/article/NPSP-Create-an-Affiliation-with-an-Organization
• https://powerofus.force.com/s/article/NPSP-Add-a-Single-Payment-Donation

Trailhead:

This Trailhead Module has useful information: Donation Soft Credit Management with Nonprofit Success Pack: https://trailhead.salesforce.com/en/content/learn/modules/donation-soft-credit-management-with-nonprofit-success-pack/manage-contact-roles-and-soft-credits

The first unit mentions "Customizable Rollups." "If you're using customizable rollups, your admin can add even more soft credit rollups, including rollups that aggregate soft credits for all contacts in a household and roll them up to the household account, as needed."

Other articles:

Managing Donations With Multiple Entities In Salesforce by Joel Salazar for Plativ:

https://www.plative.com/ask-an-expert-managing-donations-with-multiple-entities-in-salesforce/

Modify Engagement Plan Templates to work backward from a specified future date

Hi all—just wanted to share this tip as I know the inability of "stock" Engagement Plan Templates to work backward from a future date is something that kept me from using them for a long time, and I think is an issue other folks on the Hub run into as well. Our need for this feature eventually got to the point where I just decided to think it through, and it was actually pretty easy to set up declaratively and is *almost* as easy to use as the standard process for setting up a plan.

1. Create a custom date field "Final Date" on the Engagement Plan Template object and add to layout
2. Create a custom number field "Days Before" on the Engagement Plan Task object and add to layout
3. Create a (or modify your existing) Process that's triggered when a Task is created *edited to add both sets of criteria so the process won't fail if a non-EP Task is created*
   1. Criteria to meet: Task > Engagement Plan Task is not null, AND Task > Engagement Plan Template is not null
   2. Action to take if met: Update the Task that triggered the process and set the due date to Engagement Plan "Final Date" minus Engagement Plan Task "Days Before" value if there is a "Days Before" value specified. Here's the formula: IF(NOT(ISBLANK([Task].npsp__Engagement_Plan_Task__c.Days_Before__c )),[Task].npsp__Engagement_Plan__c.Finish_Date__c - [Task].npsp__Engagement_Plan_Task__c.Days_Before__c ,
      [Task].ActivityDate )

4. Set up an Engagement Plan Template as you normally would, and leave "Days After" blank for any Tasks you want to set based on a future date. Once it's done, open up that template's record, and look at the related list for the Engagement Plan Tasks you want to update. Edit these records to add your preferred "Days Before" value. It's one step more complicated than using the visualforce page, but really very straightforward.
5. Create a new Engagement Plan, and make sure to set a "Finish Date" value.
6. When the Tasks are automatically created, Process Builder checks to see if they are related to an Engagement Plan Task with a value in "Days Before," and then updates the due date based on that value and the "Finish Date" value of the Engagement Plan

Notes:

• I haven't thoroughly tested this or played around to see how dependent Tasks are handled
• I suspect if you use email alerts when the tasks are created they'll have the old value (TODAY if left blank) rather than the value defined in Process Builder
• This might be a cool #SprintIdea to implement a little more robustly and include a "days before" value in the VF page...
• #PUBCrawlTip