A national product-philanthropy nonprofit
Disaster-relief donations routed up to three times faster by a resource-matching agent.
A nonprofit receives thousands of truckloads of donated product every year and had to match each one to a partner organisation manually. Its resource-matching agent on Agentforce summarises what arrived, finds the nearby partners who need it, prioritises the communities in greatest need and books the shipment.
At a glance
- Client
- A national product-philanthropy nonprofit
- Engagement
- An operations agent on Nonprofit Cloud
- Sector
- Nonprofit
- Based in
- Virginia, United States
The stack
01
The situation
What they were working against.
Every donation had to be matched by hand to the right partner: what it was, who nearby needed it, and how to get it there. That labour limited how many donations the organisation could accept and distribute, and slowed disaster response when speed mattered most.
02
What was built
The build, in the order it happened.
Summarise and match
The agent summarises donated products and compiles nearby partners that need them, for instance children’s clothing partners for a donation of children’s shoes after a hurricane.
Prioritise by need and distance
Communities with the greatest need first, and the nearest location recommended to cut fuel use.
Book it and tell everyone
Once a partner is selected, the agent updates Nonprofit Cloud records, schedules shipment with third-party transport vendors and emails real-time updates to donor and recipient.
03
The results
The matching team goes back to the front line.
Disaster-affected communities are connected with supplies up to three times faster, the five-person matching team saves more than 1,000 hours a year for frontline response, and the routing logic targets a 20% cut in the organisation’s carbon footprint.
- Faster connection of disaster-affected communities with supplies, up to
- 3×
- Hours a year saved for the five-person matching team
- 1,000+
- Carbon-footprint reduction targeted by routing to the nearest partner
- 20%
Client name withheld. Figures are as reported for this implementation; where one was a stated target rather than a measurement, the label says so.
04
Our read
How we would build this at your scale.
What we take from this build, and what the same outcome looks like for a team of fifty to five hundred people rather than a global enterprise.
Pick the workflow where a human is the bottleneck
Matching is judgement work with clear criteria, which is exactly what an agent can take. For a nonprofit we look for the one process a small team does hundreds of times and start there.
Agentforce & AI 02Nonprofit Cloud holds the record; the agent writes to it
Programmes, partners and outcomes modelled properly are what let the agent update a record instead of sending an email. That model is the first milestone.
Implementation 03Logistics vendors are integrations
Scheduling with third-party transport is an API contract with retries and a fallback. Small nonprofits can do this; it just has to be designed rather than improvised.
IntegrationsMore case studies
A global staffing and talent group
Job-campaign preparation cut by 93%, with an agent that talks to every applicant.
ReadThe advertising business of a major social platform
Advertiser support resolution down from 8.9 minutes to 1.4, an 84% improvement.
ReadA national flag-carrier airline
Refund turnaround cut from about 14 days to about four hours.
ReadWant the same result, without the enterprise bill?
Thirty minutes with an architect. Bring the part of this story that looks like your problem and we will tell you what it takes to get there: which products, how many weeks, and what we would leave out.