Church AI comes in three kinds. Only one answers your congregation's questions. Here's what separates a good congregant assistant from the rest.
Walk into any church technology conversation right now and you will hear "AI" used to describe at least three different things. They solve different problems. Lumping them together is how churches end up buying the wrong one, or buying nothing because the category feels too messy to sort out.
Here is the honest map.
Sermon-prep tools help the pastor write. They summarize research, suggest illustrations, draft outlines. The pastor is the user. The congregation never sees it. Tools like ChatGPT, Claude, and a growing list of ministry-specific apps live here. Useful. Completely separate from anything on your website.
Admin and giving tools handle the back office: online giving, check-in, event registration, communication workflows. Some of these are adding AI features — a giving nudge, an automated follow-up email. They touch the congregation, but at a transaction layer: money, attendance, scheduling. The conversation is functional.
Congregant assistants are the third kind. This is the one that sits on your church's public website and answers questions from whoever shows up — a newcomer at 11 PM wondering about your Sunday schedule, a member looking for a sermon on forgiveness, a parent who wants to know if there is a kids' program for their age. A congregant assistant is a front door, not a back office and not a writing aid. It is the only kind that works in real time, in public, on behalf of the church.
Most of the confusion in church AI — and most of the fear — centers on this third kind.
A general-purpose chatbot can answer questions about your church. The problem is that it answers from everything it has ever read, and your website is just a hint. Ask it something your site does not cover and it will guess — politely, confidently, wrongly. It might summarize your pastor's theology from a review someone wrote online. It might invent a service time.
A good congregant assistant flips that default. It knows only what your church has actually published: your website, your sermon library, your PDFs, your podcasts. If the answer is not in your content, it says so. That constraint is not a limitation — it is the whole point.
The boundary between your content and the open internet is enforced at the architecture level, not in a prompt. Prompts can be worked around. Architecture cannot. Every answer cites its source, and the link appears with the answer — not as a footnote the person has to go find. That means your pastor is only ever quoted on things he actually said, linked to the moment he said it.
Before the answer sends, a second pass checks it against your published content. Not just "did we search correctly" — does this answer hold up against what the church actually published.
When the content does not support an answer, the assistant says so and connects the person to a real human. No dead ends. No fabrications dressed up as helpfulness.
The crisis check is worth its own paragraph. If a message signals acute distress — in English or Spanish — the system routes immediately to:
This happens before any AI is involved. The assistant does not attempt a pastoral or clinical response.
AskMyChurch is a congregant assistant. That is the only thing it does, and it is built around the specifics above.
It is trained on a church's own published content — website, sermons, podcasts, PDFs. It answers in the church's own words and cites the source in the answer. It answers in English or Spanish, detected automatically. It captures prayer requests, serve interest, and plan-a-visit requests and routes them to the right ministry leader. The canon layer — answers drawn from the pastor's own indexed sermons, linked to the exact moment in the message — is included in every plan.
Setup is a link or a QR code. The assistant builds its index when you point it at your sermon library. No integration project, no IT department required. It works with WordPress, Wix, Squarespace, Webflow, Shopify, Framer, and Google Tag Manager. Most churches are live in about 30 minutes.
Pricing is flat and sized by congregation:
| Size | Monthly |
|---|---|
| Under 500 weekend attendance | $99 |
| 500 to 2,000 | $249 |
| 2,000+ or multi-campus | $500 |
Every plan includes the full assistant and the canon layer. You choose by congregation size, not by which features you want. Founding churches get free setup and a price locked for 12 months.
The data posture is simple: everyday questions are anonymous. A person is identified only when they choose to share information for prayer, serving, or a visit — and that information goes to the church's team. Vision Genesis does not train models on a church's member conversations.
If your church already has an online giving platform or a sermon-prep workflow you like, keep them. AskMyChurch does not replace those. It fills the one gap they all share: the person on your website at midnight, asking a real question, who currently gets nothing.
AskMyChurch is built by Vision Genesis in Knoxville, Tennessee. See a live demo at askmy.church.
Not exactly. A general chatbot draws on the whole internet and treats your site as a suggestion. A church AI assistant built the right way is bounded to your church's own published content — it will not answer from outside that boundary, and it says so when something is not covered.
AskMyChurch runs a crisis check before any AI is involved. Messages signaling acute distress in English or Spanish are routed immediately to the 988 Suicide & Crisis Lifeline, the Crisis Text Line (text HOME to 741741), and the church's own care team. The AI does not attempt a pastoral or clinical response.
AskMyChurch starts at $99 per month for churches under 500 in weekend attendance. Founding churches get free setup and that price locked for 12 months.
Most churches are live in about 30 minutes. There is no integration project — you add a link or a QR code to your site, point the assistant at your sermon library, and it builds its own index.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →