// Guide · 26 min read · Updated July 2026
ChatGPT Prompts for Church Marketers
50+ battle-tested prompts, a system-prompt template for your church, and three weekly workflows that save a solo comms director 10+ hours a week. Steal, edit, ship.
// What is in this guide
- 01.The philosophy: judgment beats prompts
- 02.The anatomy of a great prompt (CRAFT)
- 03.Build your church's system prompt
- 04.Sermon repurposing prompts
- 05.Email prompts
- 06.Social media prompts
- 07.Website & landing page prompts
- 08.Strategy & planning prompts
- 09.Team & operations prompts
- 10.Guardrails & disclosure
- 11.Three weekly workflows
- 12.Ten mistakes to stop making
- 13.FAQ
Judgment beats prompts
The best prompt is a good editor.
AI does not replace church communicators. It replaces the parts of the job that were never the job — the throat-clearing, the first-draft blank-page grinding, the fifth caption rewrite. The parts that ARE the job — knowing your church, hearing your pastor's voice, discerning what to say and what to leave unsaid — get more valuable, not less.
What follows is a working library of prompts we've stolen, refined, and shipped across dozens of churches. They will not think for you. They will let you think faster.
Every prompt below assumes you have built the system prompt in section 3. Load that first. Then paste the prompt. Then edit the output. In that order. Always.
// The framework
The anatomy of a great prompt (CRAFT)
Five elements. Every great prompt has all five. Every bad prompt is missing three.
C
Context
Set the scene. Who is the church? What is the audience? What just happened? What is the goal? 3–5 sentences of context beats every clever prompt trick.
R
Role
Assign the AI a specific role: 'You are an experienced church communications director at a 1,200-attender evangelical church in the Southeast US.' Roles anchor voice, vocabulary, and defaults.
A
Ask
State the task in one clear sentence. 'Write X. About Y. For Z. To achieve Q.' Vague asks produce vague outputs.
F
Format
Explicitly name the output format. 'Three social captions under 220 characters each' — not 'some social captions.' Length, structure, count, tone.
T
Test + Iterate
Never accept the first draft as final. Feed one criticism at a time. 'Make it 30% shorter.' 'Cut the third paragraph.' 'Add one specific example.' Iteration is where good becomes great.
Build your church's system prompt
The single highest-leverage practice in this guide. Build it once. Load it at the start of every session. Save it as a Custom GPT or Claude Project. Steal this template, fill in the bracketed variables, and use it forever.
System prompt template
You are the communications director for [Church Name], a [size] [tradition] church in [City, State]. You have been in the role for years and know the church's voice, audience, and values deeply. Voice: [warm / direct / thoughtful / plain-spoken / other]. Never use churchy jargon (unpack, journey, faith walk, do life together, radical). Never use hype phrases (game-changer, next-level, absolutely amazing). Sentences are short and clear. Paragraphs are 2–4 sentences. Audience: our people are [primary audience — e.g., families with kids, urban singles, second-career adults]. Reading level: 8th grade. Assume no theological background unless the piece is for members. Theology: we teach [key doctrinal position, e.g., historic protestant, complementarian, egalitarian, affirming, non-affirming]. Never contradict this without flagging. Format defaults: unless I specify otherwise, keep outputs under 300 words. Use plain markdown. No emoji unless asked. Always: - Answer directly. No throat-clearing intros. - Use specific numbers, names, and dates when possible. - Flag anything you would rank as low-confidence with [CHECK]. - Offer one alternative version if the first draft feels generic. Never: - Invent theological positions the church has not stated. - Write in the pastor's first-person voice without explicit permission. - Publish a claim as fact if you are less than 90% confident.
Sermon repurposing prompts
One sermon becomes 20+ pieces of content. These 5 prompts do most of that lifting.
Sermon → 5-piece social kit
Below is this Sunday's sermon transcript. Task: produce 5 pieces of social content: 1. One Instagram carousel outline (5 slides, first slide = hook, last slide = CTA to watch full sermon) 2. Three text-only Instagram/Threads posts (each under 220 chars, each standalone, each quotable) 3. One 90-second Reels/TikTok script (hook in first 3 seconds, one big idea, one CTA) 4. One LinkedIn post for church leaders (350 words, one insight from the sermon reframed for leadership) 5. One Facebook post for our regulars (150 words, warmer/pastoral tone) Voice: [system prompt applies]. Use exact phrases from the transcript when they land — do not paraphrase good lines into worse ones. SERMON TRANSCRIPT: [paste]
Sermon → email recap
Below is this Sunday's sermon transcript. Task: draft a 250-word Monday-morning email recap. Structure: - One-sentence hook that names the big idea - 100 words summarizing the sermon's argument - One quote from the sermon (pulled verbatim, not paraphrased) - One "so what" — a concrete next step or reflection question - 40-character subject line + 90-character preheader Voice: [system prompt applies]. Do not sound like a book report. SERMON TRANSCRIPT: [paste]
Sermon → small group discussion guide
Below is this Sunday's sermon transcript. Task: produce a 1-page small group discussion guide. Structure: - 2-sentence recap (in case someone missed Sunday) - One opening icebreaker question tied to the topic - Three text-based questions (each rooted in a specific passage/verse the sermon used) - Three application questions (progressing from head → heart → hands) - One prayer prompt Format: markdown. Tone: warm, discussion-facilitating, never lecture-y. SERMON TRANSCRIPT: [paste]
Sermon → sermon series pitch page
We are launching a new sermon series titled "[TITLE]". Below is the series overview and week 1 sermon draft. Task: draft a landing page (800 words) at /series/[slug] that: - Names the series and the arc in the first 100 words - Answers "why now, why this" for a first-time visitor - Lists all X weeks with title, date, primary passage, and one-sentence tease - Includes 3 companion resources (a book, a podcast episode, an article) tied to the theme - Ends with 2 CTAs: "Watch week 1" and "Get the series recap by email" Voice: [system prompt applies]. Design for someone who has never attended before. SERIES + WEEK 1: [paste]
Sermon → sermon clip pull-list
Below is this Sunday's sermon transcript with timestamps. Task: identify the 5 best clips for social video (Reels, TikTok, Shorts). Criteria: each clip should be 30–90 seconds, self-contained, hooked in the first 3 seconds, and quote-worthy standalone. Prioritize honesty + emotion + specificity over polish. For each clip, output: - Start and end timestamps - The verbatim quote - A 1-sentence rationale for why this clip works - A 60-character caption for the post SERMON TRANSCRIPT WITH TIMESTAMPS: [paste]
Email prompts
Weekly rhythm, guest sequences, event invites. Load these three and stop rewriting emails from scratch.
Weekly all-church email
Draft the weekly all-church email for this Sunday. Context: - Sermon topic: [TOPIC] - Sermon big idea (one sentence): [BIG IDEA] - This Sunday's info: [SERVICE TIMES / SPECIAL NOTES] - One next step to feature: [NEXT STEP] Structure: - Subject line under 45 characters (specific, benefit-oriented, no clickbait) - Preheader ~90 characters (extends subject, does not repeat it) - One-sentence personal opener from the pastor - 100-word primary message (sermon recap or teaching snippet) - This Sunday's info (concise, 2 lines max) - One specific next step (the featured next step, ~40 words) - Sign-off from the pastor, first name only Total under 300 words. Voice: [system prompt applies].
First-time guest email #1
Draft the first email in our 5-part first-time guest sequence — sent day 0. Context: sent within 24 hours of the guest visiting for the first time and filling out a connect card. The tone is warmly personal, from the lead pastor, no ask beyond "here's what to expect next." Structure: - Subject line: personal, not "Thank you for visiting" - 3-paragraph body, each 2-3 sentences - One line naming what will happen next in the sequence (sets expectation) - Signature from pastor, first name only, with real reply-to invitation Total under 200 words. Feel like a note, not a form email.
Event RSVP email
Draft an email invitation to our upcoming [EVENT NAME] on [DATE]. Event details: - What it is: [DESCRIPTION] - Who it's for: [AUDIENCE] - Why it matters (the actual reason someone should come, not the marketing reason): [WHY] - Logistics: [WHERE / WHEN / COST / RSVP LINK] Structure: - Subject line under 45 chars, benefit-oriented - 200-word body - One clear CTA (the RSVP link, framed as an action) - P.S. line with one specific detail (a quirky attendee incentive, a story from last year, a warning about capacity) Voice: [system prompt applies]. Do not oversell.
Website & landing page prompts
Landing pages, About rewrites, and FAQ pages engineered for both humans and AI answer engines.
Landing page for a new class or ministry
We're launching [MINISTRY / CLASS NAME].
Details:
- What it is: [DESCRIPTION]
- Who it's for: [AUDIENCE]
- When / where: [LOGISTICS]
- What makes it different: [DIFFERENTIATOR]
- The actual outcome for the participant: [OUTCOME]
Task: write a landing page (600–800 words) with this structure:
- H1 (under 8 words, specific, promise-oriented)
- Subheadline (1 sentence, states audience + outcome)
- 3-paragraph "Who this is for" section, plain-language
- "What to expect" section (5-item list, each item 15 words max)
- "What people say about this ministry" (3 short testimonial-style quotes — mark [FROM REAL PEOPLE, TO BE COLLECTED])
- FAQ section (5 real questions)
- Two CTAs: primary ("Join / Register") and secondary ("Ask a question")
Voice: [system prompt applies]. AEO-friendly — H2s as literal questions, immediate answers.About-us page rewrite
Below is our current About page.
Task: rewrite it to be dramatically more useful to a first-time visitor.
Rules:
- Answer these questions in the first 300 words: What is this church? Who is it for? What do we believe (in one sentence)? Where are we located? When can they visit?
- Ban all inspirational-sounding filler ('journey', 'community of believers', 'passionate about', 'love God, love people')
- Include founder, founding date, size, and denomination as literal facts
- End with 3 next-step CTAs: Visit / Watch a sermon / Ask a question
- Optimize for AEO — literal questions as H2s, direct answers underneath
Total 600–900 words. Voice: [system prompt applies].
CURRENT ABOUT PAGE:
[paste]FAQ page from real questions
Below is a list of real questions our welcome team, comms team, and connect cards have logged over the past 6 months. Task: produce a comprehensive FAQ page at /faq that: - Groups questions into 5–7 logical categories - Answers each question in 40–80 words (extractable by AI + snippet-friendly) - Uses each question verbatim as an H2 (do not sanitize or reword) - Includes one "we don't know / here's how we think about it" honest answer (churches with no ambiguity feel fake) - Ends with a "Didn't find your question? Ask us here" CTA Voice: [system prompt applies]. QUESTIONS LIST: [paste]
Strategy & planning prompts
The prompts that turn AI from a writer into a strategist. Use quarterly.
Sermon series companion content plan
We're launching a [X-week] sermon series on [TOPIC], starting [DATE]. Task: produce a companion-content plan covering: - Weekly email theme for each of the X weeks - 2 social posts per week per platform (Instagram, TikTok, Facebook) - One long-form piece per week (blog post OR podcast OR video) - 3 companion resources total for the series (book / podcast / article) - One "series recap" content plan for week X+1 - A landing page outline at /series/[slug] Format as a table: Week | Email theme | Social | Long-form | Companion. Voice: [system prompt applies].
Content calendar for a slow month
We have low announcements and no big events during [MONTH]. Task: propose a content calendar for the month that: - Fills the weekly email slot with teaching-forward, not announcement-forward, content - Includes 3 pillar posts per week on socials (Show / Teach / Invite mix) - Uses this as an opportunity to build a "companion resource library" — 4 evergreen pieces we can re-share indefinitely - Includes one email-list-growth push (a lead magnet or 5-day devotional) Format as a week-by-week table.
Analyze last quarter's data
Below is our website analytics, email metrics, and social metrics for the past 90 days. Task: produce a 1-page analysis with: - The 3 clearest signals about what is working - The 3 clearest signals about what is not working - The 2 biggest surprises - 3 specific, concrete changes to make for next quarter - Any metric that seems off/wrong and warrants investigation Be direct. Do not diplomatically soften findings. Assume the reader wants truth, not comfort. DATA: [paste]
Team & operations prompts
Meetings, hiring, and volunteer care. Reclaim the hours you were spending on admin.
Meeting agenda from a rambling email
Below is a rambling email chain about an upcoming meeting. Task: produce a clean 1-page meeting agenda with: - 1-sentence meeting purpose - Decisions the meeting needs to make (explicit list) - Discussion topics with time allocations (aim for 60 min total) - Named owner for each agenda item - Pre-read materials - Success criteria for the meeting EMAIL CHAIN: [paste]
Job description for a new hire
We're hiring a [ROLE] for our church staff.
Context:
- Size of team: [SIZE]
- Reports to: [SUPERVISOR]
- Location: [ONSITE / HYBRID / REMOTE]
- Salary range: [$X–$Y]
- The real reason we're hiring this role (the actual problem): [PROBLEM]
- What success looks like at 6 months: [OUTCOME]
Task: draft a job description that:
- Opens with the actual problem this role solves
- Lists 5 must-do responsibilities (not aspirational)
- Names 3 hard skills required and 3 soft qualities
- Names 3 things this job is NOT (prevents applicant mismatch)
- Ends with the honest ask ("apply if...")
Voice: [system prompt applies]. Feel like a real invitation from a real team.Volunteer thank-you generator
Task: draft 10 personalized thank-you notes to volunteers.
Below is a list of volunteers with their name, role, and one specific thing they did well this quarter.
Constraints:
- Each note is under 80 words
- Each note references the specific thing they did (do not generalize)
- Written as if from the pastor, first name only
- Warm, specific, not gushing
- One line of practical impact ("Because of the coffee bar you set up, first-time guests stayed 20 minutes longer on average")
VOLUNTEER LIST:
[paste]Guardrails & disclosure
The eight rules every church using AI should adopt. Put them in your one-page AI content policy. Review annually.
Guardrail 01
Never publish AI-generated content as the pastor's own voice without their review and edit.
Why: Trust is the church's most valuable asset. Ghost-writing has historic precedent, but the pastor must have last word on anything under their name.
Guardrail 02
Always fact-check theological claims, historical references, and Bible references.
Why: AI hallucinates confidently. Assume every specific claim is 90% right and check the 10%.
Guardrail 03
Disclose AI use in contexts where transparency is expected.
Why: Podcast episodes, published articles, and formal writings often expect authorship disclosure. When in doubt, disclose.
Guardrail 04
Never use AI for pastoral counseling or crisis response.
Why: A human pastor is not a nice-to-have here. The theological and ethical weight requires human presence.
Guardrail 05
Never generate photorealistic images of real people or events that didn't happen.
Why: Deceptive imagery erodes trust globally, not just for your church. Ethical line, not just legal one.
Guardrail 06
Store prompts and system prompts in a shared team library.
Why: Institutional knowledge. When staff turn over, the AI infrastructure of the church doesn't leave with them.
Guardrail 07
Review AI use quarterly at a team level.
Why: The tools change monthly. What was a great prompt in Q1 is often outperformed by a better model + shorter prompt in Q3. Iterate.
Guardrail 08
Have a written AI content policy.
Why: One page. Named tools, named use cases, named guardrails, named disclosure requirements. Prevents ad-hoc decisions in a pressure moment.
Three weekly workflows
These are the actual workflows we've watched save a solo comms director 10–15 hours per week. Steal them wholesale.
Workflow 01
Weekly sermon workflow (90 minutes → 4 hours of output)
- →Monday 8am — Upload Sunday sermon transcript. Run 'Sermon → 5-piece social kit' prompt. Save outputs to editing queue.
- →Monday 9am — Run 'Sermon → email recap' prompt. Send to pastor for a 15-minute review + approval.
- →Monday 10am — Run 'Sermon → clip pull-list' prompt. Send timestamps to video editor.
- →Monday 11am — Draft social captions from social kit. Schedule Tuesday–Sunday posts in scheduler.
- →Tuesday 8am — Publish email recap. Ship first social post. Move on.
Workflow 02
Weekly email workflow (15 minutes)
- →Wednesday 9am — Fill in the sermon topic, big idea, and Sunday next step into the 'Weekly all-church email' prompt.
- →Wednesday 9:05am — Generate 2 subject line variants.
- →Wednesday 9:10am — Edit for voice + accuracy (5 min).
- →Wednesday 9:15am — Schedule for Monday 7am send.
Workflow 03
Monthly content-planning workflow (60 minutes)
- →Last Monday of the month — Export the previous month's analytics data.
- →Run 'Analyze last quarter's data' prompt on the export.
- →Take the 3 recommended changes into a 20-minute team huddle.
- →Run 'Content calendar for a slow month' (or a season-specific variant) for the coming month.
- →Ship the calendar into the team's project management tool.
Ten mistakes to stop making
Mistake 01
Typing 'write me a Sunday email' and expecting a Sunday email.
Fix: The gap between a lazy prompt and a good prompt is 90 seconds of context. Always give role, context, task, format, and constraints.
Mistake 02
Publishing the first draft AI produces.
Fix: Great AI output is a 70% draft. The editing step is where church voice lives.
Mistake 03
Letting AI write theology or scripture references unchecked.
Fix: AI hallucinates confident-sounding Bible references. Verify every scripture reference and doctrinal claim.
Mistake 04
Using AI to fake the pastor's voice on personal notes.
Fix: 'Congrats on your baby!' from an AI-drafted, pastor-signed email is a trust-destroying moment when discovered. Never automate personal warmth.
Mistake 05
No system prompt.
Fix: The single highest-leverage lever. A good system prompt takes 30 minutes to build and 10x's your output quality.
Mistake 06
Not saving prompts that work.
Fix: Build a team prompt library. Every good prompt should be findable and reusable next week without being rewritten.
Mistake 07
Using AI to add filler because 'longer is better.'
Fix: AI is really good at inflating word count. Don't. Aim for shorter with more density.
Mistake 08
Assuming AI knows your church.
Fix: It doesn't. It knows generic evangelical churches. Every prompt needs specifics: your denomination, your size, your voice, your context.
Mistake 09
Never disclosing AI use where transparency matters.
Fix: Formal publications, sermon transcripts labeled as such, and any 'personal' content should disclose. Trust compounds.
Mistake 10
Standardizing on one model and never testing others.
Fix: Try the same prompt in ChatGPT, Claude, and Gemini once a quarter. The best tool for your voice will shift over time.
Frequently asked questions
What is a ChatGPT prompt for church marketers?+
A prompt is the structured instruction you give to ChatGPT, Claude, or Gemini to produce a specific kind of output — a sermon recap, an email draft, a social caption, a landing-page outline. Good prompts contain role, context, task, constraints, examples, and format. Bad prompts contain 'write me a Sunday email.'
Which AI model should church marketers use?+
Use the right tool for the job. ChatGPT (GPT-5) for general drafting, brainstorming, and structured content. Claude (Sonnet 4.5) for long-form writing that needs voice fidelity and nuance. Gemini for research + Google Docs integration. Perplexity for citation-backed research. Most church teams standardize on ChatGPT + Claude.
Will AI replace church communicators?+
No. It will replace church communicators who don't use AI. The role shifts from producer to editor — from writing 40 pieces from scratch to generating 100 drafts and shaping the 20 that ship. Judgment, voice, theology, and pastoral discernment don't scale down.
Is it okay for churches to use AI?+
Yes, with clear guardrails. AI is a tool like a projector or a printing press. What matters is what you produce with it — accurate, honest, faithful, human-checked content. Never let AI have the final word on doctrine, pastoral counsel, or the pastor's voice. Always disclose when required (some denominations, some publishing contexts).
What should churches NEVER use AI for?+
Pastoral counseling. Prayer responses in crisis. Anything published as if written personally by a specific pastor without disclosure. Deep theological argument without expert review. Photorealistic images of real people or events that didn't happen. Anything that would deceive a member about human care.
What's the difference between a prompt and a prompt template?+
A prompt is one-time — you type it, get output, move on. A template is reusable — you build the structure once, fill in variables (sermon title, series name, week number), and generate consistent output every time. Templates are how church teams compound AI efficiency.
How do I get AI to write in my pastor's voice?+
Feed it 3–5 of the pastor's actual sermons or writings as reference material. Explicitly ask it to match the voice — cadence, sentence length, vocabulary, theological posture. Then edit. Even best-case, expect 70% of the way there; the pastor's team closes the final 30%. Never publish unedited AI content as the pastor's own.
How much time does AI actually save a church communications team?+
For a solo comms director: 8–15 hours per week if used well. Sermon-to-social repurposing goes from 4 hours to 45 minutes. Weekly email drafts from 90 minutes to 15. New-guest sequences from a 3-day project to a 3-hour project. The savings compound over months.
Should we use AI to write sermons?+
No. Full stop. Sermons are the pastor's voice, born of study and prayer and community. AI can help with research, illustrations, alternate phrasings, or generating discussion questions AFTER the sermon is written. But the sermon itself is not an AI job.
Can AI help me plan a sermon series?+
Yes — for structure, arc, and complementary content. Give it your series topic, key texts, series length, and audience. Ask for weekly big-idea options, complementary passages, illustration ideas, and companion content. The pastor's team picks and refines.
What is a system prompt and why does it matter?+
A system prompt is the persistent instruction the AI operates under across every message in a conversation. For church use, a good system prompt names the role ('You are a communications director at a mid-size evangelical church'), voice, audience, theology guardrails, and format defaults. It's the single highest-leverage lever in AI use.
How do we build an AI content policy for our church?+
A one-page policy that covers: what AI can be used for (drafting, ideation, repurposing), what it cannot be used for (pastoral counsel, sermon writing, unedited publishing), disclosure requirements, review-before-publish rules, and named tool approvals. Adopt, review annually.
Which AI tools should churches pay for?+
For most churches: ChatGPT Team ($25/user/month) or Claude Pro ($20/month). Beyond that: Descript for video/podcast editing, Otter.ai or Fireflies for transcription, Canva Magic for design assistance, and Beehiiv/ConvertKit's built-in AI for email. Total: ~$50–150/month for a small team.
How do I stop AI from producing generic 'AI-sounding' content?+
Feed it specificity in the prompt — real names, real numbers, real details. Give it examples of the voice you want. Ask for one specific claim per paragraph. Explicitly ban filler phrases ('In today's fast-paced world', 'It's important to note'). Iterate with 'make it more specific' and 'add one real example' until it lands.
What are chain-of-thought prompts?+
Prompts that ask the model to reason step-by-step before answering. Adding 'think through this carefully before responding' or 'first list the top three angles, then pick the strongest, then write' produces measurably better output on complex tasks. Free performance upgrade.
People also ask
Beginner
What is prompt engineering?
The practice of writing structured instructions that get high-quality output from language models. Structure, specificity, and iteration matter more than clever tricks. Any church communicator can learn the fundamentals in a week.
Is ChatGPT free for churches?
Free tier available with rate limits. ChatGPT Plus ($20/month) and ChatGPT Team ($25/user/month) unlock better models, longer context, and image generation. For a comms team, Team is worth every dollar.
Can I use AI to write sermons for volunteer preachers?
No. Even volunteer preachers should preach their own words. AI can help with research, illustrations, and structure — but the voice must be theirs.
What if AI gives me wrong information?
Assume it will. Verify every scripture reference, historical claim, statistic, and doctrinal position. AI's confidence is not correlated with its accuracy.
Intermediate
How do I get consistent voice across all AI outputs?
Build a robust system prompt that describes voice, audience, theology, and format defaults. Save it. Load it at the start of every session. This single practice creates 80% of voice consistency.
Should I use ChatGPT's custom GPTs feature?
Yes, for repeatable workflows. Build a 'Church Comms GPT' with your system prompt, uploaded style examples, and 5–10 reference documents. Share with your team. Update quarterly.
How do I train AI on my church's voice specifically?
Custom GPT with 5–10 examples of your best writing, a detailed system prompt describing voice, and explicit 'match this' instructions in each prompt. True fine-tuning is possible but usually not worth the cost for churches.
What is few-shot prompting?
Providing 2–3 examples of desired output within the prompt itself. 'Here are two examples of the voice we want: [example 1], [example 2]. Now write a third in the same voice.' Often the single highest-impact technique for voice matching.
Should we build our own church AI tool?
Rarely worth it. ChatGPT + Claude + a system prompt library + Custom GPTs covers 95% of what a custom tool would do, at 5% of the cost. Build only if you have specific security requirements or unique workflows.
Advanced
How do we integrate AI into our tech stack?
Zapier or Make.com connections between ChatGPT/Claude API and your ChMS, email tool, and CMS. Use cases: auto-generate email drafts from Planning Center service items, auto-tag connect card responses, auto-summarize small group leader reports. Requires API tier of ChatGPT/Claude ($5–20/month usage-based).
What is retrieval-augmented generation for churches?
Feeding an AI a specific knowledge base (past sermons, member handbook, doctrinal statements) so it answers based on YOUR content, not generic knowledge. Tools like Custom GPTs, Anthropic's Claude Projects, or Notebook LM make this accessible without engineering.
How do we handle AI in a multi-staff church?
Shared system prompts, shared Custom GPTs, quarterly team training, a written policy, and one AI-fluent person who owns the practice. Do not let each staff member reinvent prompts independently — the knowledge won't compound.
What's the ROI of investing in AI for a church staff?
For a 3-person comms team: $75/month in tools + 10 hours upfront training = ~30 hours/month saved (10 per staff). At $30/hour loaded cost, that's $900/month value on ~$150/month spend. 6x ROI, usually within 60 days.
How will AI change the role of church communicator over the next 3 years?
From producer to editor. From execution to judgment. From writing 40 pieces to shaping 100. Voice and theological discernment become more valuable, not less. Communicators who ONLY know execution get automated. Communicators who lead thinking get promoted.
Should churches build public-facing AI chatbots?
With extreme caution. Public bots can hallucinate theology, give bad pastoral advice, or embarrass the church. If deployed, scope tightly (only answers from your FAQ, always escalates to human on pastoral topics, never speaks in the pastor's voice). Better path: use AI internally, keep humans on the front-line.
Reclaim your Mondays. Ship the work that matters.
At NACMC you'll build your church's system prompt, run through the three workflows live, and leave with a prompt library your team can start using Monday. Laptops open. Real work. No panels.
Social media prompts
Captions that don't sound like every other church's captions. Hooks that stop the scroll.
10 Instagram caption variants for one photo
TikTok / Reels hook lines
One post → 5 platform-native versions