📌 Nonprofit AMA Recap: Q&A - Weds, Jan 14th 2025

Thank you to everyone who joined our Nonprofit AMA, our first one in 2026! Thank you to our host @Rob O'Brien and co-panelists @Jason Eric Jensen and @Bamlak Haile

 for an awesome AMA.  

Q:  From an admin/dev perspective: When creating Grant Commitments, staff need to see the Charity/Account’s grant guidelines (e.g., which months a charity can receive grants). Today, those guidelines live in a text field on the Account, but users have to navigate back several screens to reference them. What’s the best way to surface this information during Grant Commitment creation?

A: Option 1: Dynamic Forms (Quick Win) 

If your Grant Commitment object uses Dynamic Forms, you can surface parent Account fields directly on the child record page. 

How it works

• In Lightning App Builder → Fields tab
• Drill into the Account (Charity) lookup
• Drag the Guidelines field onto the Grant Commitment page as read-only

Note: This works best on the record detail page, not the initial “New” modal.

Option 2: Related Record Component (Post-Creation Visibility) 

If staff need to reference guidelines after creation without navigating away: 

Setup 

• Create a custom Update Record action on Account with only the Guidelines field.
• On the Grant Commitment Lightning Record Page, add the Related Record component.
• Point it to the Account lookup and select the action.

This keeps key context visible without editing data. 

Option 3: Screen Flow (Recommended for Creation) 

For the best user experience during creation:

• Why Screen Flow works best
• Uses a lookup to select the Charity
• Displays the Charity’s Guidelines in real time on the same screen
• Eliminates back-and-forth navigation

How

• Create a Screen Flow
• Use a Lookup component for Charity (Account)
• Add a Display Text component referencing the selected Account’s Guidelines field
• Enable reactive screen components so the text updates instantly

📘 Grantmaking setup resource: 

https://help.salesforce.com/s/articleView?id=ind.grmk_get_started_with_grantmaking.htm&type=5

🧩 Optional third-party guidance tool: 

https://www.spekit.com/solutions/salesforce

Q: How do I get started with Agentforce for setup?

A: We’ll follow up separately with guidance and next steps once we confirm the appropriate internal path and resources. 

Q: Our annual giving team wants to include new Contact roll-up fields in Marketing Cloud emails. We were told it could be a “major project,” which seems surprising. Is this actually complicated?

A: In most cases, this is fairly straightforward, with some caveats.

When it’s usually simple

• The roll-up field already exists on Contact (or a synced object)
• Marketing Cloud uses Synced Data Sources or a Data Extension you control
• Near-real-time sync isn’t required

What typically changes

• Add a column to the target Data Extension
• Update the SQL query or automation populating it
• Reference the new field in email content

Often this is hours, not weeks.

Where caution is needed

• If the Data Extension is used in existing Journeys
• Any change requires validating that journeys, filters, and decision splits still function correctly

The complexity is usually about impact analysis

, not the field itself. 

Q: What’s the best practice when one stock gift needs to fund multiple opportunities or purposes?

A: Recommended approach:

 Use one Opportunity to represent the stock gift, and allocate it across purposes.

Best-practice pattern (NPSP-aligned)

• One Opportunity for the full gift value
• Allocate using:
  • GAU Allocations for accounting/designations
  • Payments / Payment Schedules if installments are involved
• Use Partial Soft Credits if multiple donors/entities are involved

Why

• Tracks the gift once (clean revenue reporting)
• Allows proper allocation without inflating Opportunity counts
• Aligns with NPSP reporting and accounting practices

Q: We’re moving a multi-step intake process into Screen Flows. Intake staff often need to reference earlier eligibility info as they move forward. What’s the best way to keep key information visible?

A: The goal is preserving context,, not just capturing data. 

Common best practices

• Add a read-only applicant summary (Display Text) on each screen
• Repeat critical eligibility indicators at the top of each step
• Avoid relying on back-navigation
• Optionally include a mid-flow or pre-submit review screen

This keeps flows linear while supporting real-world verification needs. 

Q: How should we handle pledge Opportunities that aren’t truly “lost”?

A: Avoid using Closed Lost unless the pledge is genuinely uncollectible.

Option 1: Close Won - Pledged

Best if finance wants commitments recognized immediately.

• Close as Closed Won – Pledged
• Track installments via Payments
• Report on committed vs. collected revenue

Option 2: Open Pledge Stages (Most Common)

Create stages like:

• Pledged
• Partially Paid
• Fulfilled
• Written Off

Keep Pledged as Open, not Closed Lost. 

Option 3: Closed Lost with “Pledge Lapsed”

Use only when:

• Donor confirms non-payment
• Pledge expires per policy
• Finance writes it off

Add required loss reasons for auditability. 

Q: With Household Accounts enabled, donations through Classy often create duplicate Contacts and Households due to different emails. What’s the best approach?

A: Improve matching rules:

• Include phone + name + email
• Tune deduplication settings in NPSP + Classy
• Use automation or scheduled dedupe jobs
• This reduces manual merges and improves household-level giving accuracy.

Q: Staff want to split one Opportunity across multiple Campaigns. Campaign Influence doesn’t meet the need, and GAUs don’t roll up the way they want. What are the options?

A: Option 1: Custom Campaign Allocation Object (Recommended)

• One Opportunity → many Campaign Allocations
• Clean separation between:
  • GAUs (accounting)
  • Campaigns (credit/performance)

Supports flexible reporting and avoids over-splitting gifts.

Option 2: Split the Opportunity

Only when accounting/legal restrictions differ.

• Heavier operationally
• Inflates Opportunity counts

Option 3: Campaigns for Attribution Only

Policy-based decision:

• GAUs = dollar truth
• Campaigns = influence/engagement

Q: Best practice for householding in NPC: one household per address or per decision-maker? How do you handle multiple adults who give/vol within the some physical house? Any gotchas with either method?

A: There’s no one-size-fits-all answer. This resource covers models, pros/cons, and gotchas:

•  https://docs.google.com/document/d/1MnCwCYw5DdEfYGkHShwb22RtpDfZcdKieA8oETmX0OE/edit

Q: How can someone break into nonprofit or nonprofit consulting without direct experience? Are there remote volunteer options (international)?

A: Getting experience

• VolunteerMatch
• Catchafire (remote, skills-based)
• Hands-on volunteering builds real Salesforce + nonprofit experience

Consulting firms to explore

• Cloud for Good
• Idealist
• Other nonprofit-focused partners

Community resources

• Join the Nonprofit & Education Jobs group on Trailblazer: https://trailhead.salesforce.com/trailblazer-community/groups/0F94S000000kHeISAU

More in comments