Governed AI Comes to the Lutheran Church
How the Northern Texas–Northern Louisiana ELCA Synod partnered with Solace to deploy LutherBot — a confessionally grounded, synod-governed AI assistant — serving 5,000+ questions and counting.
AI Was Already Shaping Theology — Without the Church’s Input
NTNL Bishop Erik Gronberg, PhD, wasn’t an early AI enthusiast. His decision to act came from watching a pattern repeat itself throughout church history: Lutherans arriving late to transformative technologies — from the internet to podcasting — and ceding cultural influence as a result.
By early 2025, AI had quietly embedded itself in pastoral life through sermon drafting, Google search, and everyday conversation. Congregants and pastors were already using it. The question wasn’t whether to engage AI — it was whether the church would shape how it got used, or leave that to Zuckerberg and OpenAI.
The deeper concern was stewardship. When someone asks an AI a question about Lutheran sacramental theology, they get an answer. The question is whether that answer reflects ELCA confessional commitments, or a statistically averaged mash of everything on the internet.
“I really started realizing that AI was something that was here. That is not going to change. It’s not going away… And then I was beginning to wonder about who’s in charge of this.”The Rev. Erik Gronberg, PhD — Bishop, NTNL Synod
The Decision Frame
Bishop Gronberg and NTNL leadership identified three realistic paths:
Ignore AI adoption
Allow informal drift. Congregants use whatever tools they find, with no theological grounding or institutional oversight.
Encourage experimentation
Let congregations experiment independently. Queries and insights remain invisible. Denominational alignment is unlikely. No governance, no accountability.
Governed partnership
Controlled deployment with a bounded, approved corpus. Defined roles, synod-level oversight, full visibility into usage and risk.
LutherBot: A Governed Assistant, Not a Bot
Solace built LutherBot as a denominationally-governed AI assistant — not a general-purpose chatbot. The distinction is intentional and consequential. Where a bot answers from whatever data it was trained on, LutherBot answers from a curated, NTNL-approved corpus of 205 carefully vetted documents, including the Bible, the Book of Concord, the Large and Small Catechisms, Martin Luther’s writings, and ELCA/NTNL policy statements.
Development began in July 2024 when content was first received. A test build was delivered in August 2024, followed by an 11-month testing and revision period — iterative, collaborative, and candid about the gaps that needed fixing — before public launch in July 2025.
Governance Structure
What LutherBot Will and Won’t Do
Within scope
- Lutheran teaching, catechesis, and sacramental theology
- Lectionary support and sermon preparation assistance
- Synod and church administrative Q&A
- Referrals to official ELCA/NTNL policy statements
- Faith formation and biblical interpretation
Out of scope
- Sacramental authority or pastoral counsel
- Legal or medical advice of any kind
- Speaking on behalf of the Bishop or synod office
- Open internet retrieval or unvetted sources
- Personally identifiable pastoral care data
5,000+ Questions and a New Window Into the Congregation
In the months since launch, LutherBot has received over 5,000 questions through the NTNL website. For the first time, synod leadership can observe aggregate theological inquiry patterns at scale — not through handshakes after Sunday service, but through a structured, searchable, anonymized dashboard.
The question categories that emerged challenged some assumptions. NTNL leadership expected controversy and apologetics. What they got was a congregation hungry for catechesis.
Query breakdown — NTNL synod level
The administrative dividend
At Christ the Servant Lutheran Church (CTS) in Allen, TX — a fully localized “Engaged Church” — 26% of all queries were administrative: service times, church address, staff contacts, and program availability. These questions typically arrive as interruptions rather than scheduled work, pulling staff away from ministry at unpredictable moments.
Estimating 60+ such queries per month at 5–10 minutes each, LutherBot saves CTS roughly 6–12 staff hours every month — hours that can be redirected to the 74% of queries that genuinely require pastoral presence.
What did and didn’t happen
What happened
- Adoption became observable via synod-accessible dashboards with 5,000+ questions asked
- Leaders gained visibility into what people are asking at scale — doctrinal, pastoral, and administrative
- A governance and review pattern emerged for edge cases and quality control
- Localized churches discovered new insights about their congregation’s actual questions
What didn’t happen
- No replacement of pastors — the assistant is bounded to formation support, not sacramental authority
- No doctrinal freelancing — responses stay within the approved corpus, with “I don’t know” when outside scope
- No rogue AI — access, configuration, and oversight are administered through defined NTNL roles
- No hallucinations — when grounding is insufficient, refusal is preferred over fabrication
The Difference a Curated Corpus Makes
Solace tested LutherBot directly against ChatGPT (v5.2) using the same question: “I am not baptized but I am thinking of going to a Lutheran Church in the NTNL Synod, can I take communion?”
ChatGPT offered a brief, matter-of-fact reply suggesting that unbaptized individuals would not normally receive communion in an ELCA congregation — a statement that was theologically imprecise and failed to account for local congregational practices.
LutherBot — localized to Our Savior Lutheran Church — responded with theological grounding, pastoral warmth, and congregational specificity. It acknowledged that the congregation practices radical inclusion, directed the inquirer to their pastor for more conversation, and provided a direct phone number.
“A response that is theologically tone deaf at that critical first moment of curiosity can close a door that might never reopen.”Governing Deployment Record — Solace × NTNL, Feb. 2026
This distinction matters especially now. A September 2025 Barna Group study found that Gen Z and Millennials are now attending church more frequently than older generations — but arriving with little prior theological formation, shaped more by cultural curiosity than religious instruction. Churches can no longer assume a shared baseline of theological knowledge. LutherBot serves as an on-demand catechetical resource available 24/7, extending the formation conversation beyond the one hour a week a pastor has with their congregation.
What NTNL Actually Got
Three outcomes that matter — with the receipts to back them up.
Staff Time Returned to Ministry
Routine interruptions — service times, parking, who to call, where to show up — are now answered instantly, around the clock, without touching a staff member’s attention. That time goes back to the work no AI can do.
Actionable Ministry Intelligence
For the first time, synod and church leaders can see what their congregation is actually asking — not what they say at the door on Sunday, but what they type at midnight when no one’s watching. Those insights shape sermons, formation series, and outreach decisions.
A Pastoral Productivity Multiplier
Pastors and lay staff are using LutherBot to draft prayers, build confirmation resources, prepare sermons, and scale youth ministry content — not as a replacement for pastoral judgment, but as a tool that amplifies it.
This question came through LutherBot anonymously — typed by someone who would never say it out loud in a fellowship hall. It’s one of 217 belonging and inclusion questions NTNL has now heard for the first time. These are not search queries. They are pastoral moments.
217 belonging & inclusion questions surfaced since launch
A Synod That Chose to Lead
This isn’t a technology story. It’s a story about a Bishop who watched his tradition arrive late to every transformative technology — and decided this time would be different.
NTNL didn’t hand AI to their congregation. They governed it. They curated it. They made it Lutheran. And now 25+ churches across the synod are using it in active ministry.
“AI is here. The question is who stewards it.”
— Bishop Erik Gronberg
Scott Lyon
What Churches and Pastors Are Saying
“Our initial thoughts about LutherBot were to use it to reach young people. What we discovered is how helpful it is as a tool for ministry!”Rev. Cheryl Herreid Pastor, Christ the Servant Lutheran Church — Allen, TX
“The Solace Team helped us conceptualize the big picture value of a Lutheran-focused, grace-based bot to distinguish our Christian message among the cultural ‘noise’ of AI.”Rev. Linda Anderson-Little Pastor, St. Luke’s Lutheran Church
“I’m not answering all the questions… Using LutherBot to continue having those conversations — we’re only meeting for an hour, but they can continue having those conversations.”Rev. Trenton Ormsbee-Hale Pastor, Messiah Lutheran Church — Weatherford, TX
“Central to that effort was the deliberate curation of the theological content powering the Lutheran assistant, ensuring that responses reflected the distinct voice, values, and confessional commitments of the ELCA.”The Rev. Erik Gronberg, PhD Bishop, Northern Texas–Northern Louisiana Synod
A Typical Congregational Onboarding
For churches joining as localized “Engaged” partners, Solace follows a structured onboarding path — starting with a baseline deployment and building toward data-informed ministry decisions within 60–90 days.
Embed assistant on site. Publish 3–6 quick prompts. Identify local admin. Run baseline QA queries to establish accuracy before going live.
Train staff on dashboard. Collect early questions. Refine prompts. Begin local content ingestion — sermons, bylaws, service times, ministry descriptions.
Review dashboards. Tune edge cases. Produce one ministry output — an FAQ, a welcome flow, a formation lesson plan — informed by real query data.
“Zuckerberg is going to control your message if you don’t.”Scott Lyon — Founder & CEO, Solace