Pastoral Care AI
AI-assisted review of configured engagement signals and follow-up planning for pastoral teams.
Quick Summary: When enabled and configured, Pastoral Care AI may organize selected attendance, group, giving, and interaction signals for staff review and may offer follow-up suggestions. These signals can be incomplete or misleading; they do not establish that someone is disengaging or in difficulty, and they never replace relational discernment.
Overview
In a growing congregation, it can be difficult to notice changes in participation. If enabled, Pastoral Care AI may use configured signals—such as attendance check-ins, small group participation, giving patterns, event registrations, or communication interactions—to support staff review. A change in recorded activity is not proof that someone needs care and may reflect missing data or context outside the platform.
If the configured product provides a dashboard, it may present selected signals for pastoral staff to review, along with any available explanation of how they were surfaced. Staff choose the response; possible next steps include a phone call, a home visit, a care-team assignment, or a personal email. Confirm what follow-up fields and history the current configuration actually records.
Key Features
Engagement Signal Review
If supported, the AI can compare configured engagement signals against thresholds selected by your church. Treat any resulting review item as a prompt to investigate, not a finding of disengagement or personal difficulty; account for vacations, seasonal patterns, data quality, and other context yourself.
Prioritized Care Dashboard
If the dashboard provides sorting or prioritization, treat it as a review aid rather than a measure of pastoral need or severity. Multiple recorded changes can still be incomplete, stale, or explained by context the system does not know.
Suggested Follow-Up Actions
If suggestions are available, they are starting points for human review. A staff member might consider a check-in call, pastoral visit, care-team assignment, or personal email only after confirming the context and the church's consent and care practices.
Follow-Up Tracking
Log every contact attempt, note the outcome, and track follow-up status. The care dashboard shows which flagged members have been contacted, which are awaiting response, and which need additional follow-up.
Privacy Controls
Pastoral-care data is sensitive. Confirm the effective permissions, storage, vendor subprocessors, retention, and current security documentation before enabling this feature. Limit access to approved staff and review it regularly; this guide does not establish a particular data boundary or encryption scope.
Getting Started
Step 1: Enable Pastoral Care AI
Navigate to AI Tools → Pastoral Care AI and toggle the feature on. You will be asked to configure which data sources the AI should monitor: attendance, giving, group participation, event registration, and communication engagement.
Select only the signals that are relevant and consistently tracked at your church. If you do not use check-in for attendance, for example, leave that signal disabled to avoid inaccurate flags.
Step 2: Set Sensitivity Thresholds
If thresholds are configurable, start conservatively and document why each signal is used. Review false positives and missing context regularly; no threshold can determine whether someone needs pastoral care.
Step 3: Assign Care Team Access
Grant dashboard access to pastoral staff and care team leaders. Each person with access can view flagged members, log follow-up actions, and add care notes. You can restrict access by campus, ministry area, or specific member groups to maintain appropriate boundaries.
Step 4: Review and Act on Flags
If a care dashboard is available, choose a review cadence that fits your church's workflow. Review each item as a prompt rather than a determination, consider any suggested action, and assign follow-up only after human review. Log outcomes only in the fields and history supported by the current configuration.
Important Note on Privacy
Pastoral Care AI may process sensitive engagement data. Require leadership approval, communicate transparently about the purpose and limits of monitoring, and review current Relius privacy and subprocessor documentation. Do not assume data remains inside a single account boundary or is excluded from every external processing purpose without written evidence.
Best Practices
- 1.Use AI as a supplement, not a replacement: The dashboard surfaces people who might need care, but pastoral discernment is required to determine the right response. A flagged member might be on a planned sabbatical, not in crisis.
- 2.Review flags weekly: Set a recurring time for your pastoral team to review the dashboard together. Discussing flagged members as a group leads to better-coordinated care than individual ad-hoc responses.
- 3.Log every follow-up: Even a brief note after a phone call helps the team know what has already happened. This prevents duplicate outreach and provides context for the next person who follows up.
- 4.Adjust thresholds over time: If you are getting too many flags for normal attendance variation, raise the sensitivity threshold. If members are falling through the cracks, lower it. The right settings depend on your church's size and culture.
- 5.Restrict access appropriately: Not every staff member needs to see pastoral care flags. Limit access to those who are directly responsible for member care to protect sensitive information.
Common Questions
Q: Do members know they have been flagged?
A: The feature is intended for restricted staff use, but visibility depends on effective permissions and current product behavior. Test with representative roles and communicate the church's use of sensitive engagement data transparently.
Q: What data might the AI use for engagement review?
A: Depending on the product configuration, it may use enabled signals such as attendance check-in records, small group participation, giving changes, event registration history, or email/SMS engagement metrics. Confirm the current data sources, exclusions, and processing behavior in product and privacy documentation; do not assume that care-note or prayer-request content is excluded.
Q: Can I dismiss or annotate a review item?
A: If the current configuration supports dismissal or notes, use them to record the human context (for example, a planned absence or a service change). Verify how dismissal, retention, and later reappearance work before relying on those states.
Q: How does this differ from the existing Pastoral Care module?
A: The standard module focuses on staff-recorded care activity. When enabled, AI may add pattern-based signals for human review; it cannot determine who needs care or replace personal knowledge and consent-aware pastoral judgment.