The directory your members see.
The CRM your staff works in. One record.
Every member is one record — household, ministries served, attendance, giving, prayer requests, lifecycle stage, pastoral notes, follow-up tasks. Members see the directory and update their own info. Staff sees the whole picture. The same data, two appropriate views.
People aren't rows in a database. Software keeps forgetting that.
The same person is a giver,
a volunteer, a small-group attender,
and a parent picking up at 11.
In a church running on five separate tools, the same person lives in five separate records. The giving platform has her as a donor. The volunteer scheduler has her as a hospitality team member. The kids ministry tool has her as a parent with two children in different rooms. The email platform has her on three different lists. The directory has her with an outdated phone number that nobody's updated since 2018. When the lead pastor wants to know who she is — her full story across the church — there's no one place to look.
Directory + CRM holds the whole picture in one record. A person is a unified record: contact info, household relationships, ministries they belong to, roles they serve in, services they've attended, gifts they've given (with permissions gated to the right staff), prayer requests they've submitted, pastoral notes about them, and every follow-up task tied to their care. The member sees the directory and updates their own record. Staff sees the same data plus the pastoral and engagement context — and only the staff roles with the right permissions see giving or pastoral notes.
The result: when a pastor sits down to call a family on Tuesday, they have the whole context in one view. When a small-group leader looks up a member, they see what they're permitted to see and nothing else. When a member updates their address from their phone, every system that touches that address gets the update at once.
People belong to families. The data should reflect that.
Most church databases treat each person as an island. That breaks immediately when you try to schedule the family for a parent-child dedication, send a household-level newsletter, or look up the children of a couple in marriage counseling. The household has to be a first-class concept, because in real life it is.
Households on TrueConnect+ are records with their own page — primary contacts, dependents, shared address, household-level photo, and the relationships between members (spouse, parent, child, guardian, sibling). One change to the household address updates every member at once. Communications can address the household or any of its members specifically.
- Households as first-class records with shared address and household photo
- Spouse, parent, child, guardian, and sibling relationships
- Household-level addressing for newsletters and communications
- Per-member privacy controls inside a shared household
Where someone is on their journey with the church should be a system, not a guess.
Every person at your church is at a stage: visitor, regular attender, member, leader, alumni. Most of the time the stage is implicit — staff knows it but no system tracks it. That means the welcome-card follow-up workflow can't fire automatically. The membership-class invitation can't target the right audience. The lapsed-member outreach can't find the right list.
Lifecycle stages on TrueConnect+ are explicit, configurable, and automated. Move someone from visitor to regular attender after their third Sunday — the welcome workflow ends, the connect-card workflow begins. Move them to member after the membership class — a welcome packet goes out, they join the members-only directory. The CRM tracks where every person is, and workflows respond automatically.
- Configurable lifecycle stages (visitor, attender, member, leader, alumni)
- Automated transitions based on attendance, milestones, or workflow events
- Per-stage workflows for onboarding, engagement, and pastoral care
- Reporting by stage — see how many are at each level of engagement
Members see and update their own record. Staff trusts the data more.
The reason most church directories are out of date is that updates require staff to type new info into a system. People move, change phones, change emails, get married, have kids — and nobody calls the office to update the record. The directory drifts.
On TrueConnect+, members see their own record in the directory and can update what they own — contact info, photo, communication preferences, household info, what ministries they want to be part of. Staff sees verified updates and trusts the data. The directory stops being a snapshot from 2018 and becomes living information.
- Member-facing directory app with self-service updates
- Per-field privacy controls (who in the directory can see your phone)
- Photo upload from the member's phone
- Communication preference management built into the profile
The CRM beneath the directory
Everything a pastor needs to actually pastor.
Cross-workspace context
Open a person's record and see attendance, giving (permission-gated), ministry involvement, kids in their household, recent prayer requests, last pastoral interaction, and any active workflows they're in. One view, not seven tools.
Tags + segments
Tag a person with anything that matters — “new dad,” “empty nester,” “recently divorced,” “medical worker,” “musician.” Tags drive live segments for communications, ministry assignments, and pastoral targeting.
Pastoral notes + permissions
Confidential pastoral notes are gated to Pastoral Care role and above. The Volunteer Coordinator doesn't see them. The notes are encrypted, audit-logged, and survive staff turnover.
Tasks tied to people
Open a task against any person — “Call about the funeral arrangements,” “Send the new-parent welcome kit,” “Check in on the recovery group leader.” Due dates, overdue alerts, the right assignee.
Bulk import + export
Bringing a directory over from another tool: CSV import with field mapping, validation, dry-run preview, and rollback. Exports the same way. Your data stays portable, by design.
Engagement metric
Every person carries a rolling engagement score based on attendance, giving, ministry participation, and event attendance. Drops in engagement surface as outreach lists before the person quietly drifts away.
Tuesday morning, with a pastor and a phone.
Tuesday at 10am, the lead pastor opens his Tuesday outreach list — five families surfaced by the CRM as drifting from engagement. He picks the first one. The family record opens with the full picture: a couple with two teenagers, in the church for six years, used to lead a small group, gave regularly until eighteen months ago, attendance has been thin since the husband's job change. No recent pastoral notes. No active workflow.
He calls. They talk for forty minutes. The husband's job has been brutal; they've been showing up sporadically because Saturdays are hard. The wife mentions a friend at work going through cancer. The pastor offers to add the friend to the prayer team's list — and there, in the same window, he creates the prayer request and assigns it to the prayer ministry leader. He marks the call complete on the task list. He adds a brief, confidential note.
The husband, the wife, the friend, the prayer request, the pastoral note, the task — all one record, all connected, all in one view. Tuesday becomes ministry in a way it can't be when the pastor has to switch between four tools to do it.