Non-Profit Metrics: Boost Impact with Salesforce in 2026

If you don’t know what your donors and beneficiaries actually think, you’re flying blind on both impact and funding. Good customer satisfaction measurement gives you real data to work with, making sure your programs are connecting with the people you serve and that your supporters feel heard. The problem for most non-profits is they’re already stretched thin, so how do you actually capture this feedback and turn it into real change without a huge budget?

Step 1: Setting Up Your Feedback Infrastructure in Salesforce for Nonprofits

Most non-profits I work with are already on Salesforce for Nonprofits (NPSP) to manage their contacts. It’s a platform where you can build a pretty sophisticated feedback collection system, going way beyond just sending one-off emails. The first real step is configuring NPSP to grab satisfaction data methodically.

1.1. Defining Key Metrics and Survey Triggers

Before you build a single thing in Salesforce, you have to decide what you’re actually trying to measure. For most non-profits, this boils down to two main metrics: Net Promoter Score (NPS) and Constituent Satisfaction Score (CSAT). NPS is your loyalty metric, asking that “How likely are you to recommend…” question on a 0-10 scale to see who your biggest fans are. CSAT is for immediate, in-the-moment feedback on a specific interaction, typically on a 1-5 scale. You also need to pinpoint the moments that matter most for getting this feedback. Think about touchpoints like:

• Right after a donation is confirmed.
• After someone attends a program or event.
• When a beneficiary finishes a service cycle.
• Once a year, to check the overall health of the relationship.

In Salesforce, you’ll go to Setup > Object Manager to create the fields to hold this data. I usually add custom fields to the “Contact” object itself or, for more complex setups, to a separate custom “Feedback” object. You’ll want to create a new field like “NPS Score” (Number, 0-10) and another for “CSAT Score” (Number, 1-5). Getting this data into a central spot is what makes decent reporting possible later.

1.2. Integrating Survey Tools with Salesforce

Salesforce is built to integrate with other tools. While you could technically build your own survey forms with Salesforce Flow, it’s usually not worth the effort when most non-profits can get great results from dedicated survey tools that plug right in. SurveyMonkey and Qualtrics are solid choices, and their non-profit pricing tiers are often very reasonable. For this walkthrough, we’ll just assume you’re using SurveyMonkey since it’s everywhere.

Inside your SurveyMonkey account, find the Integrations > Salesforce section and authorize the connection to your Salesforce org. The next part is critical: you have to map your survey questions to the custom Salesforce fields you just made. So, your NPS question in the survey gets mapped to the “NPS Score” field on the Contact object. Even more important, you must pass the Salesforce Contact ID or Lead ID from Salesforce into the survey as a custom variable. This is what lets SurveyMonkey know which specific record in Salesforce to update when someone submits a response. If you don’t use that unique identifier, your data ends up siloed and almost useless, a common mistake that I see all the time.

1.3. Automating Survey Distribution via Salesforce Flows

Sending surveys manually is a huge time-sink and you’re guaranteed to make errors. Use Salesforce Flows to automate the whole process. Go to Setup > Flows and create a new “Record-Triggered Flow”.

1. Choose Object: Pick the object that kicks off the survey. If you’re surveying after a donation, it’s probably the “Opportunity” object. For a program interaction, it might be a custom object you’ve built, like “Program Enrollment”.
2. Configure Trigger: Set this to fire when “A record is created or updated”. Then add specific entry conditions. For example, to send a survey after a donation, you’d set the condition to StageName Equals "Closed Won" and maybe RecordType.Name Equals "Donation".
3. Add a “Get Records” Element: You need this step to pull the right Contact record so you can get their email address.
4. Add a “Send Email” Element: This is where the magic happens. You can build an email template in Salesforce (Setup > Email Templates) that includes the contact’s email and a link to your SurveyMonkey survey. Make sure you append the Contact ID to the survey URL as a parameter (something like https://www.surveymonkey.com/r/YourSurveyID?c_id={!$Record.Contact.Id}). This is how you pass the ID to SurveyMonkey so it knows which record to update.
5. Add a “Pause” Element (Optional but Recommended): For some feedback, like after a service is completed, it’s a good idea to wait a day or two before sending the survey, giving the person time to actually reflect on the experience.

Pro Tip: You have to implement a frequency cap. Don’t bombard people with surveys. Add a custom date field on the Contact object like “Last Survey Sent Date” and then add a condition to your flow so it won’t send a survey if that date is within the last 90 days. Doing this respects people’s time and, just as important, prevents the survey fatigue that can seriously skew your results.

Step 2: Building Customer Satisfaction Dashboards and Reports in Salesforce

Getting the data is just step one. You have to visualize it to spot trends and explain your impact to your board and funders, and Salesforce’s reporting and dashboard capabilities are useful for exactly this.

2.1. Creating Custom Report Types for Feedback Data

You might need a custom report type before you can build anything, especially if your feedback data lives on a custom object that isn’t cleanly linked to your Contacts. Go to Setup > Report Types and create a new one. Just select your main object (like “Contacts”) and then link it to your custom “Feedback” object. This way, you can report on contact details right alongside their survey responses.

2.2. Designing Key Performance Indicator (KPI) Reports

Now, let’s build the actual reports that will populate your dashboard. Head over to Reports > New Report.

1. NPS Trend Report:
   • Report Type: Use your “Contacts with Feedback” custom report type.
   • Columns: “Contact Name”, “NPS Score”, “Feedback Date”.
   • Group Rows By: “Feedback Date” (group it by calendar month or quarter).
   • Summarize: Add a summary formula to calculate NPS. The formula is (COUNT_DISTINCT(IF(NPS_Score__c >= 9, Contact.Id, NULL)) - COUNT_DISTINCT(IF(NPS_Score__c <= 6, Contact.Id, NULL))) / COUNT_DISTINCT(Contact.Id) * 100. This is just the standard (% Promoters - % Detractors) calculation.
   • Filter: Filter the "Feedback Date" to something reasonable like "Current and Previous Year".
2. CSAT by Program Report:
   • Report Type: Same "Contacts with Feedback" type.
   • Columns: "Contact Name", "CSAT Score", and "Program Name" (assuming you capture this).
   • Group Rows By: "Program Name".
   • Summarize: Add a simple summary formula for the average CSAT: AVG(CSAT_Score__c).
   • Filter: Set the "Feedback Date" for the last 90 days.
3. Open-Ended Feedback Report:
   • Report Type: "Contacts with Feedback".
   • Columns: "Contact Name", your "Open Text Feedback" field, and "Feedback Date".
   • Filter: Make sure "Open Text Feedback" is NOT EQUAL TO "" so you only see records with actual comments. This qualitative data is where you find out *why* the scores are what they are. Don't skip it.

2.3. Assembling the Satisfaction Dashboard

Now you pull it all together on a dashboard. Go to Dashboards > New Dashboard and start dragging components onto the page.

• NPS Trend: Use a Line Chart component with your NPS Trend Report. Put "Feedback Date (Month)" on the X-axis and your NPS formula on the Y-axis. This will show you the loyalty trend over time.
• CSAT by Program: A Bar Chart works well here. Use your CSAT by Program Report, with "Program Name" on the X-axis and "Average CSAT Score" on the Y-axis. This immediately shows which programs are doing well and which might have issues.
• Recent Open Feedback: Use a Table component and point it at your Open-Ended Feedback Report. Show the contact's name, their comment, and the date. I like to show the last 10-20 comments to keep these qualitative insights visible.
• Overall Satisfaction Gauge: A Gauge component is a nice touch for showing the current month's average CSAT score at a glance. You can set color-coded thresholds (e.g., Red below 3.5, Yellow 3.5-4.2, Green above 4.2).

Common Mistake: Don't make the classic mistake of overloading the dashboard with every metric you can think of. A cluttered dashboard gets ignored. I always recommend focusing on the 3-5 most critical indicators that you actually use to make decisions, which for me are usually the NPS trend, CSAT broken down by program, and a feed of the latest comments. You can always drill down for more detail from there.

Step 3: Acting on Feedback and Closing the Loop

All this data is useless if you don't do anything with it. The whole point of measuring customer satisfaction is to use what you learn to make your services and donor relations better. That means you need a process for actually reviewing the feedback and, just as important, for responding to it.

3.1. Establishing a Feedback Review Cadence

Get a recurring meeting on the calendar (weekly is great, bi-weekly works too) with your program managers and fundraising team to go over the satisfaction dashboard. In those meetings, you should be focused on a few things:

• Trend Analysis: Are the NPS or CSAT scores going up or down? Can you connect any of those movements to specific events or changes you made in a program?
• Identifying Outliers: Are there specific programs or interactions that are consistently getting terrible scores? Why?
• Qualitative Deep Dive: Read the latest open-ended comments out loud. You're looking for themes, specific complaints, or even surprising praise. If you have thousands of comments, a tool like MonkeyLearn can help with text analysis, but honestly, for most non-profits, a manual review gives you a much better, more nuanced feel for what's going on.

Editorial Aside: Don't just focus on the bad stuff. Your positive feedback tells you exactly what's working and where you should double down. Celebrating those wins with your team is great for morale and reinforces what good looks like.

3.2. Implementing Automated Follow-Up Workflows for Dissatisfied Constituents

You have to follow up on low scores immediately (I'm talking NPS of 0-6 or CSAT of 1-2). It shows people you're actually listening and are serious about fixing problems. Salesforce Flows can automate this.

Create another Record-Triggered Flow:

1. Trigger: When a "Feedback" record is created or updated.
2. Condition: NPS_Score__c <= 6 OR CSAT_Score__c <= 2.
3. Action: "Create Task". Assign it to the right person, like the program manager or donor relations officer. Make the subject something clear like "Follow-up required: Dissatisfied Constituent" and pull details from the feedback record into the description (e.g., "Contact Name: {!$Record.Contact.Name}, Reason: {!$Record.Open_Text_Feedback__c}"). Set the due date for 24-48 hours out.
4. Action (Optional): You can also have it "Send Email Alert" to the manager so they know a new task is in their queue.

This simple automation ensures no one with a bad experience gets ignored. The point isn't just to solve one person's issue, but to spot the systemic problems that are causing the dissatisfaction in the first place.

3.3. Closing the Loop and Communicating Changes

After you act on the feedback, you need to tell people about it. If someone was unhappy and gave you their contact info, have a real person reach out to them. Explain what you've done or are planning to do based on what they said. That single human interaction can turn someone who was angry into a loyal supporter. For bigger trends you've addressed, talk about it publicly. If you got a lot of feedback that program information was hard to find and you redesigned part of your website, mention that in your next newsletter. A simple "Because you told us..." is a powerful way to build trust.

Measuring customer satisfaction in a non-profit is a constant cycle of listening, learning, and changing. By using Salesforce to methodically collect feedback, visualize the important metrics, and build workflows to act on what you learn, you can make sure your work is actually hitting the mark with the people you serve and the people who fund you.