How to Build a Church Guest Follow-Up Process

Recently I was talking to a woman who had been to our church a few times. I asked if she'd stopped by the connection desk so someone could follow up with her. She had — last winter.

That caught my attention, because during that stretch I was the person responsible for those calls. I told her she should have heard from me. She didn't really remember the call. She did remember the texts from the church.

Then she said something that bothered me. She had replied to one of those texts, and nobody responded. She wasn't sure whether a person monitored the number or whether everything was automated.

I know who was responsible for that number. This isn't a slam against them. They were busy with larger church issues, and nobody ignored her on purpose. That's the problem. The system worked when it needed to send something out. It failed when a real person tried to talk back.

She still comes occasionally. I couldn't help wondering how much more connected she might already feel if we'd stayed with that conversation.

That's what I mean by people falling through the cracks. Someone has fallen through when we can no longer answer basic questions: Who is this person? Who owns the next step? What is supposed to happen next? When? What happened last time? Is anything still open?

If we don't know, somebody gets missed.

Caring About People Isn't Enough

Most churches genuinely believe people matter. James 2:15–16 talks about seeing a brother or sister in need, saying the right things, and then doing nothing. James is dealing with something larger than guest follow-up, but the principle should still bother us. At some point, saying we care has to produce action.

Churches are also legitimately busy. Sermons have to be prepared. People need counselling. Buildings break. Staff and volunteers already have full lives. We can spend a lot of energy thinking about the people we'd love to reach while overlooking somebody who already walked in and gave us their information.

I don't say that from superiority. When I was the lead pastor of a smaller church, I was bad at this. I cared about new people. I was also dealing with flooding, climbing a steel roof looking for HVAC leaks, writing sermons, and handling whatever else had broken that week.

Caring about something and having a system that makes sure it gets done are not the same thing.

Faith Perceptions showed how large that gap can get. From October 2015 through September 2016, 504 first-time guests voluntarily gave churches their contact information. After 30 days, only 119 — 24% — had received any follow-up. Researchers found confusion over who should follow up and when, and even churches with a process often had little accountability that it happened. The study was published in Outreach Magazine as Most Churches Neglect This Vital Outreach Practice.

That's not primarily a compassion problem. It's a systems problem.

Who, What and When?

Imagine the seniors ministry uses a gathering space on Wednesday, then leaves the tables out because they assume somebody else will need them. Thursday, the youth pastor walks in and has to clean up another ministry before he can start his own.

Nobody was malicious. They made assumptions.

Churches love saying, “We're all one big team.” That's true. Teams still have positions. A baseball team doesn't put nine people on the field and tell everyone they're equally responsible for everything.

For follow-up we should be able to answer three questions: Who is responsible? What needs to happen? When does it need to happen?

Life.Church uses essentially those questions in its 2018 Open Network article 6 Elements of a Successful Staff Meeting: What needs to be done? Who is responsible to get it done? When will it be completed?

If we establish that kind of clarity around events, budgets, and buildings, people deserve the same attention.

One Person Needs to Own the Next Step

Ownership doesn't mean one person solves every need. The person doing the first call may learn that a teenager wants youth information, or that something sensitive belongs in pastoral care. Their job is not to become everything to everybody. Their job is to make sure the appropriate next thing actually happens.

And who should that person be?

Experienced leaders don't all agree. Lifeway's Ken Braddy has argued that a connection from an ordinary group member can feel more meaningful, because a guest may assume staff are simply doing their job. Danny Franks has described The Summit Church moving the other way, toward campus staff making first contact, because guests often responded better when the caller could say they were one of the pastors or staff.

We don't need one of them to be universally right. There may not be one correct kind of person to do the follow-up. There does need to be one clearly assigned person.

Church culture, size, staffing, and the person being contacted may change who that is. Ambiguity shouldn't.

Churches are very good at passing information and assuming they passed responsibility.

“I emailed that to the youth pastor.”

Great. Did the youth pastor actually get it?

“I sent it.”

That's not what I asked.

People open a message, think “I'll deal with that later,” and forget. I realize that's an extremely rare phenomenon experienced by almost nobody. Still, we should plan for it.

A handoff isn't complete until the next person acknowledges it — a reply, an accepted task, a recorded note that they're now handling it. Information sent is not responsibility transferred.

The workflow is simple: Person → Owner → Next Action → Outcome. Then the outcome determines what happens next.

Keep the Person in One Place

This is where churches accidentally create five versions of the same human being.

Children's ministry knows one thing. The pastor knows something else. There's a Connect Card. The office has an email. A volunteer has a text thread on a personal phone.

Danny Franks makes the same point in his 2022 Church Answers article 7 Steps to Structure Your Guest Follow Up Process: newcomer information should flow into one process, not sit in ministry silos. One church contact can be appreciated. Four ministries independently contacting the same guest, because none of them knows what the others are doing, gets annoying quickly.

That doesn't mean everybody should see everything. They shouldn't. Sensitive pastoral information needs different visibility than a guest follow-up note. But the right people need the right information.

If someone already told another leader they just moved to town and are looking for a strong youth ministry, the youth pastor doesn't need to start with, “So, what brings you here?” They can start with, “Steve mentioned you recently moved and were asking about youth. I wanted to connect.”

One conversation starts over. The other continues.

Good recordkeeping isn't collecting as much as possible. It's preserving enough relational memory that the next person doesn't begin at zero. The database serves the relationship. The relationship doesn't exist to fill the database.

Give Follow-Up an Actual Timeline

Once somebody has responsibility, they need to know when to act.

My preference has been an immediate acknowledgement that their information was received, then a personal connection a few days later. In the settings I've worked in, I've liked a phone call within three or four days: enough breathing room after Sunday that the relationship doesn't disappear for two weeks.

Life.Church's January 2026 Open Network article Systems that Sustain Success in Ministry uses a tighter rhythm: welcome email within 24 hours, personal text or call within 48 hours, invitation to a specific next step within a week. It also insists on an owner and information the team can actually find.

You don't have to copy those times. You do have to decide yours.

“Someone should call them sometime” is not a process.

And don't confuse sending something with connecting with someone. Email, text, and cards are useful. They are not the same thing as a conversation. A phone call gives someone room to say why they came, ask a question, mention their kids, or tell you they already follow Jesus and just moved to town. Then the next step can respond to the person instead of marching them through a sequence.

We walk through a simple first-week and first-month rhythm in The Church Guest Follow-Up Checklist. The point of this article is the operating system underneath that rhythm.

Follow-Up Doesn't Need to Continue Forever

This is where a system can become stupid if you let it.

If I call and learn they were visiting family and live six hours away, there may be no reason to follow up again. If they moved to town, already follow Jesus, and have started attending, there may be several natural next steps. If they clearly don't want further contact, stop.

Sometimes the appropriate next step is nothing. That doesn't mean we've written somebody off. It means there isn't a discernible action right now. Note the outcome so the next leader doesn't start from scratch.

That's why a completed task is not a completed journey. A Welcome Call can be finished while the person is still a new guest. What you learned on the call determines whether anything else should happen.

People aren't obligated to keep moving through a pipeline because software has another box.

What If They Don't Answer?

There's no biblical rule that says you call twice, send one text, and then surrender them to the void. Use judgment.

For me that might mean one call and a short voicemail, then another try a day or two later: “Hey, it's Steve again. Just wanted to follow up. If you have any questions, feel free to call.”

We're trying to show care, not hunt somebody down. Eventually follow-up ends. Good follow-up leaves a door open. It doesn't chase people through it.

Accountability Shouldn't Take an Hour

If the process is working, reviewing guest follow-up in a church of a couple hundred people should take about two minutes, including logging in. Are calls being made? Anything unassigned? Overdue? Stalled?

Everything healthy? Encourage the people doing the work and move on.

If there's suddenly a long overdue list, ask why. Someone may have been sick, at a funeral, on vacation, or buried in something else. Show grace. Accountability isn't assuming somebody failed. It's noticing when something isn't happening and asking why, or even better, planning ahead for what may be coming and making sure there's a plan so no correction is needed.

If it becomes a pattern, maybe expectations weren't clear, the work is happening but not being recorded, the person doesn't have capacity, or the responsibility needs to move.

Follow-up also teaches the church something. If guest after guest says no other church ever called them, that's worth hearing. If several families describe the same confusing experience, that's worth fixing.

Where Technology Helps — and Where It Should Stop

A database isn't ministry, because databases aren't people. Automation helps when nobody can keep every responsibility in their head. It becomes harmful when it replaces a human conversation.

That's what we've tried to build Church Journey around.

When someone fills out a Connect Card, the administrative pieces can happen on their own: a person record, a place in the New Guest track, and a Welcome Call task with a due date, ready for someone on the team to take responsibility. Then a person does the ministry. They record a touchpoint so the next leader isn't starting over. If another step is needed, it gets its own owner and deadline. If responsibility moves, the handoff is acknowledged. If nothing else is needed, you stop.

That reflects the actual current workflow: the Welcome Call is created as an open, high-priority follow-up task and begins unassigned until someone on the team takes responsibility.

Church Journey is not supposed to decide someone is “Connected” because a Welcome Call got checked off. Completing a task doesn't change the journey. A leader does.

Put simply: automate responsibility, not relationship. The system should remember what humans forget. It shouldn't make pastoral decisions humans should make.

To me, somebody is connected when they're known and they feel known. Not because everyone knows everything about them but because they feel cared for. They feel loved. They're beginning to feel at home.

Software can't manufacture that. It can make it much harder to forget them.

Nobody Falls Through the Cracks

Think about a swimming pool. You put a fence around it so somebody isn't hurt by accident. The fence doesn't stop a person who wants to get in. They can open the gate. The point isn't to eliminate choice. It's to keep carelessness from doing the damage.

That's what I mean when I say nobody should fall through the cracks.

We can't make a guest come back, answer the phone, join a group, or belong. Nor should we.

But somebody shouldn't disappear because everyone assumed someone else called. A new believer shouldn't spend months wondering what happens next because nobody owned it. A family shouldn't retell the same story because ministries don't talk. And somebody shouldn't reply to the number we published and wonder whether a real person is on the other side.

Nobody falls through the cracks isn't a promise that every person stays. It's a commitment that somebody doesn't disappear because we forgot them, lost their information, assumed another person handled it, or never decided what should happen next.

The system isn't the ministry. The system makes sure the ministry has a chance to happen.

Because if we really believe people matter, we should build our churches like they do.