PodSaid for Pastors and Ministry Leaders — FAQ

If you are skeptical about putting AI anywhere near your pulpit, you are in good company, and that skepticism is fair. Most AI tools are trained on the whole internet and are happy to speak with confidence on things they should not. PodSaid is built differently, and the differences matter. This page is written for pastors, elders, and ministry leaders weighing whether a tool like this belongs anywhere near your church’s sermon archive.

What is PodSaid, in one paragraph?

PodSaid is a small chat pane that lives on your church’s website. A visitor types a question — “what does this church teach about grief?”, “when did pastor talk about forgiving a family member?”, “what did that series on Ephesians say about work?” — and the AI answers using only the sermons your church has already preached. Every answer links back to the specific episode and timestamp, so the visitor can hear it from you directly, in your own words, in context. It is a study companion built on top of your archive. Nothing more.

Will the AI ever put words in my mouth?

This is the concern we take most seriously, and it is the one we designed around first. The AI is instructed, at the deepest level of the system, to answer only from what your church has actually preached. It is not allowed to reach for general knowledge, other pastors’ takes, denominational commentary, or the wider internet. If you never preached on a topic, the AI won’t make something up. It will say so.

Every answer also carries citations back to the source sermon and timestamp, so a visitor can verify what the AI paraphrased against the actual audio or video. This is not a chat that talks about your teaching. It is a chat that points to your teaching.

We should be honest: no AI is perfect at paraphrase. That is why the citation matters more than the paraphrase — the sermon itself is the source of truth, and the AI’s job is to help someone find the right place in it.

Whose sermons does it draw from — only mine, or the broader internet?

Only yours. The system is grounded in your archive alone — the sermons you’ve preached, transcribed from your podcast feed or YouTube channel, along with the summaries and speaker metadata we generate from them. It does not blend in outside commentary, other churches’ teaching, or theological training data. If a visitor asks a question your archive doesn’t cover, the AI is instructed to say so rather than pull from general knowledge.

That is why the AI ends up sounding like your church. It is drawing from your church.

What happens when someone asks a question I’ve never preached on?

The AI returns a short, honest reply that the archive doesn’t cover that topic, and it stops there. It does not paper over the gap with a plausible-sounding generic answer. This is a deliberate design choice — we would rather the AI say “we don’t have material on that” than invent something.

This is also useful pastoral information. Over time, you’ll see the questions your congregation and visitors are asking that your archive doesn’t yet answer. Some churches have found that a helpful input to sermon planning.

Can it be scoped to a single teacher or series?

Yes. If your church has multiple teaching pastors, the archive can be filtered per teacher. So a widget on the senior pastor’s page can be scoped to only his sermons (“AskBruce”), and a widget on the associate’s page can be scoped to hers (“AskYancey”). Similarly for a specific series, guest teacher, or ministry track. The speaker metadata comes straight from your feed, so this reflects how you already label your content.

We’re finishing polish on the operator controls for speaker-scoping, so if you have a specific configuration in mind, mention it during onboarding and we’ll set it up with you.

What if a visitor asks something controversial, sensitive, or theologically loaded?

The AI answers from your sermons. So on any theologically loaded question — sexuality, suffering, the sovereignty of God, church discipline, baptism, women in ministry — the visitor gets what your church has actually taught, in your pastor’s own words, with a link to the sermon. It does not offer a compromise position, a denominational average, or its own opinion. It reflects your teaching, not a generic AI’s opinion.

For sensitive personal topics — grief, crisis, mental health, family breakdown — the AI can surface where your pastor has preached on the subject, but it is not counsel. We strongly recommend placing a visible “Talk to a pastor” contact link near the widget so that anyone in real need has an obvious path to a real person. More on that below.

Does this replace a pastor’s counsel? How should we frame it to our congregation?

No, and please don’t let anyone frame it that way. The AI is a study companion, not a substitute for pastoral counsel. It is good at helping someone find where you preached on a subject. It is not a shepherd, it does not know the person, and it cannot pray with them.

We recommend three things when you introduce it to your church:

1. Be transparent that it is AI. A short note on the page — “This assistant uses AI to search our sermon archive. It is not a substitute for talking with a pastor.” — respects your congregation and sets the right expectation.
2. Keep a “Talk to a pastor” link visibly near the widget. If someone is in crisis, the AI is the wrong destination. A real person, or at minimum a real phone number and email, should be one click away.
3. Frame it as what it is — a way to find sermons on a topic, not a chatbot pastor. When members hear it described plainly, most of them get it immediately.

Who owns our sermon content? What if we leave?

Your archive is yours. It was yours before PodSaid, and it stays yours the whole time. We are processing your content — transcribing it, chunking it, indexing it — so that a chat interface can search it. We do not claim ownership of your sermons, your transcripts, or the derived summaries. If you leave PodSaid, we hand it back — it was always yours — and the widget stops serving. There is no lock-in on the content itself.

How do visitors reach us if they have deeper questions?

That’s up to you and it’s important. The widget is one tool on your site. Your contact page, your prayer request form, your care team email, your Sunday welcome — all of that still matters, arguably more when a visitor has been engaging with your teaching and now wants to talk. We recommend a clear “Talk to a pastor” or “Request prayer” link placed near the widget, so the on-ramp from “I was curious” to “I need to talk to someone” is short and obvious.

How does this help our ministry practically — reach, discipleship, seekers?

Three concrete places we’ve seen it help:

Seekers finding your teaching. Someone visits the site, has one question in mind — about anxiety, about hope, about a specific passage — and can ask it directly. Instead of scrolling through a video library, they land on the sermon that speaks to it. Your pastor’s own voice, on the topic they came for.

Members going deeper mid-week. “When did pastor teach on forgiveness in Matthew 18?” is the kind of question a member might have and never bother to email about. The widget answers it and points them to the sermon.

Sermon planning input. Over time, you’ll see the questions being asked that your archive doesn’t yet cover. That is honest data about what your community is thinking about.

We won’t overclaim. This is a tool that supports pastoral work — it doesn’t do pastoral work. What it does well is make years of faithful preaching easier to find.

Can we see the questions that are being asked?

Yes, and it may be the single most pastorally useful thing PodSaid produces.

Every question asked through your widget shows up in your console dashboard — the exact wording the visitor typed, when it was asked, and which sermons the AI cited in reply. You see, in your congregation’s own words, what people are trying to learn about your church. It is unfiltered, direct, and often surprising.

Many pastors use this as honest input for sermon planning. The most useful signal is often the questions that came back light or empty — subjects your archive doesn’t yet cover, but people are actively asking about. That is not a criticism; it is data. It tells you where your teaching could next go to meet the people who are already looking.

There is no visitor identity attached to any question. No name, no email, no way to link two questions to the same person. This is not a surveillance tool aimed at your congregation. It is a mirror showing you, in aggregate, what they are asking in their own words.

What does it cost, and is there a way to try it before committing?

There’s a free tier that lists your church in the PodSaid directory and includes 200 questions per month — enough for many smaller churches to see whether it fits.

Beyond that, the Indie plan is $14.99/month. It removes the “Powered by PodSaid” footer, gives you a custom subdomain (like yourchurch.podsaid.com), and raises the question limit to 500 per month. Larger tiers scale up from there.

We offer a 14-day trial. Importantly, the trial clock starts when your content is ready — not when you sign up. Depending on your archive size, transcribing and indexing sermons can take a few days, and we don’t think you should burn trial days waiting for that. You’ll get an email when it’s ready to try.

Setup is about 40 minutes end-to-end and generally doesn’t require a developer. Most sites just need two lines of HTML pasted into a page template.

Can PodSaid draw from other content on our site — service times, ministries, resources?

Not yet, and it is worth saying plainly.

Today the widget is grounded in your sermon archive alone. That discipline is deliberate. It is what keeps the AI answering in your church’s own voice, and it is why we can say honestly that the AI is not blending in outside material. The moment we ingest content from anywhere else, that boundary becomes something we have to protect deliberately rather than something the system enforces by construction.

That said, it is by far our most-requested feature. Church websites carry much more than sermons — service times, ministry pages, staff introductions, resources — and visitors reasonably ask about all of them. Bringing that content into the same experience, while keeping the sermon-only guarantee visible where it matters, is on the near-term roadmap for this year.

We are looking for a small number of pilot partner churches to help shape it — how the content boundaries are shown to visitors, how the AI marks the source of each answer, and how it holds up under the kinds of questions your church actually receives. If that could be your church, please reach out.

What we won’t pretend

A few honest limits, because you should hear them from us, not discover them later.

• This is not a replacement for a pastor. It cannot pray, cannot know your people, cannot exercise discernment. Keep pastoral care human. Keep a real contact prominent on the page.
• We do not run a doctrinal filter over the AI’s answers. By design. The AI answers from your sermons, so it reflects your church’s theology by construction — not ours, and not a generic AI’s. That is the safeguard, and it’s a stronger one than any filter we could bolt on. But it does mean: whatever your archive teaches, that is what visitors will hear.
• AI paraphrase is imperfect. That is why every answer carries a citation back to the sermon. Trust the sermon, not the paraphrase. If you find a case where the AI mischaracterizes something you preached, tell us — we take those reports seriously.
• Pastoral judgment still matters more than any tool. We built this to serve your ministry, not to lead it. You know your congregation. Use the tool where it helps, ignore it where it doesn’t, and shut it off if it ever stops serving them well.

If you’d like to talk it through with a person before signing up, that’s genuinely welcome. We’d rather have a real conversation with a pastor than sell a subscription that isn’t a fit.