Engagement-led church platform · Planning Center native
Connect Planning Center and we'll hand you the list, by name: the people who raised their hand for baptism, the first-time guests who never came back, the next steps that quietly went cold. Then we prove whether the follow-up actually worked. Every yes deserves a follow-up.
15 minutes to connect your Planning Center. We only read your data — nothing is sent without your say-so.
Your Leak Report
needs follow-up47
people said yes and never got a follow-up
Marcus Bell
Baptism · registered, never came
The Patterson Family
Visited once, never returned
Tara Whitfield
Growth Track · started, unfinished
Andre Jackson
Said yes to serve, never placed
+ 43 more, by name
Engagement rules watch every yes — across forms, registrations, first-time check-ins, donations, workflows — and surface the people who didn't take the next step. Quiet when it works. Auto-resolves when they show up.
Said yes
Wrote 'I want to be baptized' on a Connect Card
→ Should register for or attend a baptism class
38 people surfaced. 6 had already shown up — auto-resolved. 32 need a phone call.
Was engaged
Gave 4+ months in a row, then stopped
→ Should give again, or have a stewardship conversation
Pastoral care knows before three months pass — back when it's a check-in, not a crisis.
First-time visit
Walked in for the first time
→ Should come back within 30 days
Welcome team gets a Monday list. The ones who didn't come back? You decide whether to reach out.
Open your inbox, read the briefing, click the action list, make the calls. By 10 AM your follow-up list is empty — not because you guessed, because you knew.
The marquee
Sorted by emotional weight: said yes first, then was engaged, then first-time. Each row tells you exactly what triggered it (with a link to the PCO record) and how overdue. Dismiss, snooze, send to a workflow, or write a note.
AI-summarized
“28 said-yes follow-ups outstanding — 6 from the Connect Card ‘Be Baptized’ question over 30 days old. Top urgency: Erica G. (45d).” Plain English. In your inbox at 8am.
Built for messy reality
Trigger → expected follow-up. People register OR they show up — both count. Late attendance still resolves. Auto-builds a journey map of how your church actually moves people from yes to action.
No sales call. No data migration project. No spreadsheet template to fill out.
One OAuth click. We request read-only access to check-ins, events, and giving (admin-only).
Background sync pulls historical attendance + kids check-ins. You're looking at real data in minutes.
AI summary in your inbox at 8am. Drift alerts when something's off. Your pastors finally have a habit.
Battle-tested every Sunday at
Palm Valley Church
3 campuses · 1,000+ weekly attenders · Spanish + English services
“Last month we caught 38 people who said they wanted to be baptized but never registered for the class. Six had actually already shown up — those auto-resolved. The other 32 were phone calls we should have made weeks ago. Now we make them.”
— Brad Grunenwald, COO, Palm Valley Church
Most ChMS tools answer 'what happened.' Next Steps answers 'what didn't happen yet.' The action list is built around the gap between yes and follow-up — not the activity log. Engagement rules auto-resolve when the follow-up actually fires, so the list stays clean. We don't replace your ChMS; we sit on top of Planning Center and act on the data.
Yes. Per-campus rules, per-campus action lists, multi-campus journey maps. Founder Pro and Enterprise tiers include unlimited campuses; Starter is one campus.
Your dedicated database, encrypted at rest, fully isolated from other tenants via row-level security. Read-only PCO scope on our side. Admin-only on your side — staff don't see giving by default.
Yes. Three default roles (admin, staff, viewer) with per-feature gating. Senior pastor sees giving; kids pastor sees their ministry; volunteer leaders see only what you grant them.
Most churches don't. Engagement rules use OR-logic — a baptism class follow-up can be satisfied by EITHER a registration OR a check-in. People who register count, people who walk in count, both get the row resolved. The rules adapt to how your church actually works.
Today we're PCO-native and that's where we excel. Other ChMS support is on the roadmap. If you're on Realm/Breeze/Subsplash, send us an email and we'll keep you posted.