It’s Monday morning, and Sunday’s connect cards are in a stack by the keyboard. Before anyone gets to them there’s next week’s rota with two gaps in it, thank-you notes for three first-time givers, the announcements, and the list of who is in the hospital and who asked for prayer. Most of that is typing and looking things up. A small part of it is the reason the office exists.
AI is good at the first part. It should stay well away from the second. The trouble is that the two are often the same email. This post draws the line, job by job, so your staff and your elders can agree on it before any tool is switched on.
Two tests for any job
Would you be comfortable if the member saw exactly how this was made? A welcome drafted from what a guest wrote on their card, then read and signed by a staff member, passes. A condolence note generated and sent overnight does not.
Does it need judgment about someone’s life? If a job needs someone to know what’s happening in a family, how a person is really doing, or what a pastor would say, a person does it. The assistant can remind them it’s due and bring them what you already know about that person. It doesn’t do the job.
What AI should do
First-time guest follow-up
This is the clearest win. On Sunday afternoon someone types in the connect cards. On Monday the office writes the same welcome, with small changes, to every new face. Some weeks it goes out on Thursday. Some weeks it doesn’t go out at all.
An assistant can have a welcome drafted for each guest by Monday morning, using what they told you: new to the city, two kids, interested in serving. It can suggest a group with the reason for the suggestion. A staff member reads each one, changes what needs changing, and sends it. The guest gets a personal note, early in the week, from a real person.
Volunteers
Rotas fail in two ways: gaps nobody notices until Saturday, and the same faithful people serving every week until they quietly stop. An assistant can suggest a rota that spreads the load, and it can answer the question nobody has time to work out: “Who has served every week since spring without a break?” That list is worth a thank-you and a week off.
Giving
A first gift deserves a personal thank-you, and so does a returning one. Drafting those notes is exactly the kind of work an assistant does well. It can also sort stopped recurring gifts into the ones where a card expired and the ones worth a call. The first needs an update link. The second needs a person.
Giving is also where permissions matter most. Whatever tool you use, the assistant should see giving only when the person asking is allowed to.
Welcome
- First-time guest follow-up, drafted for each personCommunity
- Group suggestions with the reason (“new to the city, has two kids”)Community
- Onboarding that adapts to what someone told youCommunity
- Automated group formation for large cohortsAdd-on
Serve and gather
- Rota suggestions that spread the load and flag burnoutCommunity
- Events, sign-ups and reminders set up from a sentenceCommunity
- An after-event summary: first-timers, returners, no-showsCommunity
Give
- A thank-you drafted for every first and returning giftCommunity
- Stopped gifts sorted into “card expired” and “worth a call”Community
What we build, and which tier each part is in.
What AI shouldn’t do
Pastoral care, on its own
Anything pastoral stays with people. That includes hospital visits, grief, marriage trouble, a crisis at home and a request for prayer. An assistant can make sure a follow-up on a care note isn’t forgotten, and it can route a prayer request to the person who should see it. It must never send a pastoral message on its own. For grief, illness and crisis, we’d go further and say: write it yourself.
Read care notes it shouldn’t
Care notes are written in confidence. An assistant with access to every record will summarize one for anyone who asks, unless it follows the same permissions as everything else. Ask any vendor whether a volunteer can ask the assistant about a care note. The answer should be no, because the volunteer can’t read the note either.
Grade people’s faith
Attendance and giving tell you something about a pattern, and nothing about a person’s walk with God. A tool that ranks members by an engagement score invites staff to treat people as numbers. Flag a change in pattern, give the reason, and let a pastor decide what it means. There’s more on this in why a reason beats a score.
Handle a safeguarding concern
If something a child, a parent or a volunteer writes reads like a safeguarding concern, it should go straight to a named person. It shouldn’t sit in a queue or turn into a draft.
Care
- Follow-up reminders on care notes, visible only to the people who should see themCommunity
- Prayer and help requests routed to the right personCommunity
- Anything that reads as a safeguarding concern goes straight to a named personCommunity
What it looks like on a Monday
Every first-time guest, followed up
Sunday’s new faces arrive Monday morning with a welcome drafted for each, and a group suggested with the reason.
From Sunday’s sermon to Wednesday’s study
The talk becomes a study guide, discussion questions and a summary for group leaders to review and send. A scoped add-on.
The first screen of the week is a short list: who came for the first time, who has drifted, which group went quiet, which gifts stopped. Each item has a reason and a draft. The Monday briefing covers what belongs on it.
Where to start
Pick one job. First-time guests are the best place, because the need is clear and the risk is low. Run it for a month with a person approving every draft. Ask the staff member doing it what they changed and why. Then decide on the next job together.
Write down your line on pastoral care before you start, and share it with your elders or board. Once it’s written, it’s much easier to hold.
What we build
We build an assistant into the church platforms we make, with everyone’s whole story in one place your church owns. Your assistant runs in your cloud, on your own data, under your own account. It sees only what the person asking may see, never trains anyone’s model on your members, and drafts rather than sends. It keeps one rule above the rest: Drafts, and your team sends. Every message to a member waits for a person to approve it. You can switch on automatic sending for low-risk jobs you choose, like event reminders. Anything pastoral is never automatic.
AI usage is paid to your own provider at cost, like hosting, with no markup and no platform fee. We estimate it in your scope. The full list of what it does, and every commitment it keeps, is on the AI Assistant page.
Questions we hear
Will an AI assistant send pastoral messages?
Not the one we build. Every message to a member waits for a person to approve it. You can switch on automatic sending for low-risk jobs you choose, like event reminders. Anything pastoral is never automatic.
Can small group leaders see giving or care notes through the assistant?
Only if your permissions already let them. It follows your roles and permissions. Care notes stay with the people allowed to read them.
Are prayer requests used to train an AI model?
No. Your provider account runs under business terms that exclude training on your data.
Which parts are in the core build?
Guest follow-up, rota suggestions, giving thank-yous and care reminders are part of the Community tier. Turning a sermon into a study guide is a scoped add-on. AI usage is paid to your own provider at cost, like hosting, with no markup and no platform fee. We estimate it in your scope.