AskMyChurch answers in English or Spanish automatically, serves Spanish-speaking members around the clock, and routes crisis messages in both languages to real help.
A visitor lands on your church website and types in Spanish. Most church chatbots either return an English answer or return nothing useful. AskMyChurch detects the language of the question and replies in the same language, automatically. Your congregation does not change a setting. Your staff does not manage a separate Spanish workflow.
The assistant is trained on your church's own published content — your website, your sermons, your PDFs. That does not change because the question comes in Spanish. The answer still comes from your church's own words, and the source is still linked in the response.
This matters more than most features. If someone in your congregation types a message signaling acute distress — in English or in Spanish — a hard-coded check runs before any AI responds. It routes that person to:
The AI does not attempt a pastoral or clinical response. It gets out of the way. That check runs in both languages, at any hour, without staff intervention.
AskMyChurch does not translate your content into Spanish. It reads your church's published content as-is, in whatever languages you have published it. If your church has Spanish-language sermon content or a Spanish section of your website, that material is indexed. If a question arrives in Spanish and the answer exists in your content, the assistant finds it and responds in Spanish.
If the answer is not in your church's content, the assistant says so — in Spanish — and offers a hand-off to a real person rather than guessing.
When a Spanish-speaking member asks to be connected for prayer, to volunteer, or to plan a first visit, AskMyChurch captures that request and routes it to the right ministry leader. The same routing that works for English requests works for Spanish. No one falls through the cracks because of language.
Nothing about going bilingual adds complexity to the setup. You share the link to your church's content — your website, your YouTube sermon library, your podcast. AskMyChurch builds the index. The assistant goes live in about 30 minutes via a link or a QR code, with no IT project and no integration work. It works with WordPress, Wix, Squarespace, Webflow, Framer, Shopify, and Google Tag Manager.
Every plan includes the full assistant — bilingual support, the crisis gate, Canon (answers from indexed sermons linked to the exact moment in the message), and source citations on every answer.
| Plan | Monthly | Congregation size |
|---|---|---|
| Base | $99 | Under 500 weekend attendance |
| Growth | $249 | 500–2,000 |
| Premium | $500 | 2,000+ or multi-campus |
Founding churches receive free setup and a price locked for 12 months, billed monthly. You pick your plan by congregation size, not by which features you want — every tier ships the same full assistant.
AskMyChurch is built by Vision Genesis in Knoxville, Tennessee. See a live demo at askmy.church.
No. AskMyChurch indexes your church's published content in whatever languages you have published it. If your church has Spanish-language content on your website or sermon library, that material is indexed and the assistant can draw from it. It does not machine-translate your English content.
Yes. The crisis gate runs before any AI response, in both English and Spanish. A message signaling acute distress routes the person to the 988 Suicide & Crisis Lifeline, the Crisis Text Line (text HOME to 741741), and your church's own care team. The AI never attempts to counsel someone in crisis.
Yes. AskMyChurch captures prayer, serve, and plan-a-visit requests and routes them to the right ministry leader, regardless of the language the request comes in.
It is included in every plan. There is no tier required to unlock English and Spanish — the Base plan at $99/month includes the full assistant with bilingual support and the crisis gate.
Updated 2026-06-26 · AskMyChurch by Vision Genesis · Knoxville, TN
See it answer — try a live demo →