What people ask the sermon on Monday

The questions arrive on Monday, not on Sunday. Most of them are people trying to find a sentence again.

Published 2026-09-29 · 2026-10-28

Give a congregation a way to ask Sunday's sermon a question and the questions come, but not the ones you brace for. Almost nobody arrives with an argument. They arrive trying to find something again: the verse you read near the end, the phrase about waiting, the name of the book you held up. An answer that quotes the sermon back to them and says where it sat — the passage, roughly when it was said — closes the loop in about ten seconds, and they go to bed with it.

That is the whole of it. A question box that answers only from what was preached, and refuses when the sermon did not cover something.

Why "grounded in the sermon" is the entire feature

A general-purpose chatbot pointed at a church website will answer anything, confidently, including things the preacher never said and would not say. That is not a small flaw. A member who is told on Monday that the church teaches something it does not teach is a pastoral problem that lands on somebody's desk by Wednesday.

So the useful version is narrow on purpose. It reads this Sunday's transcript and the ones behind it, it answers from those, it cites the passage, and when the answer is not in there it says so. "That did not come up on Sunday — you could ask in your small group" is a better answer than a fluent invention. Ask the question of any tool you are considering: what does it do when the sermon does not contain the answer? If it always produces something, it is guessing somewhere.

What actually gets asked

From our own Sundays at 222 Vienna, the questions sort into four piles and the sizes surprised us.

Finding a sentence again is the biggest by a distance. "What was the verse about the vineyard?" People are not testing the system; they lost a line and want it back.

Next is the part they missed — arriving late, a child who needed taking out, ten minutes lost. They want the middle, not a summary of the whole thing.

Third, and the one worth paying attention to: questions people would not ask a person. What the sermon meant about forgiveness when the other person has not apologised. Whether it applies if you are not sure you believe it yet. These come in late at night and they come from people who have sat quiet in the same row for two years.

Fourth, and smallest, the practical: when is the group, where do I read this.

It works in the language they were listening in

If someone followed the sermon in Farsi on their phone, the question comes in Farsi and the answer should come back in Farsi, quoting what was preached, not a rough gloss of an English answer. This matters more than it sounds. In a service translated live, the people most likely to have missed a line are exactly the people listening in their second language — and they are the least likely to tap a pastor on the shoulder about it. Asking a screen costs them nothing.

The names have to survive the trip, which is what a church memory is for: your church's name, the elders' names, the way you say the book names, approved by a person on your team once and then carried into every answer. Untended, this is where every system slips — a name mangled in an answer reads as carelessness about the person.

What to do with it on a Sunday

Put it where the rest of Sunday already lives. If people scan a code after the service for prayer or to say they came for the first time, the question box belongs on that same screen; a second destination is a destination nobody visits. Say one sentence from the front — "if you want to go back over anything from this morning, the code has a place to ask" — and then let it be.

Two habits make it better. Read what gets asked, weekly, and do not answer it individually; it is the most honest feedback on your preaching you will ever get, because nobody is being polite. If eleven people ask the same thing, that was not clear and it wants two minutes at the start of next week's message. And tell people plainly what happens to their question — who can see it, how long it is kept. A church that explains that once gets used, and the transcript and summary the same recording produces are what the answers are drawn from, so it is one system to explain, not two.

The thing we did not expect: it made the sermon last longer. A message people can still put a question to on Thursday is a message still being thought about on Thursday.

If you want to see what this looks like on your own sermon, Ask the Sermon is part of what a recording turns into — alongside the transcript, the summary and the week's drafts — and it runs in every language your church serves.


Further reading: AI church translation, its costs and how to test it and the AI tools a church uses in the week after Sunday.

Blog · All answers · Diese Antwort auf Deutsch