Four things: a closed corpus (your site and sermons only), a re-check of every answer before it sends, clickable citations, and an honest 'I don't know.'
Four things stop AskMyChurch from making things up: it can only answer from your church's own website and sermons, every answer is re-checked against those sources before it goes out, every claim shows where it came from, and when the sources don't cover a question it says so and hands the conversation to a real person. There's no fifth trick — the whole product is built around those four.
Here's how each one works.
Most chatbots are trained on the open internet, which is why they can confidently describe a service time your church has never held. AskMyChurch is closed on purpose. When we build a church's assistant, its knowledge comes from exactly two places: the church's own website and the church's own sermons. That is the entire universe of things it can say.
If your site says the food pantry opens Tuesdays at 9am, that's the answer a visitor gets. If your site says nothing about a food pantry, the assistant has nothing to say about one — and it won't fill the gap with a guess.
This matters more for a church than for a store. A wrong store hour is an annoyance. A wrong answer about what your church teaches puts words in your pastor's mouth.
A closed corpus by itself isn't enough. An AI can still take two true sentences from your site and stitch them into a claim you never made. So AskMyChurch runs a second, separate check on every answer before a visitor sees it: the drafted reply is compared against the source material, and if it says anything the sources don't support, it doesn't go out.
This check runs on every reply in every conversation, in real time — no sampling, no weekly audit that catches the mistake after a visitor already saw it.
Every answer carries its receipts. When the answer comes from your website, it links the page. When it comes from a sermon, it links the recording at the minute your pastor said it — one click and the visitor hears the actual words in the pastor's own voice. We call this layer Canon, and it exists so nobody ever has to take the AI's word for anything.
That's a higher bar than "the AI is usually right." A visitor who can check the source doesn't have to trust the software at all. They're trusting the church, which is who they came to talk to in the first place.
When the sources are silent, AskMyChurch says so plainly and offers to connect the person with someone at the church. It never invents an answer to keep a conversation going.
We describe the product as the front door of your church, always open. A front door's job is to get people to a person. An assistant that admits its limits and hands off to a human is doing exactly what it was built for.
If someone writes anything about harming themselves, hard-coded crisis routing responds before any AI is involved: 988 and the Crisis Text Line, in English and in Spanish. That path is fixed code that runs ahead of the AI, so it behaves the same way every single time. The rest of the assistant is bilingual too — English and Spanish, with the same source rules in both languages.
The fastest way to check all of this is to ask the assistant something your website doesn't answer, and watch it decline. We've already built working previews across six metros — 84 in Atlanta, 79 in Nashville, 63 in Charlotte, 60 in Columbia, 53 in Charleston, 38 in Knoxville — each one waiting for its church to claim it at askmy.church.
Pricing is by weekend attendance: $99/month under 500, $249/month for 500–2,000, $500/month for 2,000+ or multi-campus. Every plan starts with a 30-day free trial, carries a money-back guarantee, and you can cancel anytime.
No. It answers only from your church's own website and sermons, and when those sources don't cover a question, it says so and offers to connect the visitor with a real person at the church.
Before any reply reaches a visitor, a separate check compares it against the church's source material, and anything the sources don't support doesn't go out. This runs on every reply in every conversation, in real time.
Yes. Website answers link the source page, and sermon answers link the recording at the exact minute the pastor said it, so a visitor can hear the words in the pastor's own voice.
Hard-coded crisis routing responds before any AI is involved, sharing 988 and the Crisis Text Line in both English and Spanish. That path is fixed code, so it behaves the same way every time.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →