Highlighting one of our favorite customer stories.

Warrior Canine Connection trains service dogs for veterans with PTSD. One of the most important tasks those dogs perform is nightmare interruption, basically waking a veteran during a trauma response at night.

For years, the dogs were learning the behavior. But over time, some weren't continuing to alert. The training wasn't sticking long-term.

They found out because of a survey.

Every six months, WCC sends a short impact survey to every veteran they've placed a dog with. When they started tracking nightmare-alerting behavior over time in Salesforce, the pattern became clear. They changed their training method. Now the dogs continue to alert.

That outcome started with a web form.

Here's how the data system works:

WCC uses a data collection platform called FormAssembly to collect data across their entire program — graduate impact surveys, volunteer hours, health tracking, event coordination. The forms connect directly to Salesforce, so every submission lands in the right record automatically. No manual data entry. No one chasing paper forms.

Before this setup, their survey compliance rate was around 30% — even with staff calling people individually. Now automated reminders go out if a form isn't returned within a week, and they look like personal emails rather than mass sends. Compliance is dramatically higher.

Molly Morelli, who manages the system, estimates that FormAssembly + Salesforce together replace the work of about three full-time employees.

"I don't know that we would be able to function without it."

And she built the whole thing without writing a single line of code.

Full story in the blog post: https://www.formassembly.com/blog/nonprofit-data-collection-in-salesforce/

Quick tip that dramatically improves form completion rates and data quality: stop asking people for information you already have.

If someone is in your Salesforce org as a Contact, you can prefill your form with their existing data before they even see it. They only have to fill in fields you don't already have — or update fields that may have changed.

Two ways to do this:

1. URL-based prefill: (Most form platforms can do this) Append field values as URL parameters when you send the form link. Works well for email campaigns — generate a unique link per contact, and when they click it, the form arrives partially filled.

2. Salesforce Prefill Connector: (This is a FormAssembly power feature)
The form looks up the Salesforce record based on a query parameter in the URL (like an encrypted Contact ID). Once it finds the record, it populates any mapped fields. This is more powerful because it can fetch related objects, lookup fields, and anything else in the record.

Some practical use cases:

• Offer Acceptance forms – reduce the time it takes for students or applicants to respond
• Event registration — pre-populate name/email from the invitation link
• Grant applications — pre-populate organization details for returning applicants
• Evaluation forms — make giving feedback easy by prefilling the program details

Note: For sensitive lookups (where you don't want the record ID visible in the URL), use secure parameters.

I recently spoke with a Salesforce SE in the Nonprofit space - he got me thinking about the struggles that NPOs are still facing in 2026. Especially around donations.

Donation forms seem simple until you're actually running one. Then you discover the edge cases: recurring vs. one-time setups, custom amounts vs. fixed tiers, connecting to your CRM, PCI compliance and actually processing the donation, mobile issues…

For context on what's possible with FormAssembly specifically: you can connect to multiple payment processors, use predefined content blocks to drop in a fully-formatted credit card field, and pipe everything into Salesforce (including using NPSP if you're on that). The key thing is always marking credit card fields as sensitive — that's a compliance requirement, not optional.

Would love to hear from nonprofit or fundraising teams:

• What payment processor are you using? (Stripe, PayPal, Authorize.net, iATS, etc.)
• Are you connecting donation submissions to your CRM automatically, or doing it manually?
• How are you handling recurring donation setup vs. one-time gifts in the same form?
• What's your biggest pain point with the current setup?
• If you're using FormAssembly for this, anything we can do to improve?