How Multi-Site Churches Coordinate Visitor Follow-Up Across Campuses

When your church meets in three, five, or ten locations, a first-time guest at your east campus should get the same warm, timely welcome as a guest downtown. In practice, that rarely happens on its own. Coordinating visitor follow-up across campuses is one of the hardest problems multi-site churches face — because it lives at the intersection of data, people, and habits that vary from site to site.

This post lays out a practical framework: shared standards everyone follows, clear ownership at each level, and a blended contact rhythm anchored by a real phone call. You'll get a copy-ready campus playbook and a weekly cadence you can adapt.

Why multi-site follow-up breaks down

Most gaps aren't caused by lack of care. They're caused by unclear handoffs. The common failure points:

• No single source of truth. Connection cards live in one campus's inbox, digital forms feed a central CRM, and nobody's sure which list is current.
• Inconsistent timing. One campus calls within 24 hours; another gets to it "when someone has a chance."
• Ownership confusion. Is follow-up a central-office job or a campus job? When it's both, it's often neither.
• Over-reliance on automation. A central team blasts the same welcome text to every new guest and calls it done — which feels efficient but rarely brings anyone back.

Solve those four and you've solved most of it.

Set one standard, execute locally

The winning model for multi-site follow-up is central standards, local execution. The central team defines what good follow-up looks like; each campus owns doing it with its own volunteers and its own voice.

What the central team owns

• The follow-up timeline (who gets contacted, when, and by what method)
• Approved scripts and templates every campus starts from
• The shared database or list system so no guest falls through the cracks
• Reporting: return rates, contact rates, and outcomes by campus

What each campus owns

• A named campus follow-up lead (this is non-negotiable)
• Recruiting and scheduling local calling volunteers
• Making the calls within the agreed window
• Logging outcomes so the central team can see what's happening

This structure keeps the guest experience consistent without forcing every campus into a robotic sameness. A volunteer calling a guest should sound like a real person from their neighborhood, not a corporate call center.

Build a shared contact rhythm

Agree on one timeline all campuses follow. Here's a blended rhythm that pairs quick digital touches with the personal call that does the heavy lifting.

1. Day 0 (Sunday): Automated text or email within a few hours — brief, warm, no ask. "So glad you were with us at [Campus] today."
2. Day 2–3: A personal phone call from a campus volunteer. This is the single most important touch.
3. Day 5: A short follow-up text or email if the call went to voicemail, with an easy next step (a group, a class, a service time).
4. Day 10–14: A pastoral or care touch for guests who engaged — an invitation to a newcomers gathering.

The text is the doormat. The call is the handshake. Congregations today are saturated with automated blasts and robocalls, so a mass text alone blends into the noise. A live volunteer asking, "How can we be praying for you this week?" cuts through — and it's the touch guests actually remember and respond to.

A copy-ready campus follow-up playbook

Hand this one-page playbook to every campus lead so the standard is unmistakable.

Goal: Every first-time guest receives a personal phone call within 72 hours.

Roles:

• Campus follow-up lead — owns the weekly process
• 2–4 calling volunteers per campus
• Campus pastor — receives escalations (prayer needs, crises, membership interest)

Weekly cadence:

• Monday AM: Lead confirms the new-guest list is complete and assigns names to volunteers.
• Monday–Tuesday: Volunteers make calls and log outcomes.
• Wednesday: Lead reviews outcomes, escalates anything pastoral, and sends the Day-5 follow-ups.
• Sunday: Lead reports campus numbers to the central team.

Definition of done: A guest is "followed up" only when a real conversation happened or two call attempts plus one text/email were made and logged.

A short volunteer call script

"Hi [Name], this is [Your Name] — I'm a volunteer at [Campus Name] of [Church]. I'm not calling for anything, I just saw you visited this weekend and wanted to say how glad we were to have you. How was your experience?"

(Listen.)

"That's great to hear. Is there anything you're hoping to find in a church, or anything we can be praying about for you?"

(Listen. Note it.)

"I'd love for you to feel at home here. We have a short newcomers coffee after the [time] service — no pressure at all. Would it be okay if I texted you the details?"

"Thanks so much for the time, [Name]. I hope to see you Sunday."

Keep it under three minutes. The point isn't to close a sale — it's to be a warm human voice attached to the building they visited.

Keep the data clean across campuses

Coordination lives or dies on the list. A few rules that prevent guests from getting missed — or double-contacted by two campuses:

• One intake path per campus. Digital connection card feeds directly into your shared system. Paper cards get entered same-day by a named person.
• Tag every guest by campus so lists route to the right volunteers automatically.
• Log every attempt and outcome, not just successes. "No answer" is information the next volunteer needs.
• Flag pastoral needs immediately so a campus pastor follows up, not a volunteer.

This is where a tool that assigns lists, routes them by campus, and tracks call outcomes earns its keep. ChurchCallerHQ was built for exactly this — organizing volunteer calling so a central team can see contact and return rates across every location while each campus works its own list. One church volunteer put it simply: "This app is the best! I just can't stop calling!" That enthusiasm is contagious, and it's what you want spreading across campuses.

Measure what matters — by campus

You can't coordinate what you don't measure. Track these weekly, broken out by location:

• Contact rate: % of new guests who received a live phone conversation
• Attempt rate: % who received the full agreed sequence
• Return rate: % of first-time guests back within 30 days
• Escalations: prayer/care needs passed to pastors

When one campus's contact rate lags, you'll see it — and you can coach that campus lead specifically rather than guessing. Celebrate the campus that's calling well; let its lead share what's working on your next team call.

A gentle next step

You don't need to overhaul everything at once. Pick one standard — the 72-hour personal call — and get every campus doing it consistently for a month. Add the shared reporting once the habit sticks.

Multi-site follow-up isn't about tighter control from the center. It's about giving every campus the same clear standard and the freedom to reach their neighbors with a real, human voice. Start with one call, from one volunteer, at one campus this week — and build from there.