Skip to main content
EzyConn

NonprofitIndustries and use cases

AI Chatbot for Churches: Services, Weddings and Hall Hire

Church websites get the same handful of questions, usually in the evening, often from someone who has never been through the door. An assistant trained on your own pages answers them kindly. It also has to know where to stop.

EzyConn EditorialThe EzyConn blog 8 min read Updated

Try EzyConn Free

Read this part first

Two kinds of message must never be handled by an assistant: a safeguarding disclosure, and anything that sounds like a crisis. Both route to the person your own policy names, immediately, and the assistant stops replying. It asks no follow-up questions and gathers no detail.

Put your safeguarding contact and your published crisis numbers in the widget from the first message and on every page, so nobody has to say anything difficult to find them. Build that first, then test it yourself.

Why detection alone is not the plan

Do not rely on the assistant recognising a difficult message. People do not disclose in tidy sentences. They ask about something ordinary and put the real thing in the last line, or type half of it and delete it.

So make the contacts permanent rather than conditional. A named safeguarding contact and your published crisis numbers should be visible whether or not anyone asks. Nobody should have to phrase a message correctly to reach help.

Then escalate generously. A handover that proves unnecessary costs someone two minutes. Follow whatever your denomination requires, and let the assistant do one job: get the person to the right human quickly. The mechanics are in our handover protocols guide, though a church should sit further towards the human than those defaults.

What a church website actually gets asked

Once the limits are set, real value remains. Most enquiries are small and repeated, and many come from people who would never phone.

What they ask
What the assistant does
What time are services on Sunday?
Answers instantly from your site, including any seasonal changes you publish
Is there parking? Is the building accessible?
Repeats your published access, parking and step-free information
What should I wear, and will I have to speak?
Answers from your newcomer page in the same warm words you wrote
How do we arrange a baptism?
Explains your published process and passes the enquiry to the office
Can we hire the hall on a Saturday?
Gives rates, what is included and your conditions, then takes an enquiry
How can I give regularly?
Points to your published giving page. No details taken in chat

Look at the third row. What should I wear, and will anyone make me speak, are the questions that keep people at home on a Sunday. They feel too small to email about and too awkward to ask on a doorstep. Answering them at 9pm on a Saturday does more good than most of what a church website does.

Weddings, baptisms and funerals

These three bring the most enquiries and need the most care. Who may marry in a particular building, what is required beforehand, and what a service costs all vary by denomination, parish and circumstance.

So the assistant repeats your published position and stops. It never tells anyone they are eligible, holds a date, or says a service can go ahead. It takes a name, a way to reach them and roughly when, then passes that to the office or the minister.

Funeral enquiries deserve the lightest touch. Give the assistant a short, plain reply, your phone number, and an instruction to alert a named person straight away. Do not have it ask questions. Someone writing after a death should be speaking to a person within the hour, not filling in fields.

Hall hire is the quiet administrative win

If your church lets rooms, you know how much of the week goes on the same exchange. What does it cost, is it free that Saturday, is there a kitchen, can we bring our own food, do we need our own insurance.

All of that is publishable, so the assistant handles it in one reply instead of four emails across a fortnight. Give it your rates, conditions, what each room includes and the questions you always end up asking, then let it collect an enquiry for whoever keeps the diary. Bookings follow the pattern in our event registration guide.

Giving, without pressure

People do ask how to give, and the answer is usually buried three clicks deep. Let the assistant point to your published giving page and explain the options you offer. Two limits: it never takes card or bank details in a chat window, and it never raises the subject unprompted. A visitor asking about service times should not be asked for money. Our nonprofit fundraising guide covers the wider picture.

Say it is a bot, then say what it costs

Most churches run on volunteers, and the office may open two mornings a week. Say so. The opening message should state that this is an automated assistant, what it answers now, and when a person will read anything passed on. That is more welcoming than a form that promises nothing.

The AI runs GPT-4o and Claude on every plan and replies in many languages, following whatever the visitor types. For a congregation drawn from several communities, that is a real welcome. The free plan is $0 forever with no card: 2 seats, 500 messages a month, one widget, one domain, mobile app, 30-day history. Paid plans are Starter at $25 a month and Professional at $95 a month, with 20% off on annual billing. Annual billing takes 20% off; the ladder is on the pricing page.

Frequently asked questions

What must happen if someone makes a safeguarding disclosure?

It goes to the person your policy names, immediately, and the assistant stops answering. It does not ask what happened, does not ask for names, and does not try to keep the conversation going. Your safeguarding contact and the crisis numbers you publish should be visible in the widget from the first message, so nobody has to disclose anything to find them. Configure this before launch and test it yourself.

Can it help someone in a pastoral crisis?

No, and it should not try. Anything that sounds like crisis, despair or self-harm routes to a named person straight away, with the emergency and crisis numbers your church publishes in the same reply. A bot must never be the only responder to a message like that. If nobody is reachable at that hour, say so plainly and point to services staffed around the clock.

Can it answer wedding and baptism questions?

It can repeat what you publish, and no more. Who may marry in a particular church, and what is required first, varies by denomination, parish and circumstance. The assistant explains your published position, gives your fees where those are public, and passes the enquiry to whoever decides. It should never tell anyone they are eligible, confirm a date, or say a service can go ahead.

Is it strange to have a bot on a church website?

Not if you are open about it. Say in the first message that this is an automated assistant, what it can answer, and when a person is around. Many churches run on volunteers with an office open two mornings a week, and a visitor at 9pm has no idea whether anyone will read a form. An assistant that answers honestly, then says a person will reply on Tuesday, beats silence.

What does it cost for a small church?

Most churches sit comfortably on the free plan: $0 forever, no card, 2 seats, 500 messages a month, one widget on one domain, the mobile app, 30-day history. If you run a busy hall, Paid plans are Starter at $25 a month and Professional at $95 a month, with 20% off on annual billing. Annual billing is 20% off.

Answer the small questions that keep people at home

EzyConn trains on your own pages and pushes anything it should not handle to a named person, through the mobile app on every plan. Free forever, no card.

Start free

Last updated . Nothing here is safeguarding, pastoral or legal advice. Follow your own denomination's safeguarding policy and the requirements that apply where you are. If you or someone you know is in crisis, contact your local emergency number or a crisis line now. View more guides.