A Church Visitor Follow-Up Process, Day by Day
A workable follow-up process runs from the Sunday someone visits to the following Sunday: thank them the same day, check in personally on Monday, send something useful midweek, offer a real conversation, invite them back before the weekend, and welcome them if they return. Seven touches, one week, then stop.
The schedule below is deliberately concrete. You can run it from a spreadsheet and a phone, and plenty of churches do. What matters is that it exists in writing and that somebody owns it — a process that lives in one volunteer’s memory stops working the week they’re away.
The week, day by day
| Day | Send | Why |
|---|---|---|
| Sunday | Thank-you message | Sent the same afternoon, while the visit is still the most recent thing that happened to them. |
| Monday | Personal check-in | From a named person, not the church in general. This is the message most likely to get a reply. |
| Tuesday | Something useful | Service times, parking, what happens with kids — answers to the questions people don't like asking. |
| Wednesday | Offer a conversation | A real invitation to talk to a person. Some visitors want this immediately and never ask. |
| Friday | Invitation back | Ahead of the weekend, while plans are still being made. Warm, specific, no pressure. |
| Saturday | Light reminder | Only if they haven't replied. Skip it entirely for anyone who has. |
| Next Sunday | Welcome back | If they return, say so. Being recognised the second time is what turns a visit into belonging. |
Why a week, and not longer?
Because the decision has usually already been made. Someone deciding whether your church is for them is weighing it against everything else in their week, and that weighing happens in the days right after the visit — not a month later.
A sequence that stretches over six weeks isn’t more patient; it’s mistimed. It arrives after the person has already moved on, and it keeps arriving long enough to feel like a mailing list. Concentrate the effort where it can still change the outcome.
What happens when someone replies?
The sequence stops and a person takes over. That’s the whole rule, and it’s the one most systems get wrong by continuing to send scheduled messages alongside a live conversation.
In practice, sort replies into three buckets:
- A question you can answer — service times, childcare, parking. Answer it accurately, from what your church has actually confirmed, and offer nothing more.
- Something personal — a prayer request, a hard season, a question about faith. This goes to a person straight away, the same day if you can.
- “No thanks” — honour it immediately and completely. Someone who asks to stop hearing from you and hears from you again has learned something about your church that no follow-up message will undo.
Who should own the process?
One named person, with a second who covers when they’re away. Follow-up fails on ordinary weeks — the Sunday with a baptism, the week of the school holidays, the month the coordinator is unwell. A process that only runs when someone remembers isn’t a process.
This is the honest case for automating the timing: not because automated messages are better than personal ones, but because the schedule keeps running on the weeks a person can’t. The wider guide to visitor follow-up covers where that line should sit.
Common questions
- What does a good church follow-up sequence look like?
- Thank them Sunday, check in personally Monday, send something genuinely useful midweek, offer a real conversation, invite them back toward the end of the week, and welcome them if they return. Roughly a week, then stop.
- When should you stop following up with a visitor?
- Stop when they reply warmly, when they come back, when a staff member takes over the relationship, or when the sequence ends without a response. Always stop immediately if someone asks you to.