Guest follow-up at a church plant

Sunday afternoon the planter reads every Church Center connect card. Monday every guest gets a Clearstream text offering coffee that week. Each coffee is logged as a FlockConnect note shared with the coordinator. Notes left his phone at month nine when he saw they would die with it.

By Caleb Brooks · Published September 2026· 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.

Before you start

You need Church Center connect cards live (or a paper backup at the welcome table), a Clearstream login that is not only on the planter’s personal phone, FlockConnect Starter (or another shared notes place), and a named backup for weeks the planter is gone. Decide the stop rule before you launch: one Monday text, one Wednesday nudge max. Add the coordinator as a shared-notes viewer on day one, not after a crisis.

Why they built it

At 70 people, guest follow-up is personal by default. The planter reads every card and sends every text. The system’s job is not scale; it is survival. His care notes lived in his phone’s notes app until month nine, when the bus-test thought experiment landed: if he got hit by a bus, all of it was gone.

So the workflow’s real centerpiece is not the Monday text. It is that the notes now live somewhere the coordinator can see them. If he is sick, she knows who he has met with and what to pray about. A church plant’s follow-up process has to survive its founder being human. They still unload a trailer into a school cafeteria every Sunday, so follow-up that depends on a sticky note in a jacket pocket fails the same way a missing sound cable fails: quietly, until guests feel ignored.

What they’d do differently

He would add a second admin on every account. He is still the only one on two, and he knows it. He would calendar the end of the plant free year on signup day; the first paid invoice reached his treasurer before it reached him. He would also have started shared notes at month one instead of month nine. The coffee invites were faithful. The memory of them was fragile.

Monday checklist

1. Confirm every Sunday connect card is in Planning Center People with a first-visit date.
2. Send the Clearstream coffee text to each new guest from the church number.
3. Note who replied; book coffees before the week fills up.
4. Log any coffee from the prior week as a FlockConnect interaction note.
5. Share new notes with the coordinator.
6. If the planter is traveling, hand the Monday texts to the coordinator with the soft script written out.

Common mistakes

• Keeping guest texts on a personal phone with no backup sender.
• Logging care only in a private notes app.
• Sending daily nudges when a guest does not reply.
• Leaving paper cards in the trailer until midweek.
• Pasting coffee notes into a group chat for “prayer.”

Field note after the phone notes scare

At month nine the planter searched his phone for a guest from launch Sunday and found nothing. The note had been deleted in a routine cleanup. He moved interaction notes into FlockConnect that week and shared them with the coordinator. The coffee habit was already good. The archive was not.

Field note after a vacation week

The planter left town without a written text script or a second Clearstream admin. Two guests from that Sunday heard nothing until they came back the next week and mentioned it kindly. Now a vacation checklist includes: coordinator can send the Monday text, and open notes are already shared.