Features · Pipelines & Follow-up
Nobody slips through the cracks.
A visitor filled in a card, gave for the first time, or missed three Sundays. Something should happen next, every time, without a staff member remembering to make it happen. That is what pipelines and follow-up are for.
How churches run on it
From "they visited" to "they belong".
01
The visitor pipeline
A connect card lands, a card enters the pipeline, a welcome WhatsApp goes out, and two days later the care team gets the call task. Each stage is visible, so the whole team sees where every person stands.
02
Automations with patience
Steps can wait: for a number of days, for the next service, or for the person's reply. A reminder that fires the morning before the event, not the moment someone registered, is the difference between helpful and noisy.
03
Follow-up as a discipline
Requests are assigned to real callers with a queue, attempts and outcomes are recorded, and anything left too long escalates. Supervisors see the whole board, not a pile of sticky notes.
04
Every trigger you need
Form submitted, first gift, tag added, group joined, a check-in milestone, or membership of a saved list. If the data moves, a pipeline can move with it.
What is in the box.
- Visual pipelines with stages, cards, notes and collaborators.
- Automated steps: send WhatsApp, SMS or email, add to a group, tag, create a follow-up, register for an event, and more.
- Waits and conditions, including wait-until-the-next-service and wait-for-a-reply.
- Follow-up campaigns with caller teams, personal queues, attempts and outcomes.
- Service-level targets with escalation, plus snooze and scheduled callbacks.
- A public "request a call" block for your website that feeds straight into the queue.
Common questions.
A form submission, a first-time gift, a tag being added, joining a group, reaching a check-in count, or landing on a saved list. Cards can also be added by hand whenever a human spots something a trigger cannot.
Yes. Pipeline steps can send messages through your connected channels, including WhatsApp, SMS and email, and a step can wait for the person's reply before deciding what happens next.
A to-do list forgets. Follow-up in Church Flow assigns each request to a caller, tracks attempts and outcomes, escalates when a service-level target is missed, and reports on how the team is doing, so the question is never whether someone was called, but what happened when they were.
Ready when you are.
Your workspace is live in minutes. Build your first pipeline before Sunday.
Start your 30-day free trial →