Your Digital Greeter Never Sleeps: Why 24/7 Availability Is the New Baseline

There is a story Jesus told that begins with a knock at midnight.

A man's friend arrives from a journey, hungry, and the man has nothing to put in front of him. So he walks to a neighbor's house in the dark and knocks and asks for three loaves of bread. The neighbor calls back through the door: it's late, the door is locked, the kids are asleep. You know the rest. The knocking wins.

The parable is about prayer, not hospitality, and we are not going to pretend otherwise. But the scene it opens with has not aged a day. A need shows up at midnight. Midnight does not check anyone's office hours first. And the whole story turns on a single question that every church still faces, thousands of years later, in a form Jesus' listeners could never have imagined:

When someone knocks at midnight, does anything answer?

The knock sounds different now

Here is what the midnight knock looks like in 2026. It is 2:13 on a Tuesday morning, and someone in your town cannot sleep. Maybe it is grief. Maybe it is a diagnosis, or a divorce, or the specific 2 AM variety of dread that does not have a name. Maybe it is nothing dramatic at all, just a person who has been meaning to find a church since spring and whose mind finally circled back to it in the quiet.

They pick up the phone that is already on the nightstand. They find your church, the one they drive past on the way to work. And they have a question. What time is the service. Whether they can just sit in the back. Whether the divorce thing will be weird. Whether anyone will make them stand up and say their name.

For nearly all of church history, the answer at 2:13 AM has been the same answer the neighbor gave through the locked door. It's late. Come back tomorrow. Except the modern version is quieter than that. The modern version is a website that says nothing at all, and a person who closes the tab and does not knock again.

We have written before about what happens at 11 PM on a Saturday night, when the stakes are a visit the next morning. This post is about something broader than one night of the week. It is about a shift in what people expect from every organization they interact with, a shift that happened without churches getting a vote, and what it actually takes to meet it.

The standard nobody asked churches to meet

Salesforce has been surveying consumers about their expectations for years, and one finding has become a kind of load-bearing statistic for anyone who thinks about how organizations communicate: 64% of consumers, and 80% of business buyers, expect companies to respond to and interact with them in real time.¹

Read that again with a church hat on. Not "within two business days." Not "when the office reopens." In real time.

The instinctive objection is the right place to start: a church is not a company, and a visitor is not a customer. True, and we would go further. The stakes are higher. A company that responds slowly loses a sale. A church that responds slowly may lose the one moment a person worked up the nerve to reach toward God, or toward community, or just toward something that felt like help.

But here is the part that matters whether or not you accept the comparison. The person on the other end does not maintain two sets of expectations, one for companies and one for churches. They have one set, and it was formed by everything else in their life. Their bank answers at 2 AM. Their pharmacy app answers at 2 AM. The airline rebooked their flight at 2 AM without a human involved. By the time they land on your church's website, real-time response is not a delight. It is the floor. It is what "open" means now.

Churches are held to that standard whether or not they know it, and whether or not it is fair. The visitor does not consciously think "this church failed to meet my service-level expectations." They just feel, faintly, that nobody is home. And a church where nobody seems to be home is a church that is easy to not visit.

When people actually reach out

If the knocking only came during office hours, none of this would matter. It does not.

Start with the sheer size of the crowd at the door. Grey Matter Research has estimated that more than 17 million Americans who do not regularly attend any place of worship visit a local church's website in a given year.² That is not your members checking the potluck schedule. That is an enormous, mostly invisible population of unchurched people quietly looking churches up, on their own schedule, which is to say on evenings, on weekends, on lunch breaks, and in the middle of the night.

Then look at when your website works hardest. When one church website platform analyzed traffic across thousands of its client churches, it found that the highest-traffic day is Sunday itself.³ People are checking service times and children's ministry details in the exact hours when every staff member and volunteer you have is fully occupied inside the building. Your busiest greeter station is the one that has never once been staffed during its rush.

Now put those two facts next to the average church office. Many churches, especially smaller ones, keep office hours something like Tuesday through Thursday, nine to two. That is roughly 15 hours a week of "someone might answer," against 168 hours a week of "someone might ask." The overlap between when your church can respond and when your community actually reaches out is a sliver, and the sliver does not include Sunday morning, Saturday night, or 2 AM. It mostly includes hours when the people with questions are at work.

None of this is a criticism. It is arithmetic. No congregation can staff a desk around the clock, and no one should ask them to. But it is worth seeing clearly that the schedule most churches keep was built for a world where the front door was made of wood.

The window closes fast

There is a second problem stacked on top of the first, and it is about time.

In 2011, a research team audited how quickly 2,241 American companies responded to a brand-new inquiry from their own websites. The results were bleak: the average response took longer than a day, and nearly a quarter of the companies never responded at all. But the sharpest finding was about speed. Firms that reached out within an hour of the inquiry were nearly seven times more likely to have a meaningful conversation with that person than firms that waited even an hour longer.⁴

That is commercial research, and we should translate it honestly rather than just borrowing its authority. What it measures is the decay of intent. A person who fills out a form is briefly, genuinely open, and that openness has a half-life measured in minutes, not days.

For a church visitor, the thing decaying is not intent. It is nerve.

Anyone who has ever worked up the courage to walk into an unfamiliar church knows this from the inside. The decision to reach out, even just to type a question into a website, costs something. It is a small act of vulnerability, and it comes with a small window. Answer inside the window and the person feels met. Let the window close, and they do not simply reschedule their courage for Thursday between nine and two. Very often, they file the whole thing under "maybe someday" and someday quietly never comes.

Churches already know a version of this truth. The follow-up research we covered in the 48-hour rule has been saying it for forty years: reach a first-time guest within a day or two and they return at several times the rate of guests you reach late. What has changed is where the clock starts. It used to start when someone walked out of your building. Now it starts when someone types a question into your website, days or weeks before any visit, at an hour when the building is dark.

What this does not mean

Let us head off the wrong conclusion, because it is the one church leaders reach first and it leads straight to burnout.

This is not an argument for your pastor answering messages at 2 AM. It is not an argument for a volunteer rotation covering the website on Saturday nights, or for anyone's phone buzzing on the nightstand. The psalmist says God grants sleep to those he loves, and we take that at face value. A pastor doom-checking a church inbox at midnight is not a hospitality strategy. It is a resignation letter with a long fuse.

It is also not solved by the standard workarounds, and it is worth being honest about why:

• The contact form that promises a reply "within 2 to 3 business days" is a polite way of telling a person at 2 AM that nobody is home. Most people close the tab instead of filling it out, and the ones who do fill it out have often talked themselves back down by the time the reply arrives.
• The auto-reply that says "Thanks! We'll get back to you soon" answers nothing. It is a doorbell that plays a recording of someone saying they heard the doorbell.
• The FAQ page is genuinely useful and every church should have one, but it can only answer the questions someone thought to write down in advance. The questions visitors actually ask are endless, specific, and frequently too personal to appear on any page. "Do you have a wheelchair ramp at the side entrance" is not in your FAQ. Neither is "my son has autism and the last church made it hard."
• Social media DMs depend entirely on who happens to have the login and whether they happened to look. Ask any church how many messages are sitting unread in a Facebook inbox nobody has opened since Lent.

Every one of these is a way of managing the gap. None of them closes it. For most of church history, that was simply the deal: limited people, limited hours, and a locked door at midnight, with a note pinned to it if you were diligent.

It is not the deal anymore.

A greeter at the door, day or night

This is the gap Greetyr was built for, so let us tell you plainly what it does and does not do at 2:13 AM.

Greetyr is a digital greeter that lives on your church's website. When the person who cannot sleep types their question, it answers. Not with a canned menu of buttons, and not with the internet's generic guesses about churches, but from your church's own material: your service times, your traditions, your kids' check-in process, what you have actually said about yourselves. It answers the question that was asked, in plain language, with the warmth of a good greeter and the restraint of one. When it genuinely does not know, it says so and points the person to a human being instead of inventing an answer, because a confident wrong answer at 2 AM is worse than no answer at all.

If the person wants your church to know they were there, the greeter offers a simple card where they can share their name and how to reach them. That only happens because they choose it. Nobody gets scraped or tracked into a database for asking about parking.

And then, this is the part that makes the whole thing a ministry tool rather than a gadget, the conversation is waiting for your team in the morning. Summarized, intact, with anything urgent flagged so it does not sit in a pile. The 2 AM question gets a 2 AM answer, and the human follow-up, the part that turns a stranger into a guest, happens at 9 AM with full context, written by a real person from your church, inside the window while it is still open.

What it does not do: it does not counsel people in crisis, it does not pretend to be your pastor, and it does not replace a single human being at your actual door on Sunday. When a conversation touches something that needs a person, its job is to say so, warmly, and to make sure your team sees it first thing. The greeter at the digital door exists to get more people to the wooden one.

That is the whole idea behind the phrase we keep coming back to: day or night. Not because the night shift is where the numbers are, although Sundays and evenings are exactly where the numbers are. Because the knock does not schedule itself, and the answer should not have to.

Neither slumber nor sleep

Church people of every tradition have been singing the same line for well over two thousand years: he who keeps Israel will neither slumber nor sleep. Psalm 121 is prayed in cathedrals and camp chapels, at bedsides and gravesides, in every denomination that opens the book at all.

No piece of software belongs in that sentence, and we are not putting ours there. The One who keeps watch over your congregation was doing it long before websites and will be doing it long after.

But there is something worth noticing in the fact that the church has always believed in a welcome that does not keep office hours. It is in the psalm. It is in the parable of the man knocking at midnight, who does not go home empty-handed. It is in every tradition's version of the porter, the greeter, the usher, the person whose entire job is to stand at the threshold so that no one arrives unnoticed. The church has never actually believed that welcome should sleep. It has just never had a way to keep the digital porch light on.

Now it does. The assurance the psalm gives about God, the visitor at 2:13 AM is quietly wondering about your church: is anyone keeping watch?

For the first time, your website can answer yes.

Frequently asked questions

Do churches really need 24/7 availability?

The expectation already exists whether a church builds for it or not. Salesforce's research found 64% of consumers expect organizations to respond in real time, and church website traffic peaks at exactly the hours no church office is staffed, including Sunday mornings and weekend evenings. The choice is not whether visitors will reach out at those hours. It is whether anything answers when they do.

Isn't this just a chatbot for churches?

No, and the difference is the whole product. A generic chatbot deflects, collects emails, and answers from the open internet. A digital greeter answers from your church's own content, knows when to say "I don't know," hands anything sensitive to your team, and treats the conversation as the beginning of an in-person relationship rather than the end of a support ticket. Its job is to get people through your physical doors, not to keep them on a screen.

What questions do visitors actually ask in the middle of the night?

Mostly practical ones with something personal underneath. Service times and what to wear, but also whether kids are safe and where they go, whether someone who has been away from church for twenty years will feel out of place, whether communion is open, whether the building is accessible, and questions specific enough that no FAQ page could anticipate them. The late hour is not incidental. Night is when people ask the questions they would not ask out loud.

Will a digital greeter replace our welcome team?

No. Nothing that happens on a screen replaces the person who learns a name, hands over a cup of coffee, or walks a nervous family to the children's wing. The greeter covers the hours no human team can cover and makes sure your human team knows who is coming. Sunday morning hospitality is still the work of your people. This just makes sure more people show up for them to welcome.

What happens to the conversations overnight?

They are waiting for your team in the morning: summarized, complete, and flagged if anything urgent came up. If a visitor chose to share contact information, it is attached. Your staff follows up personally, with full context, usually within the window where follow-up actually works.

---

Greetyr is a digital greeter for church websites. It answers visitors' real questions from your church's own content, day or night, and points every one of them toward the people in your building who can take it from there. This post builds on our earlier essays about Saturday night at the digital door and why Sunday morning is too late.

Footnotes

1. Salesforce Research, State of the Connected Customer, second edition (2018), a survey of over 6,700 consumers and business buyers worldwide: 64% of consumers and 80% of business buyers said they expect companies to respond to and interact with them in real time. The finding was aggregated for church audiences by CommunicateJesus in "12 Essential Statistics to Shape Your Church's Website." See: salesforce.com/research and communicatejesus.com. ↩

2. Grey Matter Research, "How many people use church websites, and for what purposes?" Phoenix, AZ. The study, conducted among a demographically representative sample of American adult internet users, estimated that more than 17 million American adults who don't regularly attend worship services visit a local place of worship's website in a given twelve-month period. See: greymatterresearch.com/online-church. ↩

3. Ekklesia 360, analysis of aggregate church-website traffic across its client churches, which found that visits peak on Sundays as prospective and current attendees check service details before deciding whether to attend. We unpack the implications in Sunday Morning Is Too Late. See: ekklesia360.com. ↩

4. James B. Oldroyd, Kristina McElheran, and David Elkington, "The Short Life of Online Sales Leads," Harvard Business Review, March 2011. The team audited 2,241 U.S. companies by submitting a web inquiry and timing the response: the average response among companies that replied took over 24 hours, and 23% never responded at all. Companies that contacted a lead within an hour were nearly seven times more likely to qualify it (have a meaningful conversation with a decision maker) than those that waited even an hour longer. Commercial research, so translate it carefully to a church context; what it measures is how quickly a moment of openness decays. See: hbr.org. ↩