First-timer & member-care operations
Every first-timer should have a clear next step.
Rooted gives your church one system to capture visitors, assign ownership, guide follow-up, spot people slipping through the cracks, and understand whether they are actually becoming connected.
The real problem
Care becomes hard to coordinate as your church grows.
Once responsibility is spread across forms, WhatsApp chats, spreadsheets, volunteers, and multiple leaders, good intentions stop being enough.
Who needs follow-up today?
Who owns each first-timer?
Who is beginning to disengage?
Which teams or branches need intervention?
Rooted turns those questions into a daily operating system — not another spreadsheet to maintain.
From first visit to real connection
One journey. Clear ownership at every step.
Rooted coordinates the work that happens after someone first walks through the door.
Current stage
Capture every first-timer.
Bring new people into Rooted from forms, imports, and the intake processes your church already uses.
Google Form
Connected source
CSV upload
New visitor batch
Manual entry
Welcome desk
Illustrative product view
Built around the people doing the work
Rooted answers a different question for every role.
For follow-up assistants
Know exactly what to do today.
Instead of scanning a long visitor list, each assistant gets a focused workspace showing who needs attention, why they need it, and the next action to take.
Follow-up Assistant view
What needs attention now
First calls
4
Follow-ups
7
Overdue
2
Next action is visible, not buried.
Rooted turns operational data into a clear decision for the person using it.
Illustrative sample data
The operating layer
The promise is accountability. These are the systems underneath it.
Smart assignment
Distribute first-timers according to capacity, availability, and the rules your church chooses.
Needs Attention
Surface people who have gone too long without meaningful contact or need intervention.
Today workspace
Turn a large visitor list into a small, ordered queue of what needs to happen next.
Workflows
Automate recurring operational steps so the process does not depend on memory.
Leadership reporting
See progress, risk, workload, and activity across teams and branches.
Roles and scope
Give each role the visibility and responsibility appropriate to them.
Built for scale
One branch or many. Keep the operating model consistent.
Teams work within their local branch while leaders retain visibility across the wider church without everyone seeing or managing everything.
Ikeja — 8 need attention
Lekki — follow-up healthy
Yaba — 3 unassigned
Illustrative sample data
Make follow-up operational
Build a follow-up system that does not depend on people remembering.
Give every first-timer an owner, every follow-up assistant a clear next action, and every leader visibility into where the process needs attention.