Church Digital

The welcome card paradox: why the card isn't the problem

Site checkups · · 6 min read · By Logan Busic, Founder, Church Digital — ran the 2,000-church website study

A lot of welcome card advice tells you to tweak the fields. I'd argue the card isn't where you lose a first-time guest. Here's the assumption worth rethinking, and what to fix first.

Why this matters

A lot of advice on church welcome card best practices assumes the card is where you win or lose a first-time guest, so the fix is always to change the card: fewer fields, a better question, a QR code on the seat back. I think that assumption gets the order wrong. By the time a guest is holding your card, the decision to engage was already made or lost somewhere earlier.

The cost of holding that assumption is that you spend your one volunteer afternoon rewording a form while the actual break, the thing that decided whether a guest ever showed up on Sunday, sits untouched on your homepage. You optimize the last five feet of a journey that leaked at the front door.

At a glance

  • The welcome card comes at the end of a first-time guest's week. The homepage decision comes first.
  • A guest who arrives warm will fill out a plain, reasonable card. A guest who arrives confused won't fill out a perfect one.
  • In our 2026 study of 2,000 church websites, 56.9% of the 1,930 sites we judged had plan-a-visit content, a page a guest can read before Sunday. Make yours one of them.
  • Fix the "what to expect" path first. Come back to the card only after that path is clear.

The thesis

The welcome card is a symptom, not a lever. When card response is low, my honest read is that the guest arrived on Sunday already unsure, not that the card asked for a phone number instead of an email.

Think about the order of events. A first-time guest finds you online, usually on a phone, sometime during the week. They read your homepage. They decide whether they can picture themselves walking in: where to park, what to wear, what happens to their kids, how long the service runs. If that picture is clear, they come, and they come ready to say hello. If it's fuzzy, some never show, and the ones who do arrive guarded. The card catches the tail end of all of that. It doesn't create it.

So the paradox, as I see it, is this: a church with strong card response didn't win it at the card. It won it on the homepage, days earlier, by making the visit easy to imagine. The card just recorded a decision that was already made.

What changes if you believe this

You stop treating the card as a design project and start treating it as a thermometer. Low response is a reading, not a diagnosis. Before you touch a single field, you go look at what a guest saw before they ever sat down.

You spend your volunteer time differently. Instead of A/B testing card wording, you make sure your homepage answers the plain questions a first-time guest actually types and thinks: service times, what to expect, where to park, what to do with kids. If you only check one, check "what to expect". In my view, it's the thing that decides whether a guest arrives warm.

You also stop apologizing for a simple card. Once the homepage does its job, a short, plain card, name, a way to reach you, and one box to check, is all you need. The card stops being the bottleneck because the warmth showed up before it.

The strongest counterpoint

The honest counterargument: cards do fail on their own terms, and some failures are real. A card that asks for a home address, a spouse's name, and a giving pledge on a guest's first Sunday genuinely scares people off. A card with no clear next step, filled out and dropped in a box that no one follows up on within the week, wastes the guest's goodwill. Those are card problems, and fixing them matters.

I still hold the thesis, because those problems are quick to fix. Trim the fields, promise one follow-up, and you've handled the card in an afternoon. What's left, the part I think matters more, lives upstream on the homepage. If you only have one afternoon, spend it there first. Fix the card second.

Common mistakes

  • Treating a redesigned card as proof you've solved connection. You've cleaned one step; the earlier steps still decide the outcome.
  • Adding fields because a staff member "needs" the data. Every field you add asks a stranger to trust you more before you've earned it.
  • Collecting cards with no reliable follow-up. A guest who writes down their number and hears nothing for two weeks learns not to do it again.

Practical takeaway

This week, before you change anything on the card, open your homepage on your phone the way a first-time guest would. Ask one question: could a stranger picture their Sunday morning here, service time, parking, kids, what to expect, without calling anyone? If the answer is no, that's your afternoon's work, not the card. A four-minute homepage review will surface the gap faster than another round of card edits.

Frequently asked questions

What are church welcome card best practices?

Keep it short, ask only for a name and one way to reach the person, give them one clear reason to fill it out, and promise a single follow-up you'll actually do within the week. But the best practice that matters most happens before the card: make your homepage answer what a first-time guest wonders before Sunday, so they arrive ready to say hello.

How many fields should a church welcome card have?

Fewer than you think. Name and one contact method covers the essential job. Add a single optional box, "I'd like to hear about kids' ministry" or similar, only if someone will follow up on it. Every extra field asks a stranger to trust you before you've earned it, and on a first Sunday that trust is thin.

Why aren't guests filling out our welcome card?

My first guess is that they arrived unsure, not that the card is wrong. In our 2026 State of Small Church Websites study, an audit of 2,000 church websites, 56.9% of the 1,930 sites we judged had plan-a-visit content, a page a guest can read beforehand. A guest who couldn't picture the morning shows up guarded, and a guarded guest doesn't hand over their number.

Where this connects in our work

  • /review for a four-minute look at whether your homepage helps a first-time guest picture Sunday.
  • /research for our 2026 study of 2,000 church websites and what a guest actually finds before they arrive.
  • /examples for church homepages that answer the what-to-expect questions well.

Next step

Start with the homepage, not the card. A short review will tell you whether a first-time guest can picture their Sunday morning before they ever pick up a pen.

Related to this read

Worth a click

Keep reading

All insights