How to test AI translation in a church service before you buy

You can test a live translation system in a single ordinary service, and five things are worth testing: how far behind the speaker the translated voice actually arrives, whether that voice sounds like a person talking, whether names and terms come back right, what happens when the preacher goes off script, and what you are left holding on Monday morning. None of that needs a benchmark, a trial quarter or a demo written for you. It needs one Sunday, one person who speaks the target language, and somebody willing to sit in the back row and watch the listener rather than the screen.

The confusion is worth clearing up before you test anything, because three different products answer to the phrase AI church translation. Some systems caption only: text on a screen or a phone, no sound. Some dub a recording afterwards and give you the sermon in another language on Tuesday. Some translate live, as speech, during the service. All three are legitimate and a church may want more than one, but they solve different Sundays. Decide which Sunday you are solving before you look at a price. Once you know which one you are buying, the same short list works on all three: six questions to ask any church translation software.

How do you test it in one service?

Latency, measured honestly: sit in the back row with a listener and watch whether the translated voice is riding on the speaker's heels or arriving a sentence late. A sentence late is unusable for a sermon, however good the wording.

The voice itself. Have someone who speaks the target language natively listen to ten minutes of your actual preacher and tell you whether it sounds like a person talking or a machine reading. Tone and pace carry more of a sermon than most people admit.

Names and terms. Hand the system your list — people, places, your church's own words — and check it comes back right. Then check who on your team can edit that list without filing a support ticket.

The handover. What happens when the preacher goes off script, takes a question, or the worship leader starts talking over the end of the prayer. Anything will work on a clean read; Sundays are not clean reads. Part of that is the preacher's side rather than the system's, and preparing a sermon for live translation is mostly a matter of ending sentences.

And the week after. Ask what you are left holding on Monday morning, which is the part most churches forget to ask about.

Do the listening check more than once, and do it during the part of the sermon that tells people what to do rather than during the story, because faithfulness is not a steady state and one sample at one moment will tell you the wrong thing in either direction. A system can read a narrative passage cleanly and still slip inside an instruction, and nobody in the room who speaks only one of the two languages will hear it happen.

What does AI translation do during the service?

The words spoken from the front are turned into another language and reach a listener while the sentence is still warm — on their own phone, through their own earphones, under a second behind the speaker, in a voice that keeps the preacher's tone and rhythm instead of reading the text out flat. Captions run alongside for anyone who would rather read. No receiver box to hand out, no booth, no second person to roster.

A microphone feed from the desk goes out as speech in the target language, and each listener picks the language they want. In our own church in Vienna we run four languages on a normal Sunday, Farsi and Armenian among them, and the practical shape is this: a QR card at the door, people scan it on the way in, they choose their language, and they listen. The volunteer who used to stand at the back handing out receivers now hands out nothing, and the person who most needs the translation is usually the one who did not bring earphones — so keep a box of cheap wired ones by the door and stop worrying about it.

The things that break are not the things you expect. Names break. Verse references break. "Hesed", "Ebenezer", the surname of the missionary family you pray for every month, the name of your own church — every system guesses at these, and a wrong guess is more jarring than no translation at all. This is why a glossary that a person on your team approves matters more than any benchmark number, and why we would not buy a tool that does not have one.

What does it cost a church per month?

Our own pricing is counted in live language hours: one hour of one language going out live. Our plans start at €49 a month for five of those hours in one language, €97 for ten hours and two languages, €247 for thirty-five hours, and €497 for eighty across several sites. On Starter and larger plans, five more hours is €25. A single weekly service of about an hour in two languages lands inside the €97 plan with room to spare; two services, or a third language, is where you move up.

Work out your own number before you shop, because it is the only honest way to compare anything. Services a week, times minutes each, times the number of languages going out at the same time. A sixty-minute service in two languages is two live language hours, so about 8.7 hours in a typical month. Churches overestimate this badly — people count the whole morning rather than the minutes that are actually translated.

What is left after the service?

This is the half of the question that gets skipped, and it is where most of the value sits for a church that is not yet multilingual at all. The same recording that fed the translation should give you, within the hour, a clean transcript, a summary, the full message in readable form, a small-group guide and drafts for the blog, the newsletter and social — in every language you serve. A second QR code after the service opens a screen where people can leave a prayer request, say they are here for the first time, send a testimony or ask the sermon a question, and all of that lands in one follow-up list with a status against each person, so Monday is a list rather than a memory.

Past that, a teaching series can become a study guide or a book, a recorded sermon can come back spoken in other languages, and the names and terms your team approved once get carried into every translation and every draft from then on. A church with one language uses every bit of that weekly and switches translation on the Sunday a second language walks through the door. If you want the shorter version of all this, we keep a plain answer page on church AI translation, and the question of whether to keep your human interpreter is worth reading before you decide anything, because for a good many churches the answer is yes.

Run the five checks on one ordinary Sunday with whatever you are considering. If you would like one of those Sundays to be ours, we will set it up with you and run it on your own service, in your own languages, before you decide anything.