Four People Missed the Text. The Family Never Knew.

On a Monday evening in early August one of our members went into the emergency room. The need hit our care system at 6:28 that night. What happened over the next nine and a half minutes is the best case I can make for how church care ought to be built, mostly because so much of it went wrong.

Here's the timeline out of the log. I've taken the names out, but the times are exactly what happened.

• 6:28:36 — the ER admission gets entered. The first volunteer up on the care rotation gets a text asking if she can take it.
• 6:28:54 — she can't tonight, and taps no. Eighteen seconds later the next volunteer is being asked.
• 6:29:55 — he passes too. On to the third.
• 6:30:13 — also a no. The fourth person gets it.
• 6:38:00 — the fourth never answers at all. The window runs out and it goes to staff, three of us at once.
• 6:38:15 — one of our staff accepts, and now a specific human being is on the hook for being with that family.

Four people either passed or never saw it. On a Monday. Right at supper time. And from where that family sat in the ER waiting room, exactly one thing happened: their church showed up.

I don't tell that story to brag on the software. I tell it because on the old setup, that need dies at 6:29 and nobody ever knows it did.

Most churches are running a coin flip

The usual way a care roster works is that a need gets assigned to a person. That sounds responsible, and it hides an assumption: that the person you picked is free right this minute. Your care volunteers are some of the most faithful people in your church and they also work shifts, have sick kids, and put their phones face down at dinner. Any plan that only works when the first person answers isn't really a plan.

And when the coin comes up wrong, one of two things happens. Either nobody finds out, the text scrolls away under a school reminder and a coupon, and the family gets nothing. Or the pastor becomes the backup for every single need, which works fine until the pastor is the one who's done. I've lived both versions. Neither one is the volunteers' fault.

What we do instead

The fix isn't clever. It's borrowed straight from how on-call doctors and 911 dispatchers have handled this for decades, and it comes down to three things.

One need goes to one named person at a time, not to a group text. Group texts spread responsibility around until it evaporates.

If that person doesn't answer inside a set window, it moves on by itself. Nobody has to notice, remind, or chase anybody down. On that Monday night, three passes cost the family a grand total of ninety-seven seconds.

And it keeps climbing until an actual human says yes, with staff sitting at the top of the ladder for the nights when nobody below can. That's the difference between a church that usually responds and a church that always does.

It's easier on the volunteers, not harder

I expected this to be about protecting families. What I didn't expect was how much the team liked it.

When one person is solely responsible for a need, they carry a low hum of dread about missing it, and that dread is a big reason people quietly rotate off care teams. Now if somebody misses a text, nothing bad happens. It just moves. Saying "not tonight" costs one tap and doesn't require an explanation or an apology. The folks who passed that Monday are all still on the rotation and still taking needs, and I think that's connected.

There's a second thing I didn't see coming. When needs spread across the whole team instead of piling onto your two most dependable people, a family in a rough stretch hears from four different church members over a month instead of one worn-out one. That lands differently. It feels like the church came, not like one nice lady came.

Why a spreadsheet can't do this

I'll be honest about the catch. This whole thing is a timing mechanism. Something has to notice that fifteen quiet minutes went by and do something about it, every time, including at 6:38 on a Monday and during the week your care coordinator is at the beach. A person can run it for a while. A person also sleeps and eventually resigns, and when they do the ladder goes with them.

That's the part we ended up putting in software, which became CarePilot. The computer keeps the clock. The people do the part only people can do, which is show up at the hospital.

If you want the bigger picture of what we changed and the first eighteen days of numbers, that's in How We Stopped Dropping Care Needs. And if you're wondering whether your church is quietly running on the coin flip, Is Your Church Running on You? is a fair place to start.