AskMyChurch cites the source on every answer — the link is part of the response, not a footnote. Your church can audit exactly what it tells people.
When someone asks a general retailer's chatbot a wrong question and gets a wrong answer, they return a pair of shoes. When someone asks a church's AI a wrong question and gets a wrong answer about doctrine, grief, or where to go for help — the stakes are different.
A source link is not a nice-to-have. It is how a pastor knows the AI is speaking from the church's actual published teaching, not from the open internet stitching together opinions. It is how a visitor verifies that the answer is real before they decide to walk through the door.
Most AI tools attach a list of links at the bottom of a response. A person reads the answer, forms an impression, and ignores the list. AskMyChurch works differently: the source is woven into the answer itself. If the answer comes from a sermon, the link points to the exact moment in that message. If it comes from a page on the church's site, the link goes to that page. The reader sees where the answer came from before they decide whether to trust it.
This is not a design choice. It is a theological one. A church's assistant should not speak with authority it does not have.
A general chatbot treats your church's website as a hint. It reads your site, then layers in everything else it was trained on — Reddit, theological forums, other churches' statements — and produces an answer that sounds confident and may be completely wrong for your congregation.
AskMyChurch is trained only on your church's own published content: your website, your sermons, your podcasts, your PDFs. Grounding is built into the system, not requested in a prompt. Before any answer is sent, the system runs a re-check pass — it compares the draft answer against your church's content to confirm it holds. If the answer is not supported, the assistant says so and routes to a real person rather than guessing.
"I don't know" is not a failure. It is the correct answer when the correct answer is not in the church's content. AskMyChurch is built to say exactly that — and then offer a hand-off to a real staff member or ministry leader. No dead end. No fabrication.
This matters most for questions that should go to a person anyway: prayer requests, a member in crisis, someone asking to serve. The assistant captures those and routes them to the right team.
Before you put an AI on your church's website, ask this: *Can I see, right now, what source the assistant will cite for a specific answer?*
If the vendor cannot answer that question with a live demonstration, the assistant is operating on faith you have not placed in it.
With AskMyChurch, a church can review its Canon index — the indexed sermons and pages that form the assistant's knowledge — before it goes live. Every answer a visitor receives can be traced back to a specific piece of published content.
Plans are sized by congregation, not by features. Every plan ships the full assistant with Canon — the sermon-indexed, source-cited layer — included.
| Plan | Monthly | Congregation size |
|---|---|---|
| Base | $99 | Under 500 weekend attendance |
| Growth | $249 | 500 to 2,000 |
| Premium | $500 | 2,000+ or multi-campus |
Founding churches receive free setup and a price locked for 12 months. Billed monthly.
Setup takes about 30 minutes. No IT project, no integration beyond a link or QR code. Point it at the sermon library and it builds the index.
One more thing worth naming plainly: AskMyChurch includes a hard-coded crisis gate that runs before any AI response. Messages in English or Spanish that signal acute distress route 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 in those moments. That is also a form of citation — knowing the limits of what the tool should say.
AskMyChurch is built by Vision Genesis in Knoxville, Tennessee. See a live demo at askmy.church.
Citations are built into every answer by default — no configuration required. The source link is part of the response, pointing to the specific sermon moment or page the answer came from.
It says it doesn't know and offers a hand-off to a real person on your team. It will not pull an answer from the open internet or guess.
Yes. AskMyChurch builds a Canon index from your published content — your website, sermons, podcasts, and PDFs — and you can review that index before the assistant is live on your site.
No. The source is part of the answer itself. If the answer comes from a sermon, the link points to the exact moment in that message — visible before the reader decides whether to trust what they read.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →