Tasks. Workflows. Messaging.
The operational layer ministry actually runs on.
Tasks tied to people and ministries — assigned, due-dated, and visible to the staff who owns them. A workflow engine that fires automatically off form submissions, milestones, giving events, and lifecycle changes. Internal staff messaging and org-to-member conversations through topic inboxes. The infrastructure that makes follow-through happen.
The middle layer that nobody markets but every church needs
The reason follow-through usually fails
isn't bad intent. It's missing infrastructure.
Every church staff has the same problem: things get dropped. The welcome-card follow-up that never happened. The pastoral call that was supposed to go out by Friday but ended up in the next Tuesday's “wait, did anyone…” conversation. The volunteer onboarding that stalled because three different staff thought someone else was handling it. The widow who hasn't been visited in two months because the spreadsheet of follow-ups lives on one person's laptop.
The reason isn't lack of care. Church staff care. The reason is missing infrastructure — the absence of a system that translates “someone should follow up” into a specific task on a specific person's list, that fires automatically when the right trigger happens, that's visible to the rest of the team so coverage gaps surface before they become drops.
Tasks, Workflows & Messaging is that infrastructure. Tasks live tied to people and ministries, assigned to specific staff, with due dates and overdue flags. The workflow engine fires automatically from form submissions, lifecycle changes, giving events, milestones, and QR scans — converting the moment that requires a follow-up into a task and an email without staff having to remember. And internal staff messaging plus topic-routed org-to-member inboxes round out the communication layer that ties the operational system together.
A task isn't a sticky note. It's tied to a person, a ministry, or a workflow.
Every task on TrueConnect+ is attached to something specific. Open a task against a person (“Call the Jones family about the funeral arrangements”), a ministry (“Schedule the youth retreat venue walkthrough”), a workflow step (“Review new-member welcome packet draft”), or a service plan (“Confirm guest speaker bio for next Sunday”). The context is part of the task — you don't have to remember why a task exists.
Tasks have due dates, priorities, assignees, completion checkboxes, and comment threads for context that emerges during the work. Overdue tasks surface on the assignee's dashboard and on their manager's. Tasks can be created manually, generated by workflows, or assigned by other staff members.
- Tasks tied to a person, ministry, service plan, or workflow
- Due dates with overdue surfacing on assignee and manager dashboards
- Comment threads on tasks for context that emerges during the work
- Manual or workflow-generated; visible to the right staff per role
A trigger. A condition. Chained actions. Everything else fires itself.
The workflow engine is the brain of the operational layer. Workflows are visual rules: when [trigger], if [condition], do [action]. Triggers include form submissions, lifecycle stage changes, giving events, milestone reached, event attendance, QR scan, and recurring schedules. Conditions filter by member attribute, ministry, campus, or any tagged property. Actions chain: send an email, create a task, update the CRM, schedule a future step, add to a segment, message a staff member, or trigger another workflow.
Real workflows in real churches: welcome-card submission triggers welcome email + pastoral task + lifecycle transition. First gift triggers thank-you email + tax-receipt + assign to giving ministry. Volunteer interest triggers onboarding sequence + background-check prompt + ministry-lead notification. Lapsed-member detection triggers outreach list addition + pastoral call task. Every one of these is written once and runs forever.
- Visual workflow builder; no scripting required
- Triggers: forms, lifecycle, giving, milestones, attendance, QR scans, scheduled
- Chained actions across email, tasks, CRM, segments, staff notifications
- Conditional branches for different audiences on the same trigger
Conversations that belong in the system, in the system.
Staff messaging happens. The pastoral team chats about a sensitive follow-up. The worship team coordinates a last-minute rehearsal change. The kids team flags a parent-side incident from Sunday. When that messaging happens in a third-party tool, the context is lost the moment the conversation moves to email or a shared decision.
Internal staff messaging on TrueConnect+ is scoped to roles and ministries and tied to the records being discussed. Open a discussion thread on a specific person, a specific service plan, a specific ministry decision — and the conversation lives where the work lives. Org-to-member communication happens through topic-routed inboxes: members submit to Prayer, Information, or other inboxes the church has opened, and staff respond from the unified inbox view. Members cannot DM each other; the platform's messaging model is staff-managed by design.
- Internal staff DM and group conversations scoped to roles and ministries
- Threaded discussions tied to specific records (people, services, ministries)
- Topic-routed org-to-member inboxes (Prayer, Information, custom topics)
- No member-to-member DM — staff-managed messaging model by design
The whole operational layer
How the staff actually gets things done.
Staff to-do dashboard
Every staff member opens a Tuesday-morning view: today's tasks, overdue items, upcoming deadlines, unassigned items in their ministry. The work for the week, prioritized and visible.
Workflow templates
Pre-built workflow templates for common church motions: welcome-card follow-up, first-gift thanks, lapsed-member outreach, new-volunteer onboarding, birthday and anniversary cards. Drop in, customize, activate.
Topic inbox routing
Members submit to topics the church opens — Prayer goes to the prayer team, Information to the office, Pastoral Care to the pastoral team. Staff sees a unified inbox per topic. Response is threaded.
Pastoral-care task pipeline
Pastoral follow-ups, hospital visits, funeral arrangements, marriage counseling, and recovery check-ins live in a dedicated task pipeline visible only to Pastoral Care role and above.
Workflow analytics
See which workflows are firing how often, which ones complete vs. abandon, where members drop off in an onboarding sequence. Tune the funnels that matter to your church's growth.
No more “wait, did anyone…”
The whole layer exists for one reason: the things that need to happen, happen. The pastoral call that should go out by Friday is on a specific pastor's list, with a Friday due date. The welcome email fires before the visitor finishes their drive home. Nothing falls through.
What a week of staff work looks like with the layer.
Monday morning, the executive admin opens her dashboard. Eight tasks due this week, three overdue from last. The overdues stand out — she works through them in twenty minutes. The welcome-card workflow generated four new pastoral tasks over the weekend; they're on the right pastors' lists with Friday due dates. The first-gift workflow sent thank-you emails to six new givers automatically.
Wednesday, a member submits a prayer request via the Prayer inbox. The request lands in the unified pastoral-team inbox. A pastor responds within the hour. A workflow fires to add the member's name to the prayer-team rotation list. A task lands on the pastor's Friday list to call the member personally.
Friday afternoon, the lead pastor opens his Friday view. Three pastoral calls to make. He makes them. He marks the tasks complete with a brief note on each. The workflow advances to step two — a follow-up email queued for the following Tuesday. The next Tuesday, the email goes out automatically. The next call surfaces on his task list two weeks later.
Nothing was dropped. Nobody had to remember. The system handled the remembering, the team handled the ministry. That's the operational layer doing its job.