What an AI tool for a church actually does on a Sunday

Judge these tools by the job they do on a Sunday morning, not by the feature list. There are seven jobs, and one recording feeds all of them.

Most lists of AI tools for churches are lists of vendors. That is the wrong axis. Ask instead what has to happen between the first song and Tuesday's newsletter, and you end up with seven jobs — one during the service, two in the ten minutes after it, and four in the week that follows. A church can buy them separately and stitch them together, or have one system do them from the same audio. What follows is what each job looks like when it works.

What does it do during the service?

The first job is translation, and it is the one that changes a room fastest. Someone who does not speak the language of the service scans the code on the card in the pew, picks a language, and hears the service on their own phone — a natural voice that keeps the preacher's tone and rhythm, under a second behind him, with captions running alongside for anyone who would rather read than listen. Nothing is handed out and nothing is collected afterwards. In our own church in Vienna we run four languages this way, and Farsi and Armenian go out every Sunday.

Two things nobody mentions in a demo. Take the audio from the desk, not from a microphone in the room, or every cough and the worship band's monitor wash end up in the translation. And watch the names: "Habakkuk", the visiting speaker from Lviv, your own church's name for the youth evening — proper nouns and verse references are where every system slips, and where a glossary someone in your team has actually approved earns its keep.

The same code that carries the translation also carries the room's answers back, which is job two: Amen, first time here, a prayer request, a word for the team. That is one tap during the service rather than a card nobody fills in. A church with one language uses this part every week without ever switching translation on.

What happens in the ten minutes after the service?

A second code goes up at the end: prayer, first time here, a testimony, a question about the message, the record to read. It is on the screen while people are still standing around with coffee, which is the only ten minutes in the week when a visitor will actually type something.

Job three is what happens to those answers. They land in one follow-up list with a status per person, so the visitor who ticked "first time here" at 11:40 is a name someone is responsible for on Monday, not a slip of paper in a drawer. This is the job most churches are worst at, and it has nothing to do with language — we wrote more about how the follow-up works in every language if you want the detail.

What do you get by Monday morning?

Job four, the record. Within the hour: a clean transcript, a summary, the full message written out, a small-group guide, and drafts for the blog, the newsletter and social — in every language the church serves. The point is not that a machine writes your newsletter. The point is that the person who writes it starts from the sermon that was actually preached instead of from a blank page and a memory of Sunday. We covered the whole chain in one recording, seven pieces.

Job five is the long form. A teaching series is a book that nobody has time to assemble; from the recordings you already have, it becomes a study guide or a printed book in the languages you choose. Job six is the recorded video: a sermon or a lecture that comes back spoken in other languages, which matters for churches whose reach is larger than their room.

Can someone ask the sermon a question afterwards?

Job seven, and the one people underestimate. A member asks a question and gets an answer grounded in what was preached, citing the passage it came from — not a general answer from the internet with a Bible verse attached. Underneath it sits the church memory: names, places, terms your team has approved, carried into every translation and every draft, so the fourth service does not misspell what the first one got right.

What about a church with one language?

Six of the seven jobs run on a Sunday where everybody speaks the same language. The engagement code, the after-service screen, the follow-up list, the content pack, the study guide, the questions afterwards — none of that depends on a second language being in the room. Translation is the seventh, and it is a switch you turn on the Sunday a second language walks in, which for most European churches happens sooner than they plan for. That is the honest reason to look at these things as one system: you are not buying translation, you are buying the Sunday, and the language part is waiting when you need it.

What to do this Sunday

Pick the job that costs your team the most hours and test only that one. For most churches it is the record — so record one service properly from the desk, and see what a transcript and a summary of your own preacher actually read like before you decide anything else. If it is translation, find the two people in your congregation who would use it, sit them down with a phone and read them ten minutes of last week's sermon; their faces will tell you more than any comparison table.

And whatever you test, test it on a real Sunday with the band playing, not on a quiet Tuesday with one person reading a psalm into a laptop.

We built Sanctavo to do these seven jobs from one recording; what it costs is on the pricing page, and the live service answer page walks through how a Sunday runs from the front.