The Assisted Pastor Get the blueprint
Pastor to pastor

How I use an AI assistant to carry the church's admin load, so there's more room for people.

These are practical blueprints from a working small church. They cover the phone line, the inbox, Sunday's video, events, and receipts. Copy what helps and skip what doesn't.

Built with Grok Bot. Every blueprint here runs on Grok Bot, the AI assistant we use day to day. The ideas carry over to other assistants too.

Browse the blueprints Download the starter blueprint
Written by a pastor of a small church. Every example is anonymized.
Church text lineSat 4:12 PM
hello! what time is church tomorrow and is there something for my kids?
Hi, so glad you reached out! Sunday service is at [time]. We have kids programs from nursery through 5th grade, and someone will help you check in when you arrive. Parking info is here: [link]
great, thanks
Logged for staff: first-time guest texted "hello." Asked about service time and kids. No reply needed. Follow-up goes in Monday's roll-up.
Before anything else

The ground rules I run by

The assistant is a helper, not a pastor. Every blueprint on this site follows these four rules. If a setup can't keep them, I don't use it.

1A person approves what gets sent.

Drafts wait for me or a staff member. The only automatic messages are ones we wrote and approved ahead of time, like the FAQ answers.

2Nothing goes out unasked.

The assistant doesn't decide on its own to email, post, or text someone. It acts when it's asked, and only within the job it was given.

3People's details stay private.

Member info stays in our church systems. Summaries go only to staff. Nothing identifying shows up on this site.

4Care stays human.

The assistant handles logistics. Prayer, counsel, hard conversations, and decisions stay with people.

The blueprints

What it actually does at our church

Each blueprint covers the problem, what the assistant does, how to set it up, the guardrails, and the time it saves. Tap "Setup & guardrails" on any card.

Communication

Church phone & text line

The problem: Calls and texts come in at all hours, mostly the same few questions, and first-time guests slip through the cracks.

What it does: It answers calls and texts from our FAQ (service times, kids through 5th grade, parking, what we believe, upcoming events). It texts links like the volunteer page and passes small-group interest to a staff member. It logs first-time guests who text "hello," and writes a summary of every call with a likely-caller match from Planning Center.

Setup & guardrails Setup
  1. Write a one-page FAQ in your own voice.
  2. Get a church phone and text number from Bland (about $30 a month), then connect it and Planning Center (read-only).
  3. Choose which links it can text and who gets small-group handoffs.
  4. Test with staff for a week before going public.
Guardrails
  • It answers only from the approved FAQ. Anything else goes to a staff member.
  • The caller lookup is a "likely" match for staff and is never said back to the caller.
  • Pastoral or urgent calls go straight to a person.
Full walkthrough →
Communication

Auto-thanks for a questions inbox

The problem: After a big church announcement, we opened an inbox for questions. People deserved to know they'd been heard, but we couldn't answer everyone right away.

What it does: It sends one warm thank-you per person, never a second one, and lets them know the answer will come by direct email or in a church-wide update.

Setup & guardrails Setup
  1. Create a dedicated inbox.
  2. Write and approve one thank-you message.
  3. Have it keep a list of who's already been thanked.
  4. Have it group questions by theme for staff.
Guardrails
  • It sends only the pre-approved thank-you and never answers the actual question.
  • Each person gets one acknowledgement, total.
  • The real answers come from people.
Read blueprint →
Sunday

Sunday YouTube, done by Monday

The problem: The service video went up late or never got chapters, descriptions, or playlists.

What it does: It lines up chapters with the worship songs in that week's Planning Center plan, drafts a sermon write-up and description, and suggests playlists.

Setup & guardrails Setup
  1. Connect Planning Center Services and the church YouTube channel.
  2. Give it a sample write-up in your voice.
  3. Pick a standard playlist structure (series, topics).
Guardrails
  • Everything is a draft until I approve it.
  • I check the chapter times against the video before anything posts.
Read blueprint →
Inbox & admin

Daily inbox cleanup + reply pick-list

The problem: Important emails get buried under newsletters, receipts, and notifications.

What it does: It clears out the noise each day and gives me a short list of emails that need a reply. It drafts replies only for the ones I pick.

Setup & guardrails Setup
  1. Connect your email accounts.
  2. Tell it what counts as noise and who's always important.
  3. Pick a time for the daily list.
Guardrails
  • It archives instead of deleting.
  • It drafts only what I choose and never sends.
Read blueprint →
Inbox & admin

Weekday staff roll-up

The problem: Things that need the lead pastor are spread across texts, emails, and threads.

What it does: Each weekday morning it writes one summary of what actually needs me: decisions, approvals, and people to follow up with.

Setup & guardrails Setup
  1. Connect the channels staff use.
  2. Define "needs the pastor" with your team.
  3. Set a delivery time.
Guardrails
  • It only reads and summarizes. It doesn't reply for me.
  • Staff know what's included.
Read blueprint →
Events

Event planning: chili, Bunco, potluck

The problem: Fellowship events are simple until you're tracking who's bringing what.

What it does: It builds the timeline, task list, and sign-up form, then drafts reminders for the chili cook-off, Bunco night, or potluck.

Setup & guardrails Setup
  1. Give it the date, budget, and owner.
  2. Have it draft the sign-up form (Planning Center or Google Forms).
  3. Schedule draft reminders.
Guardrails
  • The event owner approves the form and every announcement.
Read blueprint →
Finance

Expenses & receipts

The problem: Receipts end up in pockets, inboxes, and camera rolls, and church and personal charges get mixed together.

What it does: It sorts charges into church or personal, forwards receipts to Ramp, and flags any that are missing.

Setup & guardrails Setup
  1. Connect email and your expense tool.
  2. Write simple rules for church vs. personal.
  3. Do a weekly "missing receipts" check.
Guardrails
  • It never approves or pays anything.
  • When it isn't sure, it asks.
Read blueprint →
Finance

Subscription cleanup

The problem: Software subscriptions pile up quietly.

What it does: It finds recurring charges and lists what's unused or duplicated, so a person can decide what to cancel.

Setup & guardrails Setup
  1. Have it scan card statements and receipts.
  2. Have it build a list with the owner and renewal date for each charge.
Guardrails
  • It recommends. A person cancels.
Read blueprint →
Family & kids

Kids curriculum prep

The problem: Volunteers need the lesson, leader notes, and supply list before Sunday, not during it.

What it does: It pulls the week's lesson and turns it into leader notes and a supply list.

Setup & guardrails Setup
  1. Point it to your curriculum files.
  2. Pick a template for leader notes.
Guardrails
  • The kids director reviews it before it's shared.
  • No child information is involved.
Read blueprint →
Personal

Smart home control

The problem: Not a church problem, just a fair look at the assistant outside the office.

What it does: It handles lights, routines, and reminders around the house. This is a low-stakes way to learn how the assistant works.

Setup & guardrails Setup
  1. Connect your home hub.
  2. Start with one or two routines.
Guardrails
  • Keep it separate from church accounts.
Read blueprint →
Setup

Several bots, one job each

The problem: One do-everything assistant is hard to trust and hard to fix.

What it does: We use separate assistants for the phone line, the inbox, and YouTube. Each has one job, its own rules, and only the access it needs.

Setup & guardrails Setup
  1. List your jobs.
  2. Give each bot only the accounts it needs.
  3. Write one short rulebook per bot.
Guardrails
  • Each bot gets the least access it needs.
  • Each one is easy to switch off by itself.
Read blueprint →
Kids

Kids ministry videos, ready for Sunday

The problem: Every week someone had to log in to the curriculum provider, download a pile of videos, guides, and printables, rename everything, and rebuild the kids-room playlists by hand.

What it does: It signs in to our curriculum provider and downloads that week's preschool and elementary materials: videos, leader guides, and printables. It sorts them into a folder for each week and age group, combines the printables into one print packet, and writes a one-page leader quick guide. It cleans up the file names, uploads the videos to Lightloop (our kids-room video player), and builds that week's playlists in teaching order. At the start of each month it adds the theme song, theme verse, countdown, and theme slides.

Setup & guardrails Setup
  1. Give the assistant its own login for the curriculum provider and for Lightloop.
  2. Pick a shared folder (we use Google Drive) and a standard layout: week, then age group, then videos and printables.
  3. Write down your playlist order once, for example welcome video, Bible story, then main idea.
  4. Run it with a staff member watching for the first few weeks.
Guardrails
  • A person reviews the playlists and materials before any kids see them.
  • It only uses the curriculum you already pay for and never adds outside videos.
  • If a file is missing or two files could match, it stops and asks instead of guessing.
  • It has no access to check-in or any information about kids or families.
Add to Grok Bot Read blueprint →
Featured blueprint

Walkthrough: the church phone & text line

This is the one other pastors ask about most. Here's how a call or text moves through it.

  1. Someone calls or texts the church number.It could be a Saturday night question or a Tuesday morning call.
  2. The assistant answers from our FAQ.It covers service times, kids programs through 5th grade, parking, what we believe, and upcoming events, using words we wrote.
  3. It sends a helpful link when it fits.For example, the volunteer page or the event sign-up.
  4. It hands off what needs a person.Small-group interest goes to the staff member who leads groups. Anything pastoral or urgent goes straight to a human.
  5. It logs first-time guests.When someone texts "hello," it's noted for staff follow-up.
  6. It writes a summary for staff.Every call gets a short summary with a likely-caller match from Planning Center, so we know who to follow up with.

What you need

  • A church phone/text number (we use Bland)
  • A written FAQ (one page is plenty)
  • Planning Center (read-only lookup)
  • One staff owner who reviews summaries

Guardrails

  • It answers only from approved content
  • The caller lookup stays internal and is never said to the caller
  • Easy handoff to a person, every time

Time saved

Coming soon

Free download

Get the starter blueprint

This is the short version of everything here, made for a small church staff starting from zero.

  • The guardrails checklist
  • An FAQ template for a phone/text line
  • A first-week setup plan
  • Sample instructions to give your assistant

Coming soon. Signups aren't open yet.

Newsletter

One practical blueprint, every other week.

Each issue covers what's working, what I changed, and what I'd skip. It's short enough to read between meetings.

Coming soon. Signups aren't open yet.

No spam, and unsubscribe anytime. We don't sell or share your email.

Who's writing this

A small-church pastor

I'm a pastor of a small church. Like a lot of pastors, I spent too many hours on admin and not enough with people. These are the setups that changed that for me, shared in case they help you.