The AI agents your staff will use this year are the same ones your next visitors will use to pick a church. An AI agent is AI that does the task instead of telling you how: a chatbot drafts the email, an agent sends it and books the room. AI agents for churches are ready for errands with a human approval step. They are not ready for anything pastoral, and they should never touch member data or the church card.
I’m Thomas Costello, Executive Pastor at New Hope Hawaii Kai, a church of about 300 in Honolulu, and I’ve run REACHRIGHT, a church marketing agency of 17 people, since January 1, 2016. My team uses agents every week. An agent helped research and fact-check this post, and I read every line before it went up. Every product fact below was verified October 14, 2026.
What Is an AI Agent, and How Is It Different From a Chatbot?
An AI agent is software that takes a goal, makes a plan, and carries it out by using tools on your behalf: a web browser, your inbox, your calendar, your files. The AI agent vs chatbot difference is action. A chatbot like the original ChatGPT answers in text and stops. An agent keeps going. It clicks the button, reads the next page, notices it hit a login screen, and asks you what to do. Chatbots tell. Agents do.
Here’s the plain-English version I give my staff at New Hope:
| You ask for... | A chatbot gives you | An agent gives you |
|---|---|---|
| A retreat venue | A list of camps to look up yourself | Availability checked on six camp websites, prices in a spreadsheet, inquiry forms filled and waiting for your OK |
| A volunteer reminder | A drafted email | The email drafted, the roster pulled from your schedule, and 40 personalized messages queued to send |
| Broken links on your website | Advice on how to find them | Every page crawled and a list of the dead links with where each one lives |
| A messy shared drive | A folder structure suggestion | The files renamed, sorted, and duplicates flagged, with a log of every move |
One more term you’ll hear: agentic AI. It’s the industry’s word for this whole category of AI that acts. When a vendor says its product is “agentic,” it means the product can take steps on its own instead of only answering questions. Gartner has already warned about “agent washing,” vendors rebranding ordinary chatbots as agents, and predicts that over 40% of agentic AI projects will be canceled by the end of 2027 because of cost, unclear value, or weak risk controls (Gartner, June 2025). So be suspicious of the label. Ask what the product actually does with its hands.
Which AI Agents for Churches Are Worth Using Right Now?
As of October 14, 2026, a church can choose from eight AI agents made by five companies: OpenAI, Anthropic, Meta, Google, and xAI. Two are built for office work, three write code, and three are personal assistants or always-on teammates. The landscape moved fast this year. OpenAI retired its original ChatGPT agent and replaced it with ChatGPT Work in July 2026, and Meta launched Muse in September. Every row below was checked against the vendor or reputable coverage this week. If you only try one, my pick for a church office is Claude Cowork. If your staff already lives in ChatGPT, use ChatGPT Work. If you have one technical staffer who likes building things, add Claude Code for that person.
| Agent | What it does | Access (verified Oct 2026) | Our church guide |
|---|---|---|---|
| ChatGPT Work (OpenAI) | Works across connected apps, files, and the web from a cloud computer; asks before sensitive actions | Launched July 9, 2026 on paid ChatGPT plans | ChatGPT for Churches |
| Claude Cowork (Anthropic) | Desktop agent that works directly in your files, folders, and connected apps, no terminal | Included in paid Claude plans, Pro from $20/mo | Claude Cowork for Churches |
| Claude Code (Anthropic) | Terminal agent that builds tools, scripts, and documents for your most technical staffer | Included with Claude Pro, $20/mo | Claude Code for Churches |
| OpenAI Codex | Coding agent that writes, edits, and tests software | Bundled with ChatGPT plans | OpenAI Codex for Churches |
| Meta Muse | Personal agent that sends email, books travel, and connects to calendar, payments, and shopping | Launched Sept 8, 2026, US only, Muse app or WhatsApp; free tier plus $20 and $100/mo | Meta Muse for Churches |
| Gemini Agent (Google) | Multi-step tasks on the web inside the Gemini app | Google AI Ultra subscribers, US, 18+ | Gemini for Churches |
| Grok Bot (xAI) | Always-on AI teammates, each with its own cloud computer | Beta since Aug 11, 2026, via SuperGrok Heavy or Cursor plans | Grok Bot for Churches |
| Grok Build (xAI) | Terminal coding agent | Beta since May 2026, SuperGrok Heavy | Grok Build for Churches |
Sources: SiliconANGLE, July 9, 2026; OpenAI Help Center; Claude pricing, checked October 14, 2026; Reuters via Khaleej Times, Sept 9, 2026; Gemini release notes. Prices are standard list prices. OpenAI, Anthropic, and Google run nonprofit programs, covered in each guide.
ChatGPT Work replaced the original ChatGPT agent
OpenAI’s first agent, “ChatGPT agent,” launched in July 2025. OpenAI’s help center now says that agent is no longer available and points users to ChatGPT Work, a new agent that launched July 9, 2026 alongside GPT-5.6 (SiliconANGLE). It runs on a cloud computer, works across connected apps and files, and asks a human for approval before sensitive actions. If someone on your staff read about “agent mode” last year, that’s the product that’s gone. ChatGPT now reaches about 1 billion weekly users (Yahoo Tech, August 2026), so this is the agent the most people in your congregation will meet first.
Claude Cowork and Claude Code are the office-work agents
Claude Cowork is the agent I point most church offices to first. It runs inside the Claude desktop app, works in your actual folders, and doesn’t need a terminal, so your office manager will open it. Claude Code is its technical sibling for the one staffer who likes building things. Anthropic’s pricing page now folds Cowork into Claude itself on paid plans (claude.com/pricing, October 2026). My Cowork guide and Claude Code guide have the setup and the nonprofit discount.
Meta Muse puts an agent inside WhatsApp
Muse is Meta’s personal AI agent, launched in the US on September 8, 2026 through a Muse app and WhatsApp (Reuters via Khaleej Times). It connects to email, calendar, payments, and shopping, and it can send email and book travel. Meta delayed the release from April to make it more secure, and Reuters reported that internal testers saw an agent route around guardrails to expose iCloud photos. Your members will have this on their phones before your staff has a policy for it. My Meta Muse guide for churches goes deep.
The coding agents and the xAI betas
OpenAI Codex and Grok Build write software, and most churches need neither. Grok Bot, xAI’s always-on teammate, is still a beta behind $120-to-$300 subscriptions. My verdicts are in the Codex, Grok Build, and Grok Bot guides.
Will AI Agents Choose Churches for People?
Yes, and sooner than most pastors think. The same agents your staff will use for errands are the ones your future visitors will use to find a church. A young couple who just moved to your town won’t scroll Google for an hour. They’ll tell their assistant, “Find us a church near the new house with a good kids’ program and a 10 a.m. service, and put it on our calendar.” The agent reads what it can find about every church nearby, picks a few, and books the visit.
Local businesses are already living this. Use of ChatGPT and other AI tools for local business recommendations jumped from 6% to 45% of US consumers in one year, making AI the third most-used recommendation source behind Facebook and Google (BrightLocal Local Consumer Review Survey, February 2026, n=1,002).
Nobody has published hard numbers on AI choosing churches yet. I don’t need a study to see where this goes. Half of American adults already use AI chatbots (Pew Research Center, June 2026), and Google’s AI Mode already books restaurant tables in eight countries (WinBuzzer, April 2026). A Sunday visit is the next reservation.
An agent can only recommend what it can read. If your service times live inside an image, your Google Business Profile lists hours from 2022, and your “Plan a Visit” page is a PDF, the agent skips you and books the church down the street whose information was clean. Being legible to AI means plain-text service times, a current Google Business Profile, a clear plan-a-visit page, and structured data like schema markup that tells machines exactly what your church is. I’ve written the full playbook in AI SEO for churches and in how to show up when people ask ChatGPT for church recommendations.
Will an AI agent find your church?
Before agents start booking visits, see what AI search says about your church today. Our free Churches Near Me test asks AI assistants for churches in your area and shows whether you show up or get skipped. Takes about a minute.
What Can Church Staff Hand an AI Agent Today?
Church staff can hand an AI agent any task that is repetitive, multi-step, low-risk, and easy to check before it goes out. Research, scheduling drafts, form-filling, spreadsheet cleanup, and website maintenance all fit. The test I use at New Hope is simple: if a capable volunteer could do it with a checklist and I’d still want to look before it ships, an agent can do it.
These are the jobs I’d hand an agent this month at a church of 200 to 1,000 with a staff of five to fifteen:
| Job | What the agent does | Human checkpoint |
|---|---|---|
| Event and retreat research | Compares venues, dates, prices, and capacity across websites | Staff picks the venue and signs |
| Volunteer scheduling drafts | Builds next month's rotation from availability and drafts reminders | Ministry lead approves before anything sends |
| Vendor and registration forms | Fills repetitive forms with church info you've approved | Staff reviews and clicks submit |
| Shared drive and spreadsheet cleanup | Renames, sorts, dedupes, and logs every change | Office manager spot-checks the log |
| Website maintenance | Finds broken links, outdated event pages, and wrong service times | Comms lead makes the edits |
| Sermon research packets | Gathers commentary summaries, historical background, and cross-references | The pastor studies, prays, and writes |
| Meeting follow-up | Turns staff meeting notes into a task list and drafts the follow-up email | Meeting lead edits and sends |
Notice the right-hand column. Every job has a human at the end. That’s the design. When I ran a sales team of 15 at Faith Highway, the reps who did the best work weren’t the ones with the most freedom. They were the ones with a clear process and a manager who looked at the deal before it closed. Agents are the same. Give them a lane and a checkpoint.
If you want a running start, my team built a free library of AI prompts for pastors that works as agent instructions too.
What Should a Church Never Hand an AI Agent?
A church should never hand an AI agent pastoral care, spiritual discernment, sensitive congregant data, or spending authority. Those four lines stay put when the technology gets better. They belong to the people God has called and the congregation has trusted.
- Pastoral care. No agent answers a grieving widow, follows up on a counseling session, or texts the teenager who missed youth group for three weeks. Those are shepherding moments.
- Anything that needs the Holy Spirit's discernment. Who to call into leadership, what to preach, how to handle church discipline, when to speak and when to wait. Discernment is a spiritual act, and an agent has no spirit.
- Sensitive congregant data. Giving records, counseling notes, prayer requests, background checks, and anything about minors stay out of agents entirely.
- Spending authority. No saved church card, no giving-platform login, no "go ahead and book it." An agent can build the cart. A person pays.
AI is a tool, not a shepherd. An agent can run your errands. It can't know your people.
Pastors are mostly getting this instinct right. A Barna and Gloo survey of 442 US Protestant pastors found 71% describe themselves as cautious about AI, and only 24% use it to write or edit sermons (Barna, June 2026). Lifeway Research found just 10% of Protestant pastors use AI regularly, with another 32% experimenting (Religion Unplugged, April 2026, phone survey of 1,003 pastors). Caution is healthy. So write the line on paper, and then put agents to work inside it.
Why Are AI Agents Riskier Than Chatbots?
AI agents are riskier than chatbots because a wrong answer from a chatbot is a bad paragraph, and a wrong action from an agent is an email you can’t unsend. An agent that can touch your inbox can break your inbox. Three risks matter for a church office.
Prompt injection is the big one. It means hidden instructions planted on a web page or in an email that trick an agent into doing something you never asked for, like forwarding your inbox or changing a setting. Security researchers at Palo Alto Networks’ Unit 42 have documented real web pages with hidden text aimed at AI agents (Unit 42). Anthropic reported in November 2025 that its best defenses held a browser agent’s attack success rate to about 1%, and said plainly that 1% “still represents meaningful risk” (Anthropic). One in a hundred is not a number I’d bet the church inbox on without an approval step.
Runaway actions are the second. In July 2025, an AI coding agent on Replit deleted a company’s database during a code freeze and then wrongly said it couldn’t be rolled back (eWeek). In February 2026, a Meta AI security researcher said her open-source agent bulk-deleted her real inbox and ignored her commands to stop (TechCrunch). If a security researcher can lose an inbox, your volunteer coordinator can too. Those two stories are why I won’t let an agent near an inbox at REACHRIGHT or New Hope without an approval step turned on.
Quiet data exposure is the third. An agent signed into your church email can read everything in it, including the counseling thread from last spring. Whatever you connect, assume the agent can see.
How Do You Write a Church AI Policy for Agents?
A church AI policy for agents is a one-page document that names who can use agents, which tools are approved, what data agents may touch, what they may never do, and which actions need a human’s approval. Most churches don’t have one. An Exponential survey of about 594 church leaders, fielded in 2025, found 73% had no AI policy at all (Exponential, 2025), and that survey skews toward leaders already interested in AI. Writing one puts you ahead of most churches by Friday.
- Name an owner. One staff member approves new agent tools and answers questions. At most churches over 200, that's the executive pastor or operations director.
- List approved tools. Name the agents staff may use on church work. Everything else is off-limits on church accounts.
- Set the spending limit at $0. Agents never hold a church card or a giving-platform login. A person completes every purchase.
- Require approval before anything sends, buys, deletes, or publishes. Turn on the confirmation settings every major agent offers, and never switch them off for speed.
- Sort data into tiers. Public info is fine. Internal docs are fine with approved tools. Giving, counseling, prayer requests, background checks, and minors' data are never connected.
- Give agents their own accounts. Separate logins with only the access each job needs. Never a pastor's personal account.
- Review monthly. The owner reads the agent logs once a month and adjusts the list. Tools change every few weeks; the policy should too.
That covers agents specifically. For the broader rules on disclosure, honesty, and AI-generated images, start with my 7 church AI rules, then add these seven lines underneath.
How Should a Church Roll Out Its First AI Agent?
Your first 30 days with an AI agent should prove one small job works before you hand it a second. Churches that start with the whole office end up with a mess and a staff that quits trying. Here’s the rollout I recommend to churches over 200:
- Week 1: Pick one errand. Choose a single job from the hand-off table above, like event research or broken-link checks. Write down what “done” looks like.
- Week 1: Set up a separate account. Give the agent its own login with access to only the folders and apps that job needs. Turn on every approval setting.
- Weeks 2 and 3: Run it with a human watching. One staff member runs the job, approves every action, and notes where the agent got stuck or guessed.
- Week 4: Review the log. The policy owner reads what the agent did, checks the output, and decides whether the job is worth keeping.
- Day 30: Expand by one. If the first job saved time and broke nothing, add a second job. If it didn’t, fix the instructions or drop it.
Frequently Asked Questions
AI Agents for Churches: The Bottom Line
AI agents for churches are worth using now, inside a fence. Hand them the errands and keep a human at every checkpoint. Shepherding and the offering plate stay with the people God called to carry them. Write the seven-line church AI policy this week, before anyone on staff connects an agent to anything.
Your next hundred visitors will use agents to decide where to go on Sunday, so make sure those agents can read your church. Run the free AI visibility test today. If you want my team to look at how AI and Google see your church today, book a free Church Marketing Review. It’s a 30-minute call, and we’ve run it for 800+ churches.
Thomas Costello is the founder and CEO of REACHRIGHT (since 2016) and Executive Pastor at New Hope Hawaii Kai in Honolulu. He planted a church in Austin in 2007, led The Journey in Madison, Wisconsin, and ran a 15-person sales team at Faith Highway before starting REACHRIGHT.
More Resources for Churches
- AI for Churches: The Church Leader’s Guide, every AI guide we publish in one place
- AI for Churches: What It’s Good For and Where the Line Is, the cornerstone guide
- Claude Cowork for Church Staff, the agent I recommend first
- Meta Muse for Churches, the agent your members will have on WhatsApp
- 7 Church AI Rules, the policy to write first
- AI SEO for Churches, how to get your church recommended by AI
