The Multi-Campus Follow-Up Playbook: One Standard, Many Locations

When your church grows from one location to three, five, or ten, a strange thing happens: your follow-up gets worse before it gets better. Each campus develops its own habits, guest cards live in different inboxes, and a first-time visitor at your east campus has a very different experience than one downtown. Figuring out how multi-site churches coordinate visitor follow-up across campuses is less about buying more tools and more about agreeing on one standard everyone runs.

This is a playbook for the person who owns that standard — usually a central Connections or Assimilation Director working with campus pastors. The goal isn't uniformity for its own sake. It's making sure a guest gets a warm, personal, timely response no matter which door they walked through.

Why multi-site follow-up breaks down

Before the fix, name the failure points. Across multi-campus churches, follow-up tends to slip for a few predictable reasons:

• No single owner. Everyone assumes another campus or the central team has it handled.
• Inconsistent timing. One campus calls guests Sunday night; another gets to it the following Thursday, if at all.
• Data scattered everywhere. Paper cards at one site, a Google Form at another, a QR code at a third.
• Wildly different quality. A guest at Campus A gets a personal call; a guest at Campus B gets a generic mass text and nothing else.

The answer to all four is a shared standard plus clear ownership at each location.

Set one follow-up standard for every campus

Write down the non-negotiables that apply everywhere, then let each campus own the execution. Think of it as a franchise model: same recipe, local kitchen.

Your central standard should define:

1. The timeline. For example: a first-time guest gets a personal phone call within 48 hours, a text within 24, and a handwritten note within a week.
2. The channels and their order. Text to say thanks quickly, then a real call to build relationship. A blended approach works — texts are great for logistics and speed, but a human voice is what actually brings people back.
3. The core message. No sales pitch. Say thank you, ask one question, offer one easy next step.
4. The outcome you track. Every attempt is logged: reached, left voicemail, texted, or no answer — plus a note.

Why the phone call stays central

Most congregations are drowning in automated blasts — appointment reminders, promo texts, robocalls. When a real volunteer calls and says, "Hey, I saw you visited Northside on Sunday, I just wanted to say we're glad you came," it cuts through in a way no automation can. A live voice communicates that a person, not a system, noticed them. Keep texting for what it's good at, but don't let it replace the call.

Decide who owns what: central vs. campus

The biggest coordination win is drawing a clean line between central and local responsibilities. Here's a division that works for most multi-site churches:

Central team owns:

• The standard, scripts, and templates
• Training and onboarding new campus calling teams
• Reporting across all campuses (so you can spot the location that's slipping)
• The system where guest data lands

Each campus owns:

• Their own volunteer callers
• Making the calls within the agreed timeline
• Logging outcomes
• Local hospitality touches (notes, coffee invites, connecting to a group)

The central team measures; the campus executes. When central tries to make every call for every location, it becomes a bottleneck. When campuses invent their own process, quality drifts.

Unify your data intake

You cannot coordinate what you can't see. Every campus needs to feed guest information into one place, tagged by location. A common structure:

• One digital connection card used at all campuses, with a required "campus" field.
• A shared list that routes each guest to the right campus's calling team automatically.
• A visible status on every guest: new, contacted, connected, or inactive.

This is where software earns its keep. A tool like ChurchCallerHQ lets the central team build one guest list, assign it to the right campus's volunteers, and see outcomes roll up across every location — so nobody has to email spreadsheets around on Monday morning.

A copy-ready campus call script

Give every campus the same backbone script, then let callers use their own words and reference local details. Here's a template your teams can adapt:

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

[Listen. Respond to whatever they say.]

"That's great to hear. Was there anything you were hoping to find, or any way we can help you get connected?

[If interested:] "We've got a short newcomers gathering after the 10:30 service next week — I'd love to introduce you. Can I text you the details?

[To close:] "Thanks so much for the few minutes. I hope we see you again — and feel free to reach out anytime. Have a great week!"

Keep it under three minutes. The point is warmth and a single easy next step, not a checklist of announcements.

A weekly multi-campus follow-up rhythm

Coordination lives or dies on a repeatable weekly cadence. Here's a template rhythm:

• Sunday afternoon: Guest cards from every campus land in the shared system. Automated thank-you text goes out.
• Sunday evening / Monday: Each campus's list is assigned to its volunteer callers.
• Monday–Tuesday: Calls happen within the 48-hour window. Outcomes logged.
• Wednesday: Campus coordinators review who wasn't reached and schedule a second attempt.
• Thursday: Central team pulls the cross-campus report — contact rate and connection rate by location.
• Monthly: Campus coordinators meet (or hop on a call) to compare numbers and share what's working.

Track the numbers that reveal weak spots

The advantage of a unified system is comparison. When you can see each campus side by side, problems become obvious and fixable. Watch:

• Contact rate — percentage of guests reached by a live person per campus.
• Speed — how many were contacted within your window.
• Return rate — percentage of first-time guests who came back within 30 days.

If one campus has a 70% contact rate and another has 30%, that's not a mystery — it's a coaching conversation about staffing or ownership.

Keep the human touch as you scale

The temptation as you add campuses is to automate more and personalize less. Resist it. The churches that grow healthy multi-site follow-up are the ones that treat volunteer calling as core, not optional. As one ChurchCallerHQ user, Judah Picou of Sam's Test Lab, put it: "This app is the best! I just can't stop calling!" That enthusiasm — a volunteer who genuinely enjoys reaching out — is exactly what scales well when you give it a clear system.

Start small: pick one shared standard, one intake form, and one weekly rhythm. Roll it out to your strongest campus first, prove it, then hand the playbook to the others. Coordination across campuses isn't about controlling every detail — it's about making sure every guest, everywhere, hears a real voice say they're glad they came.