Visitor follow-up when the replies come in four languages
The hard part of a multilingual Sunday is not the sermon. It is Monday morning, when four prayer requests are sitting in a script the person who answers them cannot read.
Published 2026-10-11
Answer in the language the person wrote in, and get it out before Tuesday evening. That is the rule, and nearly every church that serves more than one language breaks it for the same reason: the responses arrive in four languages and the volunteer who would answer them reads one. So the Farsi requests wait for the one person who reads Farsi, that person has a job and three children, and by Thursday the newcomer has concluded that the warm church he visited does not write back.
We run four languages at 222 in Vienna, Farsi and Armenian every Sunday, and this is the part of the week that took us longest to get right. The service itself is settled: people listen on their own phones and the sermon arrives in their language. The responses afterwards were the mess.
Which language do you answer in?
Theirs. Not the language of your office, and not the language of the service. If someone writes you a prayer request in Farsi at ten past twelve, a reply in German reads as a polite refusal of the thing he just did, which was to reach out in the only language he can be honest in.
Two things make this cheap rather than heroic. The first is that these messages are short: a name, a situation, a sentence of thanks. The second is that nobody expects literary prose from a church office. Three plain sentences in the right language beat two paragraphs in the wrong one.
Keep the original text beside the translated one, always, and never throw the original away. The names are in the original. So is the tone, which tells the person answering whether this is a crisis or a courtesy.
What if nobody on the team reads the script?
Then you need two things, and neither of them is a bilingual volunteer you do not have.
You need the gist in a language your team reads, so the person on duty can triage: is this a prayer request, a question about the sermon, somebody's first Sunday, or a practical note about the car park. And you need the reply to go back out in the sender's language. Both are mechanical now. What is not mechanical is the judgement in between, which is why the list belongs to a person and not to a tool.
One warning from our own Mondays. A request written in Farsi often opens with a greeting formula that, translated word for word, reads far more dramatic in German than it is. Answer the request, not the formula. If you reply to the politeness instead of the need, you will sound like you misread the message, because you did.
Does each language need its own person?
No, and resist it if someone offers. Four parallel follow-up lists produce four different standards of care and no way to answer the only question that matters on Monday night: who has not been written to yet.
One list, every response in it, a status per person. We use three: new, answered, handed on. "Handed on" is the honest one, because some requests belong to a pastor or to a woman in the congregation who has lived through the same thing, and the list has to be able to say so rather than quietly mark it done.
What a second language adds to that list is one column, not a second system. Everything else we wrote about the list and the twenty minutes on Monday holds exactly as it is.
How do you keep the names right?
Copy their spelling. If a man writes his name in Armenian script and you cannot read it, paste it as he wrote it and put your own transliteration after it, not instead of it. Anyone who has moved countries has had his name mangled on enough forms to notice which churches bother.
Write down the handful of spellings your team keeps getting wrong, the same way you write down the words your preachers use every week. It is a ten-minute job that pays out for years.
Do you need special equipment for any of this?
For the follow-up, nothing at all. A code on the screen after the blessing and one person who owns the list is the entire apparatus.
For the room, the equipment question is smaller than it used to be too. Receivers, headsets and a locked cupboard were the old answer; most churches now find the listener's phone carries it, and the money goes on a clean audio feed instead. We set out what is still worth buying, what to borrow and what you no longer need in our answer on translation equipment.
What to do next Sunday
Put the code where people can still see it while they are putting their coats on, not only during the notices. Ask three things, not eight. Decide before Sunday who sits down with the list on Monday for twenty minutes, and tell that person that a reply in the sender's language, however short, counts as done. Then look at who answered, and in which language, and you will learn more about your congregation in two weeks than a year of counting heads at the door.
Sanctavo carries the whole Sunday: live translation of the service on each listener's phone from one QR code, with captions alongside, and a second code after the blessing that opens prayer, first time here, testimony and Ask the Sermon. Every response lands in one follow-up list with a status per person, and within the hour the transcript, summary, study guide and the week's drafts come back in each language your church serves.