Church operations, with intelligence built in

Know who needs attention.Know what happens next.

Rooted brings people, attendance, follow-up, workflows, reporting and operational intelligence into one system — so care does not depend on spreadsheets, memory or chasing updates.

PeopleAttendanceFollow-upWorkflowsReportsIntelligence
Rooted · Overview

Friday, 9 October

Good evening, Church Admin

People to action

14

Needs attention

8

Unassigned

5

What needs attention

8 people have no recent touchpoint

Review follow-up

5 new visitors are still unassigned

Assign now

Ikeja follow-up is below its recent baseline

View signal
Ask Rooted

“Which branches need follow-up intervention this week?”

Analyse authorised scope

Illustrative product view based on Rooted workflows

One branch or manyScoped by role and responsibilityBuilt around real church workflowsWorks with existing intake processes

The problem is not a lack of care

Your church already has a system.It is just scattered everywhere.

Forms capture names. Sheets track follow-up. WhatsApp carries updates. Attendance lives somewhere else. Leaders ask for reports. Volunteers hold context in their heads. Rooted turns those disconnected pieces into one operating loop.

Capture

Bring the data in.

Forms, imports and connected intake processes feed the same operational system.

Coordinate

Make ownership explicit.

Assign people, tasks and responsibilities according to scope, capacity and your church’s rules.

Operate

Move the work forward.

Today views, workflows, reminders and attendance keep action close to the people doing it.

Understand

See what is actually happening.

Reports and intelligence show progress, risk and breakdowns across teams and branches.

One operating layer

The work is connected because the person is connected.

Rooted is not a pile of modules. Each surface shares the same people, ownership, scope and operational context.

Signals, not dashboard theatre

Know what deserves attention before the meeting.

Rooted Intelligence turns recorded operational data into deterministic signals, while Ask Rooted helps leaders query what is happening in the scope they are authorised to see.

Intelligence · Rooted

Operational overview

Live context

Branches at risk

2

Investigate

Unassigned people

5

Act now

Healthy journeys

73%

On track

Next best action

Rooted keeps the operational decision close to the signal, so teams can move from “what happened?” to “what should we do?” without rebuilding the context.

Rooted Intelligence

A dashboard should not make you do the analysis.

Rooted surfaces operational signals from recorded data and lets authorised leaders ask questions in natural language. The point is not “AI features.” The point is faster, better decisions.

Proactive signals. See overdue, unassigned and at-risk patterns before they disappear into a report.

Ask Rooted. Query follow-up, activity, outcomes and operational context within your authorised scope.

Tell Rooted. Capture follow-up updates in natural language instead of fighting the interface.

What changed this week?

Signal

Follow-up slowed in 2 branches

Recent activity is below the selected comparison baseline.

Opportunity

17 people are close to completion

A focused follow-up pass could move the journey forward.

Ask Rooted
Which teams need intervention and why?

Answer

Two teams show elevated overdue follow-up relative to their recent activity. Review workload and unassigned visitors first.

Illustrative operational signals

One system, different responsibilities

Give each role the view they actually need.

Accountability gets worse when everyone sees everything. Rooted scopes the work and the data to the person responsible for acting on it.

Follow-up Assistant

Start with the next person.

See the people who need action now, the context behind the task and the outcome you need to capture.

Prioritised daily queue
Context before every conversation
Simple follow-up capture

Built for real church operations

Grow the church without losing the operating model.

Branches can run locally while leaders retain the visibility they need across the organisation. Roles, permissions, assignment rules and workflows keep responsibility clear as the structure grows.

Branch-level responsibility and workload controls
Scoped dashboards, reports and intelligence
Roles and permissions across the organisation
Shared operating standards without flattening local teams

Organisation

Branch health

Ikeja

8 need attention

Review

Lekki

Follow-up healthy

Healthy

Yaba

3 unassigned

Assign

Surulere

Journey on track

Healthy
Same operating model. Local responsibility. Shared visibility.

Make care operational

Stop rebuilding the state of the church every time someone asks for an update.

Put people, attendance, follow-up, workflows and operational intelligence in one place — with clear ownership from the first visit onward.