By default, no. SleekAI is configured to refuse contested doctrinal questions and instead route visitors to a pastoral conversation. Salvation, communion practice, baptism mode, end-times views, and political-adjacent questions all get a polite redirect to a real pastor. The system prompt holds the line even when the visitor pushes. The bot does answer factual questions about what your church practices ("We baptize by immersion", "We celebrate communion on the first Sunday of each month") when those are on your published pages, because that's information, not interpretation.

The bot collects the request in conversation, asks whether it's confidential or shareable with the broader prayer team, and asks whether the requester wants follow-up contact. The data lands in a WordPress custom post type or routes through the JS API to your existing prayer-list system. Confidential requests stay confidential. Shareable requests can be auto-routed to the printed Sunday prayer list. The pastoral care team sees everything, the broader congregation only sees what was marked shareable.

Yes. SleekAI is multibot, so the youth section can have a bot with a different tone and a different scope. The youth bot answers questions about Wednesday night programs, retreats, and youth small groups. The kids bot focuses on check-in, age-appropriate programs, and parent FAQs. The main site bot handles services, baptism, membership, and prayer. Display conditions route visitors to the right bot based on page or URL pattern, and each bot has its own system prompt scoped to its area.

Yes. SleekAI's display conditions support post type, taxonomy term, user role, logged-in state, and URL pattern. Memorial pages, funeral livestream pages, and grief support pages can be excluded entirely so a chatbot pop-up never appears in a tonally inappropriate moment. The same logic keeps the bot off legal-notice pages, the privacy policy, and the careers section if you don't want it there. Each location runs in or out independently.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter, and the model bills you directly. There's no per-message markup from SleekAI. For a typical single-campus church the monthly model cost is usually $5 to $25 in actual API usage. GPT-4o-mini or Gemini Flash is the typical pick for cost. GPT-4o or Claude Sonnet for higher quality on pastoral-tone prompts where warmth and care matter most.

Yes, it can answer general questions about giving (where to give, recurring vs one-time, tax receipts, designated funds vs general fund) by reading your giving page and any FAQ posts. It does not process payments itself. When the visitor is ready to give, the bot links to your giving platform (Pushpay, Tithe.ly, Subsplash, or your custom integration) and steps out of the way. For tax-receipt questions about a specific past donation, the bot routes to the finance team rather than guessing.

Yes. The model itself is multilingual, so a Spanish-speaking visitor can chat in Spanish and get a Spanish response, same for Mandarin, Korean, or any language the chosen model supports well. If you publish key pages in multiple languages (with Polylang, WPML, or TranslatePress), the bot reads the localised page and quotes it back in the matching language. Service-time questions in Spanish about the Spanish service are answered with the Spanish service details.

Only at the level you choose. The system prompt is yours to configure, and most churches set the bot to be welcoming and clear about what they believe while routing actual spiritual conversations to a real person. The bot answers "What do you believe?" by quoting your statement of faith page. It answers "How do I become a Christian?" by offering to connect the visitor with a pastor and giving them next-step resources from your website. It does not pressure, follow up uninvited, or play the role of evangelist itself.