How do you follow up a first-time visitor who does not speak your language?
By making the first step theirs, in their language, during the service, and by putting everyone who took it into one list that somebody owns on Monday. A visitor who fills in nothing has not refused to be known; they were never asked in a language they could answer.
What a first-time visitor actually does
They arrive late, sit near the back, do not know when to stand, and understand a third of what is said. A welcome card in the pew is in a language they read slowly. A person with a clipboard by the door is exactly the encounter they came hoping to avoid. If they leave without anyone knowing they were there, it is not because they did not want to be found. It is because every way of being found was in the wrong language or asked too much.
Whatever the church does about this, it has to happen while the visitor is still in the building, in the language they think in, and in one tap.
The first step has to be theirs
The moment a church translates its service onto the visitor's phone, it has something it did not have before: a screen in front of that person, in their language, for an hour. That screen can ask the question the clipboard could not. Is this your first time here? Would you like someone to pray for you? Is there a way to reach you?
- Each question is a choice the visitor makes, not a form they must fill in to keep listening.
- Each is in their own language, the one they chose to listen in.
- Nothing is required: a visitor can press Amen and leave nothing else, and that is a complete visit.
- If they do leave a way to be reached, consent is recorded with it, because that is the law and because it is the decent thing.
What the list on Monday needs
The Sunday half is easy to get excited about. The Monday half is where visitors are lost. Every church has a story of a card that sat in a drawer. A follow-up list that works has a few properties, none of them technical.
- One list, not one per source: first-time visitors, prayer requests, contact requests and comments in one place, per service.
- A status per person that a team can move: new, contacted, needs prayer, invited, connected, closed.
- A private note per person, for the team and nobody else.
- The visitor's preferred language beside their name, so the person who calls is the person who can.
- A way to take it out — an export — for the church that works from a spreadsheet or a phone tree.
- A rule for when it is deleted, kept with the service it came from.
The status column is the whole thing. A list without one is a pile of cards; a list with one is a pastor's Monday morning, done by Tuesday.
In their language, all the way
Following up in the visitor's language means more than the phone call. It means the message they heard is available to read afterwards in that language, the newsletter arrives in it, and the invitation to Wednesday's group is written in it. A church that translates the service and then follows up in the host language has moved the wall one week later.
How Sanctavo does it
During the service a listener can tap Amen, say it is their first time, ask for prayer, leave a word, or leave a way to be reached, in the language they are listening in, each of them a switch the church turns on per service. Everyone who did is in one list afterwards, with a status — new, contacted, needs prayer, invited, connected — a private note for the team, their preferred language, and an export. Consent is recorded, the list is private to the church and deleted with the service, and the message itself, the newsletter and the small-group guide exist in that visitor's language too. The visitor who came once is called, invited, and not forgotten.