An assistant answers only from what you publish. The checklist: real text pages for times, kids, parking, next steps, staff contacts, giving, and sermons — which is also just good website hygiene.
AskMyChurch answers only from your church's own website and sermons. That constraint is the product's honesty — it can't put words in your church's mouth — but it means the quality of the answers is set by the quality of what you publish. Here is the content checklist, and the pleasant surprise in it: everything on this list is just good website practice. Write it for the assistant and you've written it for every human visitor, every search engine, and every AI engine that ever looks at your church.
1. Service times — as text, on a page. Not a graphic, not a PDF, not only in the footer. A page that says, in words, when services happen, how they differ (traditional, contemporary, bilingual), and how long they run. If you're multisite, per campus.
2. Kids and youth. The page parents check before ever visiting: age groups, check-in process, where to go the first time, safety basics, what time youth group meets. Parents ask these questions at night, specifically, and rarely by phone.
3. Plan a visit. Parking (which lot, which door), what to wear, what happens in the service, where to get coffee. The questions people are embarrassed to ask a person are the ones they will happily ask a website.
4. Next steps. Baptism, membership, classes — what they are, when they run, how to start. If the answer is 'talk to Pastor Dave', publish that, with a way to reach him.
5. Staff and contacts. Who leads what, and how to reach the office. An assistant routes prayer requests, serve interest, and visit plans to the right leader — but the right leader has to exist on a page.
6. Giving. How to give, where the money goes in broad strokes, how to get a statement. These questions carry mild awkwardness for the asker, which makes an assistant the preferred channel.
7. Beliefs. What your church teaches, in your own words. Paired with posted sermons this gets stronger: the Canon layer indexes new sermons automatically each week and answers teaching questions from your pastor's actual preached words, cited to the minute.
Nothing embarrassing — that's the design. The assistant says your content doesn't cover the question and hands the person to a real human. Every one of those handoffs is logged effort-free content strategy: a real question your site couldn't answer, asked by a real person. Most churches discover their gaps aren't exotic — it's the baptism page nobody wrote and the youth schedule living in a PDF.
Write the seven pages first; they cost an afternoon or two and help everyone. Then the assistant — about thirty minutes with a link or QR code — turns those pages into answered questions at any hour, in English or Spanish automatically, with every answer citing the page it came from. Plans are $99, $249, or $500 a month by weekend attendance. The better your site, the better any of it works — which is the most honest sales pitch a website tool can make.
AskMyChurch answers only from your church's own website and sermons — it never fills gaps from the open internet. A question your site doesn't answer gets an honest 'that's not in our content' and a handoff to a person. So the pages you publish are the assistant's entire vocabulary.
Facts trapped in images and PDFs — a service-times graphic, a schedule flyer, a ministry PDF. Text on a real page is what search engines, screen readers, and your assistant can all read. If it matters, it belongs in page text.
For most churches, an afternoon or two. Seven short pages cover the bulk of real visitor questions, and every one of them helps human visitors regardless of whether you ever add an assistant.
The assistant's unanswered questions are the list. Every handoff to a human marks a question your content couldn't cover — review those and write the missing page.
Updated 2026-07-11 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →