It is nine on a Thursday night, and Dola is holding her phone the way you hold something you are hoping will ring. Two days ago she posted in the serving group chat: "We really need help with kids ministry this Sunday, please let me know if you can." One person left a thumbs up. Nobody has offered. She is doing the quiet math on whether she can cover the check-in desk and the toddler room at the same time, and she already knows the answer.
Before she decides her people have gone cold, it helps to look at what she actually asked them to do. "We need help with kids ministry" sounds simple, and it quietly hands the reader three jobs at once. First, figure out what help even means this week. Second, decide whether they are the right person for something nobody has defined. Third, raise their hand for a commitment with no edges on it. Most people stall on the first job and feel a small guilt about it, and that guilt comes out as silence. Those are people who care and still could not tell what they were being asked to say yes to.
Now read a different message. "Can you run the check-in desk this Sunday from 9:00 to 10:30?" A person can answer that in the time it takes to read it. One duty. One date. One box of time with a beginning and an end. There is nothing to decode and no way to volunteer yourself into a surprise. You either can or you cannot, and both answers are fine.
That is the shape a good ask takes, and it is the shape Cendance sends. Each person gets their own request, one duty at a time, with two buttons: accept or decline. No thread to scroll, no wondering whether the "we" in the message includes you. Just a clear question and a clear way to answer it.
Then there is Saturday, which has a way of rearranging everyone's week. A kid spikes a fever, a car refuses to start, an aunt arrives from out of town with three suitcases and no warning. The old script for this is a guilty text to the whole group, hoping a stranger covers you. Now a volunteer can propose a swap to a teammate by name. The desk stays covered, the coordinator sleeps, and nobody has to perform their apology in public.
A lot of the yes, it turns out, is decided by timing. A roster you publish three weeks out earns warmer answers than one you post on Thursday, because a yes is easy to give while the calendar still has room in it. Ask someone in early September and they will happily hold a Sunday in October. Ask them the night before and you are competing with everything already on their page. So publish early, and let the reminders stay gentle and boring: one the day before, one the morning of, automatic, so no coordinator spends Saturday night working as a one-person texting service.
And then the part that is easiest to skip and does the most quiet work. People come back when someone noticed they came the first time. A short thank-you that names real people and the real mornings they showed up, said out loud where the team can hear it, does more for next month's roster than any reminder ever will. A volunteer who feels known by name keeps saying yes for years, long after they have forgotten which Sunday it started.
You will find your rosters with your serving teams in the Cendance dashboard, and every volunteer can see what they have said yes to under My Serving Schedule. Publish next month's roster this week, keep each ask small enough to answer in one breath, and watch that quiet chat start filling back up.
