The Sunday St. Andrew's Left WhatsApp Behind

The moment it breaks

Mark had been running St. Andrew's for eight years using WhatsApp groups. One for announcements. One for the prayer chain. One for volunteers. One for each life group. Then one more for each life group's leadership. By last year, he was managing sixteen separate chats, watching notifications pile up at 11 p.m. on Sundays, and watching good people - his volunteers, his prayer warriors - get buried in noise.

'Three weeks ago,' Mark told me, 'someone asked a genuine prayer request in the main group. It was gone in ninety seconds. Buried under jokes and memes.' That's not the kind of community a pastor wants to lead. That's WhatsApp's fault, not his.

He'd tried everything: chat rules (ignored), pinning messages (forgotten), separate admin groups (more chaos). By February, he was sitting in his office on a Wednesday evening, scrolling through yet another thread about the church car park, and thinking that there had to be a better way.

Why announcement boards aren't enough

A lot of churches think the answer is a website or an announcement board. Post the news once, job done. But that's not how community works. Mark's people didn't just need to read announcements. They needed to know when the prayer meeting was on. They needed to sign up for the outreach rota. They needed to see who was bringing biscuits for the new members' welcome event. They needed their prayer requests to exist in a space where they wouldn't vanish in three seconds.

When Komuniti launched, one of the design choices we made was to separate the prayer wall from the chatter. A prayer request isn't a message in a group chat. It's a record. It's something the pastoral team can see, follow up on, even pray through weeks later. Mark saw that distinction immediately. 'The difference,' he said later, 'is that a prayer request feels like it matters.'

The announcement nobody expected

Mark decided to announce the migration during the Sunday morning service. Not to apologise for WhatsApp. Not to beg people to download an app. But to explain what was changing and why it mattered.

'I told them: we're moving to somewhere designed for what we actually do. No ads. No algorithm. No random person's meme interrupting your prayer request. Just us, structured the way our church is actually structured.' He gave people the download link. His leadership team had set up the discipleship journey for new members - the onboarding sequence that helps people understand what each group is for.

By the end of Sunday, 187 people had joined. By the end of the week, 220.

What surprised him wasn't the speed. It was the quality of what came next. The prayer wall filled up with requests that stayed visible. The volunteer rota - which he'd never managed properly in WhatsApp because no one could keep track - suddenly had people signing up for the outreach day and swapping shifts with one another. The new members group became a place where baptism questions and first-steps discipleship actually happened, rather than a chat that moved too fast for anyone to engage.

The features nobody asked for, until they needed them

One detail I hadn't expected Mark to care about was the Givr integration. We'd built it because UK churches operate on Gift Aid, and trying to manually manage tax relief for charitable giving in a WhatsApp group is madness. But Mark hadn't mentioned giving as his problem.

Two weeks after the migration, he emailed back: 'Three people have asked where they can give to the church directly. They didn't want to do it in person or by bank transfer. They just wanted to be able to do it from the app, and for it to sort itself out.' That's when Komuniti stopped being a group chat replacement and started being the thing St. Andrew's actually needed to run.

The Ekklesia link meant his member management wasn't a spreadsheet anymore. The Streamr integration meant people could see a notification when Sunday's service was going live. The discipleship journey meant new members actually knew what each group was for, instead of joining random chats and being confused.

None of these are flashy features. None of them would make a product presentation exciting. But they're the things that happen when someone designs a platform for how churches actually work, rather than trying to make a group chat do something it was never meant to do.

What happens after the app goes live

The real lesson isn't that 220 people downloaded an app on a Sunday. It's what happened next. Mark's elders finally had a prayer wall they could actually use for intercession. His volunteer coordinator could see who was available for the repair day without messaging fifteen people individually. His youth leader could post sermon notes and get comments from parents who were actually engaged, rather than watching announcements disappear into the void.

Mark sent me a video message a month later. He was sitting in his office, same one where he'd been frustrated with WhatsApp six months earlier. 'I'm not exaggerating when I say this has changed how we function as a church.' He meant it. Not because Komuniti is fancy. But because it's built for what he's actually trying to do: lead a community of people who want to pray together, serve together, and know what's happening on Sunday morning without getting lost in noise.