- Starting price
- $49/month after 14-day trial
- Free tier
- No
- Platforms
- Web · Embeddable website chat · Member hub
- Developer
- L&D Holdings LLC
- Launched
- 2026
- Updated
- Aug 9, 2026
The verdict
Doctrinally.AI is a compelling way to make a church’s existing teaching searchable: citations that jump to a sermon timestamp or PDF page are materially better than an answer that merely sounds pastoral. Its newer Website Chat can also turn a visitor question into an identifiable prospect record and attached transcript, which changes the product from a study tool into a ministry intake system. Run a synthetic pilot, curate sources, publish a conspicuous AI and privacy notice, keep crisis and confidential care out of chat, review unanswered and risky conversations, and ensure every response can defer to a named human. “Grounded in our sermons” reduces one kind of hallucination; it does not prove the sermon, retrieval, synthesis, application, or lead handling is right.
Try Doctrinally.AI ↗Opens doctrinally.ai
Doctrinally.AI gives a church one content library and two public chat surfaces. Member AI lives on a Doctrinally subdomain or, on Enterprise, the church’s own domain. Members scan a QR code or open a URL and ask questions without a login. Website Chat adds a script tag to the church’s existing site, opens a tailored conversation with visitors, and can collect a name and email in a Prospects dashboard with the conversation attached. Both products answer in a voice shaped by sermons, videos, PDFs, documents, and devotions uploaded by church administrators.
The retrieval design is the strongest part of the offer. Administrators can paste a YouTube sermon link, upload a video or PDF, or write in the built-in editor. Answers cite the selected source; embedded sermon citations can play from the relevant timestamp and PDF citations can link to a page. Analytics report trending questions, unanswered queries, and apparent teaching gaps. Enterprise adds an automatic weekly YouTube-channel sync that organizes videos, shorts, live replays, and chosen playlists and avoids known duplicate imports.
Standard is $49 per month for Website Chat, a Doctrinally subdomain, unlimited uploads, 1,500 member questions monthly, analytics, unlimited members, and email support. Enterprise is $99 per month for 3,000 questions, a custom domain, church logo and branding, YouTube auto-sync, priority support, and onboarding. Every plan has a fourteen-day trial, no setup fee, no long contract, and cancellation from billing. Limits stop by default; a church can deliberately enable overage at ten cents per Standard message or five cents per Enterprise message and set a cap.
L&D Holdings LLC owns and operates the service. Its April 2026 privacy policy says OpenAI currently processes messages, while Vercel, Trigger.dev, and Stripe provide hosting or operations; uploaded church content and conversations are not used to train AI models. It describes tenant isolation, encrypted transmission, role-based access, and thirty-day retention after cancellation. The product is new and vendor claims are not an independent evaluation. We reviewed its official product, features, workflow, pricing, FAQ, privacy, and terms pages plus public examples. We did not create an administrator account, upload copyrighted teaching, embed the widget, submit a lead, run a congregation pilot, measure answer accuracy or latency, test deletion or export, penetration-test isolation, or receive independent theological, security, privacy, accessibility, child-safety, or outcome evidence.
✓ The good
- Source-grounded answers - responses point back to church-uploaded teaching instead of presenting an unsupported generic synthesis
- Usable citations - video can jump to a sermon timestamp and PDFs can link to the relevant page
- Two audiences, one library - visitor Website Chat and congregation Member AI avoid duplicating content management
- Fast publishing path - a script tag, subdomain, unique URL, and QR code remove the need for a custom church app
- Unlimited members and uploads - both plans meter questions rather than seats or document count
- Predictable cost controls - message limits stop by default and overage requires explicit opt-in with a configurable cap
- Teaching-gap analytics - unanswered and trending questions can inform human follow-up and future preaching
- Explicit provider and retention details - the policy names OpenAI, Vercel, Trigger.dev, Stripe, and a post-cancellation deletion window
- Content ownership retained - terms say churches keep ownership while granting the limited license needed to operate the service
✗ Watch out
- Retrieval is not truth - a confidently cited answer can faithfully reproduce weak teaching, quote an old position, or misuse a source in a new situation
- Lead capture changes consent - a spiritual question can become a named prospect with a full transcript attached to a church dashboard
- No permanent free plan - the fourteen-day trial becomes at least $49 monthly if the church keeps the assistant live
- Public no-login access raises abuse risk - spam, prompt attacks, impersonation, minors, crisis disclosures, and malicious queries need tested handling
- Third-party AI processing - member and visitor messages are sent to OpenAI, and operating data also depends on several cloud providers
- New product evidence is thin - testimonials are useful but there is no independent answer-quality, safety, privacy, security, or ministry-outcome study
- BSB-only displayed Scripture - terms identify the Berean Standard Bible, which may differ from the translation a congregation teaches from
- Policy ambiguity needs clarification - guest messages are called not permanently stored, while prospect conversations are marketed as attached in the dashboard
Best for
- Churches with a substantial, current, rights-cleared sermon and document library and a named editorial owner
- Teaching teams that want cited discovery and a map of questions, not an autonomous digital pastor
- Church websites whose visitor-care team can respond promptly and responsibly to opt-in prospect records
- Congregations willing to publish plain AI, privacy, retention, emergency, and human-contact disclosures
- Organizations prepared to test doctrinal, pastoral, security, accessibility, and safeguarding cases before launch
Avoid if
- The church cannot assign a qualified person to curate sources and review high-risk, unanswered, and sampled conversations
- Members are likely to submit confession, counseling, abuse, self-harm, child, health, legal, or other confidential details
- Your privacy or child-safety requirements prohibit third-party generative processing or public no-login chat
- The sermon archive contains guest speakers, changed positions, licensed media, personal stories, or errors that have not been cleared and labeled
- Visitors could reasonably mistake generated answers for a direct statement, promise, or pastoral decision from church leadership
What Doctrinally.AI is
Doctrinally.AI is a retrieval-augmented generation service. It indexes the church’s source library, retrieves passages related to a question, and asks a generative model to compose a response with citations. The model has not become the pastor and is not literally “trained” into a new church-owned model merely because marketing uses that shorthand. Source selection constrains the answer but does not eliminate model knowledge, inference, omission, or error.
It is also a website engagement and contact-record product. Once a visitor provides identifying information, the church can receive a warm lead with conversational context. That may be useful hospitality, but it creates controller responsibilities for purpose, notice, access, retention, pastoral sensitivity, security, and follow-up. Evaluate the member and prospect use cases separately even though they share infrastructure.
Why churches consider Doctrinally.AI: every answer can lead back to the teaching it used
A normal website search returns titles and keyword snippets. A generic AI returns fluent prose whose origin is often unclear. Doctrinally.AI combines conversational discovery with an inspectable sermon moment or document page. That is especially valuable when someone remembers an idea but not the date, wants to compare a current question with a series, or needs the full message rather than a detached quotation. Unanswered-query analytics can reveal where the library genuinely lacks material.
Citations improve auditability only when the source corpus is governed. Create approved, archived, draft, superseded, guest, sensitive, and restricted states. Record speaker, date, series, Scripture, intended audience, rights, and corrections. Exclude counseling stories and private examples. Sample whether citations actually support each claim, not merely share vocabulary. Add a canonical statement of belief and contact routes, but do not let a short summary flatten areas where pastoral conversation is required.
Member AI and source library: make retrieval a doorway to human discipleship
Members can open a no-login hub through a URL or bulletin QR code and ask questions against uploaded sermons, PDFs, videos, and written devotions. The system says it acknowledges when the library lacks an answer. Analytics collect themes and misses so leaders can find recurring questions or under-taught subjects. Standard offers a branded subdomain; Enterprise adds a custom domain and automatic YouTube ingestion.
Place the assistant beside, not over, normal church care. Every screen should say it is generated, may be wrong, and is not private pastoral counsel. Provide “ask a pastor,” correction, report, and crisis controls. Review response samples by topic and vulnerable audience. Do not interpret a trend dashboard as spiritual surveillance or single out individuals for discipline, fundraising, or pastoral judgment from ambiguous queries.
Website Chat and prospects: useful hospitality requires genuine consent and restraint
The embeddable widget can open one tailored prompt, answer questions about the church, and invite a visitor to share name and email. Its key is locked to the configured origin, while rate limits operate at the edge and in Postgres. Captured information and the transcript appear in a Prospects dashboard, turning an anonymous exploration into a follow-up opportunity without requiring a separate contact form.
Do not hide the conversion. Before collecting identity, explain what will be sent to the church, who can read the transcript, why it will be used, retention, deletion, and whether prayer or pastoral content should be submitted. Make refusal easy and preserve anonymous browsing. Restrict prospect access by role, log exports, set deletion schedules, and forbid reuse for donor scoring or unrelated marketing. Reconcile the privacy policy’s guest-retention statement with the transcript feature in writing.
Citations, analytics, and automated sync: convenient scale increases editorial risk
Inline playback and page links let a reader inspect the retrieved evidence. Enterprise can pull a church’s existing YouTube channel, organize media into folders, and check weekly for new content. Administrators see popular topics, failed answers, and content gaps. These functions reduce manual ingestion and make a large archive conversational soon after setup.
Automatic freshness is not automatic approval. A live replay can include copyrighted music, a guest message, prayer requests, names, an uncorrected mistake, or content intended for one moment. Sync into quarantine, not straight to public retrieval. Require metadata and approval, transcribe accurately, review timestamp boundaries, keep correction and removal logs, and test whether deleted or unlisted YouTube content leaves every index, cache, transcript, and backup as expected.
Pricing
Trial
14 days free
Every plan can be tested without a setup fee or contract. Use synthetic questions and a deliberately small, reviewed source set before exposing the assistant to a public site or real congregation.
Standard
$49/month
Includes Website Chat, a Doctrinally subdomain, unlimited uploads and members, 1,500 questions each month, analytics, and email support. It does not include a custom domain or YouTube channel auto-sync.
Standard overage
$0.10/message
Only applies if a church opts in. Otherwise the monthly limit hard-stops with a friendly notice. Set a low cap, alerts, abuse controls, and a human alternative before enabling overage.
Enterprise
$99/month
Adds 3,000 monthly questions, custom domain and church branding, weekly YouTube auto-sync, priority support, and onboarding. Despite the name, public terms do not describe SSO, audit logs, DPA terms, or an uptime SLA.
Enterprise overage
$0.05/message
Optional and capped by the church. Confirm whether Website Chat lead-opening messages, follow-ups, failed answers, automated attacks, and administrator tests all consume the same quota.
Standard’s $49 monthly price is straightforward for a church that needs both member chat and a website widget. There is no annual discount listed in the reviewed public pricing, so budget $588 for a full year unless checkout states otherwise.
Enterprise doubles the monthly price to $99, or $1,188 annually at the listed month-to-month rate. The useful upgrades are not merely more messages: custom domain, church branding, weekly YouTube auto-sync, onboarding, and priority support change the administrative experience.
Question quotas need a definition. Ask whether one user turn, one generated response, retries, moderation refusals, widget greetings, lead capture, and follow-up all count. Load-test public abuse and seasonal spikes before assuming 1,500 or 3,000 will cover the congregation.
Hard limits are a good default. If overage is enabled, use the smallest practical cap and alerts at several thresholds. A bot consuming 1,000 Enterprise overage messages would cost $50; the more important cost is a public spiritual service becoming unavailable during a surge.
Staff time is part of ownership. Include source clearance, transcript review, evaluation, privacy and safeguarding design, prospect follow-up, corrections, analytics review, and export. A five-minute technical install is not a five-minute responsible launch.
Where Doctrinally.AI falls behind
Independent evaluation. Publish answer-supportedness, citation precision, refusal, crisis, abuse, self-harm, child, medical, legal, doctrinal, and prompt-injection results with methods and limitations.
Consent clarity. Explain the exact moment a guest transcript becomes persistent, who receives it, whether it can be deleted before sharing identity, and how visitors can remain anonymous.
Security evidence. Document MFA, administrator audit logs, encryption at rest, key management, backups, incident response, penetration tests, vulnerability reporting, DPA terms, and subprocessor regions.
Pastoral safety. Add visible escalation, local crisis guidance, child-safe behavior, abuse-reporting boundaries, self-harm refusal, and configurable human handoff rather than relying on ordinary chat copy.
Source governance. Churches need approval states, expiration, versioning, speaker and rights metadata, corrections, exclusions, restricted content, and removal verification across indexes.
Accessibility. Publish keyboard, screen-reader, zoom, reflow, contrast, focus, motion, captions, transcript, citation-player, and embedded-widget conformance evidence.
Operational assurance. Enterprise naming should come with an uptime target, status history, support objectives, disaster recovery, structured export, and documented shutdown process.
Translation and language. Public materials do not establish multilingual UI, multilingual retrieval quality, or alternatives to the BSB text used in generated Scripture displays.
Doctrinally.AI vs. church search vs. ChatGPT vs. a pastor
A conventional church-site search is predictable, cheap, and privacy-light, but it expects the visitor to know keywords and open several results. Doctrinally.AI synthesizes and cites an answer, lowering discovery friction. Keep an ordinary searchable sermon archive because it remains a transparent fallback, supports browsing, and does not require visitors to narrate a spiritual concern to an AI provider.
ChatGPT can discuss theology and files but is not automatically limited to one church’s approved corpus, embedded under its domain, equipped with sermon timestamp citations, or connected to a prospect dashboard. A church could build a custom equivalent, but then owns retrieval, evaluation, security, consent, and maintenance. Doctrinally packages that workflow; the policy confirms OpenAI still processes the messages underneath it.
A pastor can know the person, ask why the question matters, hold silence, recognize danger, pray, admit uncertainty, correct prior teaching, and remain accountable. The bot is available at midnight and can find an old sermon faster. Use that availability to surface sources and invite conversation—not to simulate private appointments, make pastoral decisions, handle crises, or let leaders avoid questions their people are actually asking.
The bottom line
Doctrinally.AI solves a real information problem elegantly: sermons contain years of answers that ordinary search rarely exposes, and playable citations make generated synthesis inspectable. Standard is a reasonable $49 pilot; Enterprise’s $99 tier earns its premium when custom branding and governed YouTube auto-sync save real work. The decision should turn on care and control, not installation speed. Start with approved low-risk material, publish transparent notices, test hostile and vulnerable prompts, resolve prospect-transcript retention, restrict dashboards, create immediate human and crisis exits, and measure supported answers rather than message volume. If church leaders will not review what the AI says in their name, they should not put it on their domain.
Alternatives to Doctrinally.AI
Frequently asked questions
How much does Doctrinally.AI cost?
Standard is $49 per month for 1,500 questions. Enterprise is $99 per month for 3,000 questions plus custom domain, branding, YouTube auto-sync, onboarding, and priority support. Every plan has a fourteen-day trial.
Does it train a new AI model on our sermons?
The practical design is retrieval over uploaded church content, followed by generation and citations. The privacy policy says messages are currently processed by OpenAI and neither content nor conversations are used to train AI models.
Do members need an account?
No. Member AI can be reached through a URL or QR code without login. That lowers friction but makes disclosure, rate limiting, safeguarding, abuse testing, and human handoff especially important.
What happens when the monthly message limit is reached?
The default is a hard stop, so the church is not unexpectedly billed. Administrators can opt into capped overage at $0.10 per Standard message or $0.05 per Enterprise message.
What does Website Chat collect?
It can ask a visitor for name and email and place the lead in a Prospects dashboard with the conversation attached. The church should disclose this before identity collection and clarify the product policy’s guest-message retention language.
Can answers still be wrong when they have citations?
Yes. Retrieval can choose the wrong source, and generation can misquote, omit context, combine incompatible statements, or apply an old sermon badly. A citation improves inspection; it does not certify truth.
What happens to data after cancellation?
The privacy policy says account data is retained during the subscription and church data is kept for thirty days after cancellation before permanent deletion. Confirm backups, exports, prospect transcripts, analytics, and deletion evidence in writing.
Sources & further reading
More AI Bible & Faith Tools
Magisterium AIA chatbot that refuses to answer Catholic questions from the open internet - and instead pulls every claim from 25,000+ Magisterial documents with citations.
BiblosOne of the clearest free demonstrations of meaning-based Bible search, now paired with substantial daily-reading tools—but semantic relevance is not interpretation, and the live service lacks the privacy and methodology pages needed for unqualified trust.
Church.tech (now Gloo Content Studio)The former Church.tech has become Gloo Content Studio, a capable sermon-repurposing workspace for clips, transcripts, devotionals, posts, podcasts, and publishing—with useful ministry context, two conflicting official price tables, and AI output that still needs pastoral review.
AnorA white-glove intelligence layer that connects a church or nonprofit’s existing email, giving, event, and commerce systems, resolves constituent identities, and answers cross-system questions—powerful for organizations with fragmented data, but costly and governance-heavy because the “complete picture” is sensitive by design.
AskMyChurchA church-trained AI assistant with unusually thoughtful citations, anonymous questions, pastoral boundaries and crisis routing—stronger than a generic chatbot, yet paired with absolute accuracy claims and incomplete retention, vendor and compliance detail.
Bible BotA carefully instructed Christian companion inside ChatGPT, with unusually candid limits and pastoral safety rules—but still a probabilistic AI whose model, privacy, memory, and access belong to OpenAI’s platform.