The Square Filter Church Invitations Get Wrong, and What It Costs Attendance

Activity sharing gets adopted when inviting someone takes one familiar action, carries all the essential event details, and gives the recipient a clear next step. For West African churches, that usually means a mobile-friendly event card shared through the messaging apps members already open, backed by one reliable event record.

In April 1970, Apollo 13’s crew faced rising carbon dioxide inside the spacecraft. The lunar module had square filters, while the command module’s available filters were round. Engineers at NASA’s Manned Spacecraft Center in Houston had to make incompatible equipment work using materials already aboard the spacecraft.

NASA engineer Ed Smylie and his team developed an adapter from items available to the astronauts, including plastic, cardboard, a sock, and duct tape. Mission Control then guided the crew through the assembly. The improvised system worked, helping keep the air safe during the journey home. The episode is documented in Jim Lovell and Jeffrey Kluger’s book Lost Moon.

The lesson for church activity sharing is practical: adoption depends on fitting the invitation into the tools members already have. Asking people to learn a separate sharing workflow creates the same kind of mismatch as supplying the right filter in the wrong shape.

Build around the invitation members already send

A member in Accra who wants to invite a colleague to a conference will probably send a short message through an existing conversation. They should not need to copy the venue from one announcement, find the time in another WhatsApp thread, download a flyer, and explain how registration works.

Create one share action on every event page. When tapped, it should prepare a compact invitation containing:

• The event name, date, time, and venue.
• A clear registration or information link.
• A short sentence the member can edit before sending.
• A recognisable image sized for a phone screen.
• The church or branch name, especially when several branches use similar event names.

Keep the shared message useful even when the image fails to load. Dates, venues, and registration instructions should appear as text rather than living only inside a poster.

Church staff also need one authoritative event record. If the time changes, every page and registration flow should reflect the update. This avoids the problem described in The Fourth WhatsApp Thread, and What Its Buried Service Time Could Cost: a message can travel widely while carrying information that is already stale.

Give the recipient a complete next step

A shared activity reaches two people: the member sending it and the friend receiving it. Design for the friend.

The recipient may know nothing about the conference, the branch, or the church’s registration process. The destination page should therefore answer the immediate questions in one view: What is happening? When and where? Who is it for? What should I do next?

Use one primary action, such as “Register for This Event” or “Save Event Details.” Avoid presenting several equal buttons for registration, giving, joining a group, contacting an administrator, and downloading the app. Hick’s Law applies here: more choices increase decision time and make abandonment more likely.

Registration should also avoid unnecessary account creation. Ask only for information the church needs to reserve a place or communicate an important update. After registration, provide a clear confirmation and a share action so the newly registered guest can invite someone else.

ChurchFlow’s conference registration, QR confirmation, branch selection, and bus coordination provide a useful operational foundation for this journey. A member can invite someone into a process that leads toward a real registration record rather than another reply buried in a chat. Church Event Registration: How Kojo Turned WhatsApp Replies Into Reliable Attendance explains why that distinction matters.

Create reasons to share without pressuring people

Members share activities when the invitation feels relevant to a specific person. Generic prompts such as “Share this event” give them little help.

Place the prompt after moments of commitment. Someone who has registered, selected a bus, or saved an event has already decided the activity matters. A prompt such as “Know someone who would enjoy this conference?” connects that decision to a real relationship.

Offer editable starter text rather than a rigid promotional message:

“I’m attending [event name] at on. I thought you might be interested. Here are the details.”

The member can add the personal reason that makes the invitation credible. That small contribution also draws on the IKEA effect: people value and support messages they have helped shape.

Avoid public leaderboards, guilt, or claims that “everyone is inviting friends.” Church invitations carry trust. Manufactured pressure can weaken it.

Measure the path from share to attendance

Counting taps on a share button tells you that someone opened the sharing menu. It does not tell you whether an invitation produced a visit.

Use a simple event trail:

• Record that the share action was opened.
• Attach a privacy-conscious referral identifier to the event link.
• Record when the recipient views the event.
• Connect completed registration to the shared link.
• Compare registrations, check-ins, and attendance by sharing source.

Review the results by event and channel. One congregation may respond strongly to personal WhatsApp invitations, while another sees more registrations from SMS or a church website. Let behaviour guide the next change.

Start with one upcoming event and a small group of members. Watch them attempt the full journey on ordinary phones: open the event, share it, receive it on another device, register, and find the confirmation. Any point that requires explanation needs another pass.

Apollo 13’s adapter succeeded because it respected the materials and constraints already present inside the spacecraft. Church activity sharing follows the same rule. Fit the invitation to members’ existing conversations, then connect that familiar action to accurate event details and a registration path the church can actually track.