Hello Everyone! Here is our Q&A from today's (Aug. 20th) AMER AMA thank you to our hosts @Cassidy Schulze @Bamlak Haile and our AMA Lead @Rob OBrien!
Q: What are real-world use cases for implementing Agentforce at a small nonprofit?
A: Agentforce can help nonprofits of all sizes improve efficiency and impact. Common uses include:
- Automating donor or volunteer support with AI-driven chatbots.
- Assisting staff with quick knowledge retrieval, reducing time spent searching for answers.
- Streamlining intake processes for program applications.
- Supporting fundraising teams with donor insights and suggestions.
📖 Read recent examples of nonprofits using AI
💡 Join the AI Education & Agentforce Design Workshop (free, open to all) on Oct 2: Register here
Q: How do I set up and share Trail Tracker with staff for training?
A: After enabling the sync job, you’ll need to:
- Install Trail Tracker from the AppExchange.
- Assign the permission set to users.
- Share the app with employees so they can see assigned trails, badges, and progress.
Q: We’re considering Accounting Subledger for journal entries, but are concerned about Data Processing Engine’s (DPE) 30-hour monthly processing time limit. How can we mitigate usage risk?
A: DPE limits are based on volume and complexity of data. To optimize:
- Keep dimensions and mappings as simple as possible.
- Batch data in smaller runs to reduce peak processing loads.
- Monitor processing usage early to adjust design before scale-up.
📖 Subledger & DPE limits documentation.
Q: In NPSP, how do you manage acknowledgment status for Opportunities with multiple payments? Also, what should the Close Date be?
A:
- For multi-payment Opportunities, some orgs create custom record types (e.g., “Multi-Payment Gifts”) so acknowledgment can be tracked at the Payment level rather than only at the Opportunity.
- For Close Date: best practice is to use the date of the final expected payment, but you can create a process/field to reflect when the first payment is anticipated if that better fits reporting.
Q: Our users want to edit each other’s Notes, but only the note owner can edit. Any workarounds?
A:
- Classic: Notes sharing allows collaborators to edit.
- Lightning: Sharing only grants view access. Editing by multiple users isn’t supported out-of-the-box.
- Advanced option: Developers can use a trigger on ContentDocumentLink to allow editing if a user has access to the related record.
⚠️ Be cautious: Notes don’t support simultaneous editing, so add fields like Last Edited By and Last Edited Date to track changes.
Q: Our nonprofit collects program applications via Adobe forms → Excel → manual emails. How can we move this directly into Salesforce?
A:
- Web-to-Lead can capture basic submissions.
- Experience Cloud allows branded portals for applications and status tracking.
- Third-party form tools (FormAssembly, Formstack, Jotform, etc.) integrate directly with Salesforce objects for automation.
📖 Community discussion on forms
Q: We use NPSP and want to report on Payments “Acknowledged / To Be Acknowledged” separately from Opportunities. Any tips?
A:
- Ensure your Integration User has the correct Fundraising Permission Set so data flows correctly.
- Build reports directly on the Payment object with acknowledgement fields, separate from Opportunities.
- For advanced issues, post in the Partner Community for tailored guidance.
Q: We use NPSP and want to report on Payments “Acknowledged / To Be Acknowledged” separately from Opportunities. Any tips?
A:
- Ensure your Integration User has the correct Fundraising Permission Set so data flows correctly.
- Build reports directly on the Payment object with acknowledgement fields, separate from Opportunities.
- For advanced issues, post in the Partner Community for tailored guidance.
Q: We use Outbound Funds Module. When should disbursements be entered, and how do we distinguish them from payments?
A:
- Best practice: Enter disbursements only once funding requests are approved. This keeps your pipeline clear and reports accurate.
- Disbursements = commitments of funds; Payments = actual transfers made. Reporting should separate the two.
- To audit what your predecessor automated, check for Flows, Process Builder, or Apex jobs tied to funding request objects.
📖 OFM resources on Trailhead & Help Docs
Q: What are good ways to document Profiles and Permission Sets?
A:
- Use Custom Report Types to capture object/field permissions.
- Export metadata using tools like Config Workbook (free, generates detailed permission reports).
- Consider vetted AppExchange apps if your org allows third-party solutions.
📖 Helpful links:
Q: How can Data Cloud be used by nonprofits, especially in museum/venue settings?
A:
Key use cases:
- Unified visitor & donor profiles — combine data from ticketing, membership, POS, events, and donations for a 360° view.
- Personalized engagement — segment audiences to send tailored campaigns, offers, or exhibit recommendations.
- Fundraising optimization — identify high-value donors, predict giving patterns, and improve retention with automated journeys.
- Operational efficiency — break down data silos, automate workflows, and create real-time dashboards.
- Enhanced visitor experience — personalize digital touchpoints (website/app), streamline ticketing & membership, and offer dynamic recommendations.
