Product tour
See one care journey from first request to faithful follow-up.
Walk through how a church receives a need, protects sensitive context, coordinates staff and volunteers, and keeps leaders informed without losing the human story.
A connected ministry workflow
Six moments, one shared care record.
The tour follows a request as it becomes coordinated care. Each screen shows a capability already available in Faith Care HQ.
-
Step 1
A care request arrives.
A member or community visitor can use the church's public page to ask for care without creating a staff account. The form captures enough context for the team to respond while setting clear expectations about emergencies and sensitive information.
Public access stays separate from staff access
The church controls whether care requests, prayer requests, and volunteer signup are available. Public submitters never receive access to the internal workspace.
The fictional church hub presents only the public options enabled by that church. -
Step 2
The team reviews and routes the need.
New requests enter a focused inbox where authorized staff can review urgency, assign ownership, and convert the request into an active care case when ongoing coordination is needed.
Intake becomes accountable work
Status, urgency, assignment, and submission details help the team move from an incoming message to a clear next action.
The inbox keeps new and active requests visible without exposing them on a public page. -
Step 3
Care stays connected around one case.
The case brings together ownership, notes, tasks, visits, timelines, privacy levels, and follow-up history. Staff can see what happened, what is next, and who is responsible.
Privacy follows the context
Standard, pastoral, counseling, and restricted visibility allow the team to protect sensitive details instead of treating every record the same.
A shared case record gives authorized staff continuity without flattening privacy boundaries. -
Step 4
Volunteers receive only the assignment they need.
Approved volunteers can support tasks and visits through secure assignment links. They can accept, decline, complete, or request help without becoming staff users or seeing the full care case.
Participation without broad access
The volunteer experience is intentionally narrower than the staff workspace and communicates only the context needed for the assignment.
Token-based assignment links let volunteers respond without a staff login. -
Step 5
Leaders see where attention is needed.
The dashboard brings urgent cases, overdue work, care trends, requests, volunteer activity, and automation alerts into a daily operating view for ministry leaders.
Visibility supports follow-through
Leaders can identify stalled work and emerging pressure without opening every case individually.
The dashboard summarizes the fictional church's current care workload and trends. -
Step 6
AI helps staff prepare and summarize.
Built-in assistants can draft case consolidations, suggest next steps, prepare member or household briefings, summarize visits, and create workflow drafts within the church's plan allowance.
People remain responsible for care decisions
AI output is a draft for authorized staff to review. It does not replace pastoral judgment, consent, or the church's responsibility for what it records and shares.
AI tools sit inside the care workflow so staff can review suggestions alongside the source context.
See how the workflow fits your ministry.
Create a church workspace to explore the full Team trial and see how the workflow fits your care process, roles, and privacy needs.