No, deliberately. The system prompt is configured under Safe Sanctuaries principles: the bot provides public-program information (when programs meet, what's coming up, who the leaders are, how to register) and does not become a back-channel for teens to have private conversations with staff outside the proper youth-protection protocols. Real teen-to-staff conversations happen in supervised contexts (multiple adults present, parents informed, documented) not in a chatbot. The boundary is the foundation of any responsible youth-ministry chatbot configuration.

If a teenager expresses suicidal ideation, self-harm, abuse, or any signal of being in danger, the bot immediately routes to verified hotlines: 988 Suicide & Crisis Lifeline (call or text 988), the Childhelp National Child Abuse Hotline (1-800-422-4453), and 911 for immediate danger. The bot does not try to talk a teenager through a crisis itself, because that requires actual training and supervised relationship. The bot also notifies the youth pastor or designated safety contact via the JS API so a real person follows up the same day. Verified public hotlines only — never invented numbers.

Yes. The bot captures student full name, grade, parent contact, t-shirt size, dietary restrictions, current medications, allergies, emergency contact, and any program-specific fields (swim ability for camp, passport for mission trip, fundraising plan, scholarship request). The structured registration lands in a custom post type or routes through the JS API. Medical-release forms and waivers get linked at the right step. Payment routes to the existing checkout (Tithe.ly, Pushpay, Subsplash, or your church's giving platform).

Yes, when each event has an assigned-leader field linked to your leader-bio posts. The bot quotes the youth pastor, directors, and small-group leaders going to each retreat or trip, and parents can read each leader's bio. Background-check status (Safe Sanctuaries trained, current background check on file) is part of the bio. Parents who want to know who their child will be with on a retreat get a clear answer, which is one of the most-asked youth-ministry questions and one most generic chatbots cannot answer.

Yes. SleekAI is multibot. Most youth ministries run a parent-facing bot (formal, complete with policies and contact paths) on the parent-resources page and a student-facing bot (friendlier tone, focused on event Q&A and small-group connection) on the student-facing event pages. Both share the youth-safety boundaries. Display conditions route visitors to the right bot based on URL pattern. The student-facing bot is still bound by the same hard rules: no private channel, immediate crisis routing, never replacing pastoral care.

Yes. The data-source wizard maps your event calendar plugin (The Events Calendar, EventOn, Sugar Calendar, Modern Events Calendar, or a custom post type) and reads each event with dates, cost, age range, leader assignment, and registration deadline. The bot quotes whatever's on the calendar without manual sync. When you publish a new retreat with the dates and cost, the bot has it the next time a parent asks, no retraining needed.

Yes, at the level your published page allows. The bot can confirm scholarships are available, describe the application process from the scholarship page (typical form, conversation with youth pastor, confidentiality of decisions), and capture interest with contact info for follow-up. The bot does not approve scholarships or quote specific amounts because those decisions are made by the youth pastor and finance team based on application context. The bot's job is to make sure no family is excluded because they didn't know aid existed.

Yours. SleekAI is bring-your-own-key for OpenAI, Anthropic, Google, or OpenRouter, and the model bills you directly with no per-message markup from SleekAI. For a single-church youth ministry the monthly model cost is usually $5 to $20 in actual API usage. GPT-4o-mini handles parent Q&A and registration capture well at low cost. GPT-4o or Claude Sonnet for higher quality on safety-boundary holding, where reliable refusal of inappropriate teen-staff private chat scenarios matters more than per-message savings.