The FAQ Your Sunday Bulletin Can't Answer
There is a car in the far corner of the lot with the engine still running. A woman sits in the driver's seat. Behind her, strapped into a car seat, a baby has finally fallen asleep. She can see the front doors from where she is parked, and she has been looking at them for a while now.
Her phone is in her hand. She is not texting anyone. She is scrolling the church's website hunting for the word nursery, and she is not finding it. She finds a sermon series title. She finds a photograph of the building taken in summer, when the flower beds looked good.
Then she puts the car in reverse.
Nobody inside that building will ever know she was in the lot. She will not appear in a count. She will not fill out a card. The pastor who prayed that morning for God to bring visitors will never learn that one came within sight of the door and drove home.
I helped produce bulletins for 15 years, and every one of them was written for the people already in the room. The sermon series title. The potluck sign-up sheet. A reminder about which lot to park in during construction. All of it useful, and all of it written in a shared dialect that quietly assumes you already belong here. Meanwhile a different set of questions circled the building every Sunday without ever landing, because the people holding them were never going to raise a hand and ask. They decided in the car instead. Sometimes they decided not to come in at all.
A church website FAQ is the page that answers what a stranger needs to know before they walk through your doors, not a summary of announcements for people who already walked through them.
That distinction sounds small. It is the whole thing.
The questions insiders never think to write down
I expected the hard questions to be the theological ones. I had answers ready for those. I had books on the shelf for those. Across 15 years of pastoring in Ontario, the questions that actually kept people in the parking lot turned out to be logistical, and they were embarrassing to ask. Not embarrassing because they are silly. Embarrassing because asking one out loud announces that you are new, and being visibly new is the exact thing a nervous visitor is trying to avoid.
Here are five real ones, the kind that rarely make it onto a church website:
- Is there a nursery, and will someone I have never met be holding my baby?
- Is the building wheelchair accessible, and is the accessible entrance the same door everyone else uses or a side door around the back?
- What do people actually wear? Not what the website says is fine, but what will make me feel out of place if I get it wrong.
- Will I be asked to stand up, raise my hand, or be introduced as a visitor?
- What happens if I arrive ten minutes late? Will I have to walk in front of everyone?
Lay those five side by side and something surfaces that none of them says on its own. Not one is about doctrine. Not one is about denomination or service length. Every single one is a question about exposure. Will I be seen before I am ready to be seen.
The most important question on a church website is usually the one nobody is willing to ask out loud.
What a bulletin answers versus what a visitor is asking
The gap is easiest to see side by side.
The bulletin says: Sunday worship at 10:30 a.m. The visitor is asking: If I get there at 10:38, is that a disaster?
The bulletin says: Nursery available during the service. The visitor is asking: Who staffs it, are they screened, and can I stay in the room the first time?
The bulletin says: Come as you are. The visitor is asking: Yes, but what are people actually wearing.
The bulletin says: Join us for coffee after the service. The visitor is asking: Can I leave right after without anyone stopping me?
The bulletin says: We would love to meet you at the welcome desk. The visitor is asking: Is there a way to visit without being introduced?
The first column is written by someone who belongs. The second column is written by someone deciding whether they can.
Why a chatbot belongs here, and why most people get it wrong
When a pastor asks me about putting AI on the church website, the picture in his head is almost always the same. A little window in the corner, answering service times. Giving links. The office phone number. Those are fine answers. They are also the answers your site already carries, and a visitor can dig them out in about nine seconds.
The real value is different.
It is 11 p.m. on a Thursday. The house is quiet. Somebody is lying in bed with a phone above their face, and they type the sentence they would not say in a foyer: is the building wheelchair accessible. There is no receptionist watching their expression. Nobody writes down that they are new. They get a plain answer, they close the tab, and no human being learns that the question was ever asked. That privacy is not a technical feature. It is pastoral.
I say this as someone who spent 15 years in software engineering before the 15 years of pastoral ministry, and who came back to engineering specifically to marry the two. The useful question is never "what can the technology do." It is "what does this person need in order to take one more step toward a real human being."
The bridge principle
This matters more than any feature list, so I want to be direct about it.
AI is a bridge to real people. It is never a replacement for pastoral care, counseling, medical advice, or legal advice. A chatbot on a church site should answer the logistical question honestly, and the moment a conversation turns toward grief, crisis, doubt, or anything that needs a human being, its job is to hand off to one. Say who that person is. Offer the phone number, the prayer request form, the email that a real staff member reads. Never let a machine pretend to be a pastor. Never let it hold someone who needs to be held.
Everything we build at ChurchWiseAI is built on that rule, including the hard cases. If a visitor asks a question the church has not answered, the right response is "I do not know, but here is who does," not a plausible guess. A confident wrong answer about your nursery policy costs you the visit. A confident wrong answer about anything spiritual costs more than that.
What to do this week, even without any software
You do not need to buy anything to fix most of this.
Sit down with three people who joined your church in the last two years and ask them one question: what were you nervous about before your first visit? Then stop talking and let the silence do its work. Write down exactly what they say, in their words, not in yours.
Then put those answers on a page on your website, plainly worded, no church jargon.
Google has been clear that there is no separate checklist for showing up in AI-generated answers beyond the ordinary work of publishing genuinely helpful, first-hand content. A page that honestly answers what people are actually typing into search tends to do well in both places. That is convenient, and it is not the reason to do it.
The reason is the woman in the car. She is in a parking lot right now, engine running, baby asleep in the back, and her phone is the only thing she is willing to ask.
Frequently asked questions
What questions do visitors ask before coming to a church for the first time? In my experience the most common ones are logistical rather than theological: nursery availability and childcare safety, wheelchair and stroller accessibility, what people actually wear, whether visitors are singled out or introduced, and what happens if they arrive late. These are questions about exposure and comfort, not belief. Most church websites answer none of them directly.
What should a church website FAQ page include? Start with the questions newcomers are too self-conscious to ask in person, then add the standard logistics (service times, address, parking, what the service is like, how long it lasts). Write each answer so it stands on its own without requiring another page. Avoid insider language such as ministry names or acronyms that only regular attenders would recognize.
Can a chatbot replace a church greeter or welcome team? No, and it should not try. A chatbot's job is to answer the low-stakes question privately so that a nervous person feels ready to meet an actual human, and then to hand off cleanly when the conversation needs a person. Greeters, pastors, and prayer teams do work that no software does.
Is it safe to put AI on a church website? It is safe when it is honest about its limits. That means it says "I do not know" instead of guessing, it never offers counseling or medical or legal advice, and it routes anything sensitive to a named staff member with real contact information. Ask any vendor how their system behaves when someone in crisis types into the chat window, and listen carefully to the answer.
How much does a church chatbot cost? ChurchWiseAI is priced as an affordable monthly plan sized for small and mid-size congregations rather than as an enterprise contract. Current tiers and what is included are listed on churchwiseai.com/pricing. If your budget is genuinely tight, tell me and we will talk about it honestly.
If you want help
If your website does not answer the five questions above, that is fixable, and you can start this week without spending a dollar. If you would rather have a conversation about it, book a call with me through churchwiseai.com and we will look at your site together. I would rather talk with you about what your visitors are actually asking than sell you a feature you do not need.
John Moelker is an engineer (15 years) and pastor (15 years), founder of ChurchWiseAI and WiseAI Agency.