A practical buyer's guide: the eight questions that separate a church AI assistant you can trust from one you cannot — grounding, citations, crisis, price, and more.
A lot of churches add a chatbot to their website and find out what it does only after someone complains. The tool answered a doctrinal question with something the pastor never said. Or a person in crisis got a generic response. Or it answered in English when the question was in Spanish. These are not edge cases — they are the normal behavior of a general-purpose AI dropped onto a church site without guardrails.
Choosing a church AI assistant in 2026 comes down to eight questions. Ask them before you demo anything.
This is the most important question. A general chatbot answers from the whole internet and uses your website as a suggestion, not a boundary. That means it will answer a question about baptism using whatever is most common online — not what your pastor actually teaches.
What you want: an assistant that is trained *only* on your church's own published content — your website, your sermons, your PDFs — and that refuses to answer from anywhere else. The boundary should be built into the system, not stated in a prompt that can be overridden.
An AI can sound confident and be completely wrong. The citation is what lets a staff member or a curious member verify the answer. The source link should be part of the answer itself, not a footnote, and it should point to the specific place in the sermon or page where the answer comes from.
A trustworthy assistant admits the limits of its knowledge. If a question is not answered somewhere in the church's own content, it should say so plainly — and then offer a path to a real person. A tool that guesses rather than admits uncertainty is a liability, not an asset.
This is non-negotiable. Before any AI processes a message, there should be a hard-coded check for signals of acute distress. If that check fires, the response should route to the 988 Suicide & Crisis Lifeline, the Crisis Text Line (text HOME to 741741), and the church's own care team — in that moment, not after an AI attempt at comfort. The AI should never attempt a pastoral or clinical response to someone in acute distress.
Ask every vendor: is the crisis gate before the AI, or after?
If any portion of your congregation speaks Spanish — or if seekers in your area do — your assistant needs to detect the language of the question and reply in kind. English-only tools exclude people at the front door.
Everyday questions should be anonymous: no names, no accounts. A person should only be identified when they choose to share their name for a specific reason — a prayer request, a serving inquiry, a plan-a-visit form. And the vendor should not use member conversations to train or improve their models. Ask for that in writing.
Some vendors offer deep IT integrations. That is fine if you have an IT team. If you do not, you need something that goes live with a link or a QR code, works with the site builder you already have, and builds its index by pointing at your sermon library. Setup measured in hours is realistic. Setup measured in weeks is an IT project.
Pricing in this category varies from free (with platform lock-in) to several hundred dollars a month. What matters is what is included at each tier. Some vendors charge extra for bilingual answers, crisis routing, or cited answers. Others include everything in the base plan and price only by congregation size.
The honest landscape in 2026 includes a few meaningful options:
Gloo (Faith Assistant) is a large, publicly traded platform with a free assistant. If you want a focused tool that lives on your own site, cites your own sources, and keeps your data separate from a broader network, Gloo is a different kind of product rather than a direct upgrade or downgrade.
Doctrinally.AI is a smaller lab, also in the cited-answers space. Compare carefully on what comes standard: crisis routing, bilingual answers, and a re-check pass before sending.
OnlineGiving bundles a basic chat with a giving platform. If you are already a customer, it is worth knowing what that chat can and cannot do — but it is not primarily an AI assistant.
Wesley AI and Pastors.ai are both in this space. Run the eight questions above against both.
AskMyChurch is an assistant a church embeds on its own website. Every plan — Base at $99/month, Growth at $249/month, Premium at $500/month — ships with the full assistant: grounding in the church's own content only, a re-check pass on every answer before it sends, cited sources linked to the exact sermon moment, a bilingual English/Spanish response, the crisis gate before any AI, and the ability to capture prayer, serve, and plan-a-visit requests and route them to the right ministry leader.
You pick a tier by congregation size: Base covers under 500 weekend attendance, Growth covers 500 to 2,000, Premium covers 2,000 or more, or multi-campus. There are no feature upgrades to pay for separately.
Founding churches get free setup and a price locked for 12 months, billed monthly.
AskMyChurch is built by Vision Genesis in Knoxville, Tennessee. See a live demo at askmy.church.
Ask where the assistant gets its answers. A trustworthy tool is trained only on your church's own published content — its website, sermons, and PDFs — and will not answer from the open internet or invent doctrine the pastor never taught.
A hard-coded check should run before any AI processes the message. If the check detects acute distress, the response must route to the 988 Suicide & Crisis Lifeline, the Crisis Text Line (text HOME to 741741), and the church's own care team. The AI should never attempt a pastoral or clinical response in a crisis.
AskMyChurch is $99/month for churches under 500 weekend attendance, $249/month for 500 to 2,000, and $500/month for 2,000 or more or multi-campus. Every plan includes the full assistant — there are no feature tiers.
About 30 minutes. There is no IT integration required — the church's site gets a link or a QR code, and the assistant builds its index by pointing at the sermon library. It works with WordPress, Wix, Squarespace, Webflow, Shopify, Framer, and Google Tag Manager.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →