Church Benevolence Software: Knowing Where to Send People

Church benevolence software answers one question quickly: where do we send this person? It holds a current list of local providers, shows which ones are open right now and how far away they are, and keeps a record of who was helped. That is the whole job. Everything else it does is downstream of getting that first answer right.

CMinLink is a benevolence and referral tool for churches and nonprofits. It is a program of Bridgeway Community Initiatives, Inc., a North Carolina nonprofit, not a commercial CRM adapted for church use.

Why is it hard to know where to send someone?

Churches are often the first place people turn. Someone calls about a utility cutoff, or knocks on the office door with an eviction notice. The person at the desk wants to help and usually has about four minutes to do it.

What they reach for is a printed list, a shared spreadsheet, or a long-serving volunteer’s memory. Each of those fails in the same quiet way:

• The list goes stale. A grant ends, a program closes, hours change, and the entry looks exactly the same as it did when it worked.
• Nobody knows what is open now. Posted hours are not the same as open on a Tuesday afternoon in October.
• The knowledge is in one head. When that person retires or takes a Thursday off, the church starts over.
• There is no history. Nobody can tell whether this family was here in March.

None of that is carelessness. It is what happens when the tool is a piece of paper.

How does the directory find the right provider?

CMinLink starts from a curated directory of local organizations and the services each one offers. Staff search it three ways: by category, by full text across names and descriptions, and by location.

Three things make the result usable at the desk rather than merely correct:

• Open right now. The directory computes whether a provider is actually open at this moment, and when it next opens if it is not. A single organization can keep different hours for its food pantry and its clinic, and the right set is used for the right service.
• Real travel distance. Distances come from mapping services, measured from your church’s address, not straight-line estimates. Walking, driving, transit and bicycling can be compared, which matters when the person in front of you does not have a car.
• Eligibility before the call. Requirements are stored per organization, so a worker can screen before sending someone across town.

You can see the directory on the CMinLink product page.

What about the volunteer who is new?

The person covering the office on a Wednesday morning has not memorized the directory. They can type what they heard in plain language, including the messy version of it, and get matched services back.

The assistant is restricted to the referral domain and is not a general chatbot. It watches for signs of crisis and routes those to 911 and the appropriate hotlines rather than trying to handle them. That boundary is deliberate and it is enforced in the product, not left to the prompt.

What gets recorded, and what stays private?

When a referral is made, CMinLink records which organization, which service category, what the person needed, how the referral was delivered, and who logged it. If the person has been helped before, that history is already there.

Privacy is handled by making anonymity a first-class option rather than an afterthought:

• A referral can be logged with no individual identity attached.
• Anonymous referrals still count in totals and trends.
• Person records are protected by role-based access, and identifiers are stored encrypted.
• Every action is written to an audit trail.

What happens after the referral?

This is the part most churches have never had, and it is worth being precise about what it is and is not.

A referral in CMinLink has a state. It moves from created, to assigned to a specific person on your team, to contacted, to closed. Closing it requires an outcome: served, partially served, or not served. The reason list behind that outcome is configurable per church, so it uses your vocabulary.

A referral can carry a follow-up date. A daily job finds the ones that are overdue and surfaces them, so following up is a list rather than an act of memory.

One claim worth not overstating: CMinLink can send a referral electronically to a partner agency, using the HSDS and FHIR interoperability standards. That is a real capability on the Outreach plan, but it only works with agencies that support those standards, and most local providers do not yet. For everyone else, the referral is delivered the way it always was, by phone, email, print or text, and the outcome is recorded by your staff.

If you want the longer argument for why the follow-up matters, it is in Closing the Loop on Referrals.

What does leadership actually get?

Benevolence money is trust placed in church leadership by the congregation. The reporting exists to answer for it.

• Dashboard totals for referrals today, this week and this month, plus recent activity and the providers you refer to most.
• An outcome and service-gap report with connection rate, median days to close, outcome and reason breakdowns, and gaps by service category. The gap column is the interesting one. It tells you what your community asked for that you had nowhere to send them.
• A directory quality worksheet that surfaces incomplete provider records so staff can fix them, and a printable services directory.
• Export for records, analysis, or sharing anonymized totals with a ministerial association or a regional initiative.

Why not a general-purpose CRM?

A sales CRM can be bent into this shape. Churches that try it end up maintaining the bend.

CMinLink assumes the things a benevolence ministry already assumes: that most of the people you help are not members, that some of them do not want their name in a system, that the person at the desk is a volunteer, and that the answer to “where do we send them” has to arrive in under a minute.

Next steps

• See how it works on the product page.
• Book a walkthrough and we will use your county’s providers, not a demo dataset.
• Compare plans.