No. SleekAI is configured to recognise doctrinal questions and to refer them to the pastor. The bot will say something like "that's a conversation Pastor Linnea would love to have, the office hours are Mon to Thu 9am to 3pm at (763) 555-0182" and offer the visitor-coffee slots. Questions about the real presence, justification, baptism's relationship to faith, predestination, and the Book of Concord all fall in this category. The guideline filter reinforces the boundary.

Yes, when the synod and the congregation's published practice are recorded. The bot quotes what your about-us page or constitution says about communion, ordination, and other practices rather than generalizing across ELCA, LCMS, WELS, or NALC. If your page says "we practice close communion" or "all baptized Christians are welcome," the bot uses that exact framing. It does not invent a position.

Yes. Sunday school registration timing, confirmation class schedules, the typical age range, what students need to bring, and which pastor leads each cohort can all be pulled from the corresponding pages. The bot can also hand off to the Director of Christian Education or the pastor when a parent has a question about whether confirmation is the right fit this year.

Yes. A small parish with one Sunday service and a part-time pastor does not need a complex bot. SleekAI runs fine on a simple worship schedule, references the pastor's published Tuesday and Thursday office days, and notes when worship moves to the school auditorium during summer. The cost is whatever the model usage is, typically a few dollars a month at small-parish traffic on GPT-4o-mini.

At a logistics level only. The bot explains the published process (start with a call to the office, the pastor meets with the family, pre-marital sessions if required, the typical fee structure if posted) and gives the office number. It does not commit to dates, schedule the pastor, or discuss the substance of the service. Those conversations belong with the pastor and the worship team.

Yes. SleekAI uses the LLM's multilingual capability, so a visitor asking in Spanish, German, Swahili, or Mandarin gets answered in that language. The underlying data (service times, addresses, ministry names) stays the same, only the response language changes. This is useful for congregations with growing immigrant communities or a multilingual surrounding neighbourhood.

Yours. SleekAI is BYO API key for OpenAI, Anthropic, Google, or OpenRouter, billed directly to you with no markup from Sleek. For a single-congregation chatbot on GPT-4o-mini the typical monthly usage is a few dollars even with regular visitor traffic. Switch to GPT-4o or Claude Sonnet for higher-quality handling of nuanced visitor questions about ministries or communion practice.

Yes. SleekAI stores every conversation in WordPress with the model name, token usage, and the page URL where the conversation happened. The office can review what visitors actually ask, which tends to surface gaps in the website ("a lot of people are asking whether nursery is available at the 8:30 service"). Logs stay in WP admin, not shared outside the congregation.