A plain nine-question checklist for buying a church AI assistant in 2026 — grounding, citations, crisis safety, language, data, setup, and price.
If you're shopping for an AI assistant for your church website this year, you'll find three very different things wearing the same label. Knowing which is which saves you from buying the wrong one. Here's a plain checklist — what the categories are, and the questions that separate a tool you'd trust from one you wouldn't.
"Church AI" covers three jobs that don't overlap as much as the marketing suggests:
If you want the third — an assistant on your site — don't be sold the first two. They're useful, but they're not the same purchase.
Ask every vendor these. The good ones answer cleanly; the weak ones change the subject.
The assistant should answer from your website, sermons, and documents — and nothing else. Ask whether that's built into the system or just requested in a prompt. You want it built in. A prompt-level instruction can be ignored; a real grounding system can't reach the internet to begin with.
Every answer should show where it came from, on the answer itself. If you can't see the source, you can't trust it in front of your congregation, and you can't audit what it's telling people.
When the answer isn't in your content, does it admit that and hand off to a person — or does it guess? A tool that always has an answer is a tool that will eventually invent one.
This is the question that matters most. Someone in real distress will message your assistant. It must route them to 988, the Crisis Text Line, and your own care team *before any AI replies* — not attempt a pastoral response. Ask specifically whether the crisis check runs before the AI, and whether it works in every language your congregation speaks.
If you have Spanish-speaking members, an English-only assistant serves half of them. Ask whether it detects and answers in the languages your people actually use.
Everyday questions should be anonymous — no names, no accounts. Someone should be identified only when *they* choose to share their info for prayer, serving, or a visit, and that should go to your team, not the vendor. Ask whether the vendor trains models on your members' conversations. You want: no.
Beyond facts about the church, can it answer "what did the pastor teach about X?" in the pastor's own words, with a link to the moment in the message? This is the difference between a FAQ bot and a real way into your teaching.
You shouldn't need an IT project. A link or QR code on your site and a pointer to your sermon library should have it running the same day. If a vendor needs weeks and integrations, ask why.
Watch for tools that put grounding, citations, crisis safety, or other languages behind a higher tier. Those aren't premium add-ons; they're the baseline for a church. The honest products ship them in every plan.
Print the nine questions. On a call, check off each one as the vendor answers it cleanly. If they can answer all nine without dodging, you're looking at a real congregant assistant. If they get vague on grounding, citations, or crisis — the three that protect your church — keep looking.
AskMyChurch is built by Vision Genesis in Knoxville, Tennessee, and was designed around all nine of these. Try a live demo at askmy.church.
Number four — what happens in a crisis. It's the one place a wrong answer is unforgivable, and the one most tools haven't thought through.
No. Grounding, citations, crisis routing, and bilingual answers are the baseline for a church assistant, not premium upsells.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →