Prayer requests
What somebody asked the church to pray about is not training data and not a text to summarise.
What it can take off your team's hands, what it must never touch, and what it costs.
AI and automation
Most of what a ministry team spends its admin hours on is moving the same words between places — a recording into an article, an article into a newsletter, a newsletter into a post, all of it again in another language. That part is worth automating. Deciding what the church says is not.
None of these modules is switched on yet. They are built and quoted per project, because what a ministry needs here varies far more than a website does. Ask, and you will get an honest answer about whether it is worth it for you — including no.
The modules
Each is separate. A ministry can take one and ignore the rest.
In: a YouTube link, an audio file, a manuscript or existing subtitles. Out, as drafts: title suggestions, a summary, scripture and theme index, a devotional, small-group questions, a newsletter piece, social copy, SEO title and description, and Chinese, English and Burmese drafts. Everything is saved as a draft. Nothing publishes itself.
A ministry glossary so your own terms stay yours; personal names, place names and theological terms locked so they are never re-translated; translation memory so the same sentence does not come back different next month; an unreviewed marker on everything; and a per-language list of what is still missing. We do not claim the translation is accurate. Burmese and anything theological has to be read by a person who knows both the language and the faith.
Answers only from the pages the ministry has already published — meeting times, address, statement of faith, events, sermons, contact, giving — and links the page it used. When it does not know, it says so and points to the contact page. It does not guess, it does not offer pastoral advice, it cannot see member records, and it is not an emergency service.
An enquiry sorted, acknowledged and passed on. A new event turned into newsletter and social drafts. A new upload turned into a sermon draft. Missing translations, stale service times and broken links raised in the console instead of by a visitor.
Clear page structure, correct structured data for the organisation, its events, articles, videos and sermons, natural-language FAQs, and a visible last-updated date. We do not promise a search ranking and we cannot promise an AI assistant will quote you.
The boundary
This list is not negotiable, and it is the reason a ministry can use any of the rest.
What somebody asked the church to pray about is not training data and not a text to summarise.
Counselling notes, private messages to a pastor, anything said in confidence.
Names, ages, photographs, attendance, families — nothing about a child leaves the ministry's own system.
Who gave, how much, and when. A giving page shows the ministry's own method; the records stay with the ministry.
Phone numbers, addresses, membership lists. A public model has no reason to see any of it.
If a field is marked private in the console, no automation reads it, including the ones the ministry set up itself.
That is the useful question, not which model we use. If the honest answer is that you do not need any of this yet, you will get that answer.