Yes. The system prompt sets the register, and religious schools typically configure the bot to use the tradition's actual language. A Catholic school's bot speaks of catechesis, sacraments, the liturgical calendar, and the magisterium when relevant. A Jewish day school's bot speaks of tefillah, Judaic studies, the Hebrew calendar, and the school's specific Hebrew-immersion model. The bot reads the school's own pages and reflects the vocabulary the school uses, not a generic 'religious education' framing.

Yes. The bot reads your published sacramental preparation page (or observance integration, religious-formation programme, etc.) and quotes it. For Catholic schools, First Reconciliation, First Communion, and Confirmation are typically anchored to specific grades; the bot quotes those grades from the published page. Anything family-specific (a child not yet baptised, parents from different traditions) routes to the pastor or director of religious education rather than answering directly.

Yes. If your tuition page lists multiple tiers, the bot reads each as a structured field. In-parish (or member, congregant, parish-supporter) and out-of-parish tiers are common, and the bot quotes the right one based on the family's described status. For multi-parish or multi-congregation feeder structures, the bot can identify which parishes qualify from the published list and answer accordingly.

Yes, with the right framing. Many religious schools enrol a meaningful percentage of families from outside the tradition, and the bot quotes the school's published policy on non-tradition families. Some schools require participation in religious-formation classes; some make it optional in upper grades; some require respectful engagement only. The bot reflects whatever the school publishes, in the right tone.

Yes. The system prompt routes theological, doctrinal, and pastoral questions to the clergy or head of school by webhook. The bot can answer at the descriptive level ('we follow the Diocese of Springfield catechetical guidelines'), but anything that crosses into theological interpretation routes to the priest, rabbi, imam, or designated teacher who can speak in the tradition's authority. Most schools consider this the right boundary.

At the policy level. The bot reads your published list of sponsoring parishes, congregation members, or feeder congregations and answers in-parish status questions from that list. For a family at one of those parishes or congregations, the bot quotes the appropriate tuition tier. Specific membership verification (are we registered at this parish) routes to the school office, since that involves looking up a record the bot doesn't access directly.

Yes. The system prompt forbids collection of child names, religious identification details beyond a general level, family situation specifics, and other sensitive information. Parent contact is collected only for tour bookings. Conversation logs live in your WordPress database with the security you've configured, and many religious schools set short retention windows (30 to 60 days) to keep the privacy posture consistent with the pastoral care framing the school takes everywhere else.

Yes. The same configuration model works for any tradition. The bot reads the school's pages and reflects the tradition's vocabulary. A Jewish day school's bot can answer about kashrut policy, Shabbat-aware programming, Hebrew-language sequencing, and bnei mitzvah preparation. An Islamic school's bot can answer about Quran memorisation, salah programming, and Islamic calendar observances. A classical Christian school's bot can answer about the trivium, paideia, and the school's confessional statement. Each is configured to the tradition's actual register, not a generic religious-education translation.