It scales with your repeat questions: an office fielding 15 routine service-time, giving, and volunteer questions a day loses 6+ hours a week it can absorb.
The time an assistant saves scales directly with how many repeated questions your office fields, and you can count that yourself in one week. As a working example: an office that handles fifteen routine questions a day — service times, giving links, volunteer signup, kids check-in — at five minutes each is spending more than six hours a week answering things the church website already says.
That six hours is not ministry. It is inbox triage. Nobody hired an office administrator so she could paste the same giving link forty times a month.
Before you evaluate any tool, pull one week of inbound questions from every channel: office email, voicemail, Facebook messages, the website contact form, texts to staff phones. Tally each one into two piles.
Pile one: questions already answered somewhere in your published content. What time is the Christmas Eve service. How do I get a giving statement. Where does the youth group meet. Is there childcare at the 11:00. Do you have anything in Spanish.
Pile two: questions that genuinely need a person. A grief call. A benevolence request. A member upset about something specific.
Most offices find pile one is the bigger pile. That pile is the assistant's job. Pile two stays with your staff — and reaches them faster, because it is no longer buried under pile one.
AskMyChurch answers only from your church's own website and sermons. That constraint is the whole point: anything you have published, it can field — at 11 p.m. on a Tuesday, on Christmas morning, while your administrator is at her kid's game.
The boundaries matter as much as the coverage. If the answer is not in your content, the assistant says so and hands the conversation to a real person — it never invents an answer. And before any AI response runs at all, a hard-coded crisis check routes signs of acute distress to 988 and the Crisis Text Line, in English and in Spanish. Those messages are never left sitting in a receptionist's inbox on a Sunday night.
Plans are priced by weekend attendance: $99/month under 500, $249/month for 500 to 2,000, $500/month for over 2,000 or multi-campus. The full breakdown is at the pricing page.
Now put that against your audit. If your office spends six hours a week on pile-one questions and you cost that time at $25 an hour loaded, that is roughly $650 a month of staff time going to questions the website already answers — against $99/month for a church under 500. Your numbers will differ. Run them with your own tally; the comparison should be checkable, not hand-waved.
There is a 30-day free trial, a money-back guarantee, and you can cancel anytime, so testing the math against a real month costs nothing.
Saved time only counts if it moves somewhere. In practice the shift looks like this: first-time guest follow-up calls that used to slip, hospital and care visits, volunteer coordination that needs judgment instead of a link. The assistant covers the front door — the front door of your church, always open — so the people on staff can handle the people.
One more effect that does not show up in an hours count: the questions that arrive at 9 p.m. on Saturday. Nobody was going to answer those before Monday anyway. Now a visitor deciding whether to show up Sunday morning gets the service time, the parking situation, and what to do with their kids — before they lose their nerve.
Do not take a percentage claim from anyone, including us. Run the sequence: one-week inbox audit, put the assistant on your site during the free trial, then re-count what still reaches the inbox in week four. The difference is your number, measured on your own church.
Setup details are at /docs, and the product overview is at askchurch.ai.
It scales with how many repeated questions your office fields, so count them yourself over one week. As a working example, an office handling fifteen routine questions a day — service times, giving links, volunteer signup, kids check-in — at five minutes each is spending more than six hours a week answering things the church website already says.
Pull one week of inbound questions from every channel — office email, voicemail, Facebook messages, the website contact form, texts to staff phones — and tally each into two piles: questions already answered in your published content, and questions that genuinely need a person. Most offices find the first pile is the bigger one, and that pile is the assistant's job.
Run your own numbers: six hours a week of pile-one questions costed at $25 an hour loaded is roughly $650 a month of staff time, against $99/month for a church under 500 in weekend attendance. With a 30-day free trial, a money-back guarantee, and cancel-anytime, testing the math against a real month costs nothing.
AskMyChurch answers only from your church's own website and sermons — if the answer is not in your content, it says so and hands the conversation to a real person rather than inventing an answer. Before any AI response runs at all, a hard-coded crisis check routes signs of acute distress to 988 and the Crisis Text Line, in English and in Spanish.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →