ChurchToolStack
Search

First-time guest follow-up at a multi-service church

Every first-time guest at this 2,100-attendance church gets a personal contact within a week. Cards go into Rock on Sunday, volunteers are assigned by zip code Monday, Clearstream texts Tuesday at 2 pm (not Monday at 9, because half the city works nights), and the volunteer calls by Friday.

By Caleb Brooks · Published · Editorial standards · Conflict of interest

Field guide page: steps and costs from hands-on church-tech work, written under a pen name. Church names stay private. See how we write and verify.

What are the exact steps?

  1. Enter every card on Sunday, before Monday

    Paper connect cards (still about 40% of first-time guest info) go into a locked box in the connection office after the last service, and a volunteer enters them into Rock RMS (the church's people database) Sunday afternoon. The online card on the website feeds straight into a Rock workflow. Nothing waits until Monday. Sticky notes on usher clipboards do not count.

  2. Rock assigns each guest to a volunteer by zip code

    Monday by noon, Rock assigns every new guest to a connection-team volunteer based on zip code. Neighborhood assignment beats random lists in a metro where drive time matters. The connection lead checks the 'unassigned' list before lunch. It is usually people who left the address blank.

  3. Clearstream sends the thank-you text Tuesday at 2 pm

    Not Monday at 9 am. Half this city works when everyone else is off: casino floors, hotels, hospitals, the airport. Monday-morning texts woke up people who had just finished twelve-hour shifts. Tuesday at 2 pm stopped the angry replies and raised the reply rate. Clearstream (a church texting tool) keeps texts off personal phones.

  4. The assigned volunteer makes one personal call or text by Friday

    The volunteer marks it done in Rock. If they do not, the step escalates to the connection lead. No guest depends on one volunteer remembering. Soft script, one voicemail max, honor do-not-contact notes the same day they arrive.

  5. Anyone who came back gets invited to the next-steps lunch in week three

    Return visits move guests out of the follow-up sequence and into a personal invitation. The lunch is the on-ramp to membership and serving. Keep first-week touches light so week three does not feel like a pileup.

  6. Review Spanish-congregation handoffs weekly until scheduling is in system

    About 250 people meet at 1:30 in the chapel. Their volunteer scheduling still lives in WhatsApp until a bilingual leader owns a move into Planning Center Services. Guest cards from that service still enter Rock the same Sunday. Do not invent a second follow-up database while you wait for the scheduling fix.

Which tools does this church use?

  • Rock RMS Church database (ChMS)

    Source of truth for guest records; assigns each new guest to a connection-team volunteer by zip code.

    $4.45 per average weekly attendee per year (~$9,100/yr suggested donation at this size) + partner hosting + a full-time admin's salary

  • Clearstream Texting

    Sends the Tuesday 2 pm thank-you text to every new guest.

    ~$200/mo

  • Online connect card (church website) Forms

    Feeds straight into a Rock workflow; paper still ~40% of first-time guest info.

    $0 (on the website)

Common questions

How much does Rock RMS actually cost?

Rock is free and open-source, but the suggested donation is $4.45 per average weekly attendee per year: a little over $9,000 annually at 2,100 attendance, plus partner hosting, plus the salary of the full-time systems admin who runs it. People hear 'free' and forget the salary.

When should you text first-time guests?

This church texts Tuesday at 2 pm. Their first year, Monday at 9 am drew complaints from hospitality workers asleep after overnight shifts. Tuesday afternoon ended the angry replies and raised the reply rate.

What goes wrong when a church copies this workflow?

Three things, in the ops director's words: running Rock without a dedicated admin; running two check-in systems during a migration (they did it for a year: miserable); and letting a giving contract auto-renew without re-bidding processing rates.

Before you start

You need Rock RMS with a real systems admin (not a volunteer who “knows databases”), Clearstream on a plan that can handle weekend volume, a locked box for paper cards, and a connection lead who checks unassigned guests Monday before lunch. If you lack a dedicated Rock admin, do not copy this workflow yet. The ops director’s warning is blunt: people hear “free” and forget the salary.

Why they built it

Half this city works when everyone else is off: casino floors, hotels, hospitals, the airport. The church runs a Saturday 5:30 pm service because it is the only one many of their people can make, and that shaped everything about follow-up. The process has to work for guests whose weeks look nothing like a desk worker’s.

It also has to survive scale. Four weekend services, about 2,100 in attendance, and roughly 40% of first-time guest info still arriving on paper cards. Follow-up that depends on anyone’s memory collapses under that weight, so every step either fires automatically in Rock or has a named owner with an escalation path.

What they’d do differently

They would put a written data-access policy in place for deacons sooner. Right now deacons can see more of Rock than they should. They would calendar the giving contract’s renewal date: they almost rolled into another Pushpay term without re-bidding processing rates. They would not run two check-in systems side by side for a year again.

Their open wound is the Spanish congregation (about 250 people meeting at 1:30 in the chapel) whose volunteer scheduling still lives in WhatsApp. The ops director’s plan is to get it into Planning Center Services by spring, but only once a bilingual leader owns it: “I need a bilingual leader who owns it, not just a tool.”

Monday checklist

  1. Confirm Sunday paper cards from every service (including Saturday and the chapel) are in Rock.
  2. Connection lead clears the unassigned list before lunch.
  3. Spot-check zip-code assignments for odd metro edge cases.
  4. Confirm Tuesday 2 pm Clearstream thank-you is scheduled (not Monday 9 am).
  5. Escalate any Friday calls still open from last week.
  6. Note do-not-contact replies the same day; block further texts.

Common mistakes

  • Monday-morning texts in a night-shift city.
  • Leaving paper cards until the office opens Monday.
  • Running Rock without a dedicated admin.
  • Dual check-in systems during a migration.
  • Measuring success by texts sent while escalations sit untouched.

Field note after Monday 9 am texts

Hospitality workers who finished overnight shifts woke to a cheerful thank-you and replied angry. Moving Clearstream to Tuesday at 2 pm ended those replies and raised real conversations. Timing is pastoral care when half your city works weekends.

Field note after a year of two check-in systems

During a migration they ran old and new check-in together for a year. Volunteers learned neither well. Kids lines slowed. The ops director’s advice: cut over with training, accept a hard weekend, and do not “ease in” with twin systems.