An AI receptionist for a small church costs from nothing on a free trial tier to roughly $40 to $200 a month on paid AI plans, and $300 or more if trained people answer. Whatever the price, bereavement, hospital, crisis, abuse and safeguarding calls must pass straight to a person.
The price is the easy part. The rules about which calls the AI must never handle are the real work, and they belong to your leaders, not to a vendor's default settings. This tutorial gives a monthly cost frame for a part-time office, a hand-off list you can adapt, and a script for what the assistant says.
What the vendor pages tell you, and what they do not
Several products now market themselves to churches. One, Shepherdline, titles its site "AI Receptionist for Churches" and, when I read it in October 2026, showed three plans billed annually: $39 a month for up to 300 calls at one location, $95 for up to 1,000, and $199 for unlimited calls across up to five locations, plus a $299 non-refundable setup fee and a 14-day free trial. The page used a "$" sign without naming the currency, and I could not confirm what the plans include for call transfers, recordings or data, so ask before you rely on them. Another search result, Aligned, turned out to be church software (a free leader plan, a Pro plan at $9 a month, and modules from $10 a month) rather than a phone receptionist, a reminder to check what a page really sells before you compare prices.
General receptionist services publish prices too. Smith.ai's page lists live-staffed plans at $300 a month for 30 calls, $810 for 90 and $2,100 for 300, with extra calls at $11.50, $10.50 and $8.50, and charges for extra call-transfer destinations ($15 a month each) and for text notifications ($0.50 a call). Its AI receptionist has a free tier of 25 calls a month (extra calls $3 each) and a Pro plan from $150 a month for 75 calls, with extras at $2.50. Plans change often, so check the current page.
How many calls does your office really take?
Count before you shop. For two weeks, tally every call the office takes in a simple sheet: date, time, reason, minutes, and whether it needed a person. A small church with a part-time office might see something like this (illustrative).
| Reason for call | Calls a month | Needs a person? |
|---|---|---|
| Service times and directions | 25 | No |
| Hall hire enquiries | 12 | Take details, person follows up |
| Wedding, baptism and funeral enquiries | 10 | Yes, always |
| Rota and volunteer queries | 15 | Sometimes |
| Prayer or pastoral requests | 8 | Yes, always |
| Sales and wrong numbers | 20 | No |
| Total | 90 | About 30 need a person |
In that month, 45 calls (service times plus sales or wrong numbers) need no person at all, and 12 more only need details taken. Roughly 33 involve people in a way that matters. That is the share where an assistant adds little and a person adds everything.
A monthly price frame for a part-time office
With about 90 calls a month, here are the realistic routes, with illustrative figures. Check each against the vendor's current page.
| Option | What you get | Illustrative monthly cost |
|---|---|---|
| Voicemail and a clear greeting | Service times in the greeting, messages read on weekdays | $0 to $20 on most phone lines |
| Free AI trial tier | A small number of AI-answered calls, usually under 30 | $0 until the limit |
| Church-specific AI plan | Up to 300 calls at one location; $299 setup fee, billed annually | $39, or about $64 a month averaged over the first year |
| General AI receptionist, paid | 75 calls, then about $2.50 for each extra | $150, and more above the allowance |
| Live-staffed receptionist, lowest tier | 30 calls answered by trained people | $300, plus extra calls at $11.50 |
| Live-staffed, 90 calls | All your calls answered by people | $810 |
For this office, the church-specific plan covers all 90 calls for about $64 a month in year one (($39 x 12 + $299) / 12). A general AI plan would cost about $190 (75 calls at $150, plus 15 extra at $2.50). A human plan at 90 calls is $810, more than four times as much. Neither figure includes the time your staff spend reading messages and returning calls, which you will still do.
Add one cost people forget: the transfer destination. If the assistant sends urgent calls to the pastor's mobile, check whether the vendor charges for extra transfer destinations or for notifications, as the pricing page I read does. And ask what the monthly bill looks like in a bad month: a funeral week can double the call volume.
A part-time office, in sums
Suppose a church has an administrator working three mornings a week, 12 hours in all. The phone takes about 90 calls a month at roughly four minutes each, plus a minute to log: 450 minutes, or 7.5 hours. At $20 an hour that is $150 a month of staff time on the phone. An AI plan at $64 to $190 a month will not save money by itself. Its value is that calls are answered on the other two days, in the evenings and on Sundays, and that the administrator spends fewer minutes on service-time questions. If those hours go on visiting, planning or admin that is behind, that is the return. If they do not, the case is weak.
The calls that go straight to a person
This is the list to agree before anything else. Write it as a rule the system follows with no judgement involved: if the caller mentions or seems to mean any of these, stop and transfer, or give the emergency instruction.
- Bereavement. A death in the family, or a funeral request. A person phones back at once, or the call is transferred live.
- Hospital and illness. A member in hospital, or serious illness. Transfer to the on-call minister.
- Crisis and self-harm. Any mention of harming themselves or others. The assistant must say to call emergency services now if anyone is in immediate danger, and transfer to a person. It does not counsel.
- Abuse or safeguarding. Any concern about a child or vulnerable adult, including a disclosure. Transfer to your designated safeguarding lead, and follow your own safeguarding policy. The assistant must never promise confidentiality or ask probing questions.
- Domestic violence or someone afraid. Transfer, and give the emergency number if there is immediate risk.
- Prayer requests. Offer to pass it to someone and take the message. Do not let the assistant pray, console or advise.
- Complaints about a person. A complaint about a leader or volunteer goes to the person named in your complaints policy.
- Anyone who asks for a human. At any point, in any words. One request is enough.
- Anything the assistant is unsure about. If it does not understand twice, it hands over.
Your denomination or governing body may have its own rules for these calls, so check them before you set up anything. For a wider view of where admin AI stops and pastoral care starts, see the tutorial on ChatGPT for church work, admin versus pastoral care.
A script for what the assistant says
Write the exact words, in a warm tone, and keep them short. An illustrative script follows. Adapt it to your church's voice.
Opening
"Hello, you've reached the office at [church name]. I'm an automated
assistant. I can give service times and take a message, and I can put you
through to a person at any time. How can I help?"
Urgent or pastoral
"I'm sorry to hear that. I'll connect you to someone now. Please hold."
[Transfer to on-call number. If no answer after 20 seconds:]
"I couldn't reach anyone just now. I'm taking your name and number and
a minister will call you back within [30 minutes]. If anyone is in
immediate danger, please call emergency services now."
Safeguarding
"Thank you for telling us. I'm putting you through to the person who
looks after this. Please stay on the line."
Hall hire
"I can take your name, number, date and what the event is, and the
hall booker will call you back on [days]."Three details matter. The assistant says what it is, in the first sentence. It offers a person before it is asked. And the urgent script has a fall-back that never ends with the caller left in silence. If your system cannot do a fall-back like that, it is not ready for a church phone.
On-call rota: the part vendors cannot supply
A transfer needs somewhere to go. Before go-live, build an on-call rota with a named person for each day and a second person behind them, with mobile numbers loaded into the system. Illustrative arrangement for a church with two ministers and a safeguarding lead:
- Weekdays 9 to 5: the office, then minister A's mobile if the office does not answer within 20 seconds.
- Evenings and weekends: minister on call that week, then the other minister.
- Safeguarding calls at any time: the safeguarding lead, then their deputy.
Test the rota every month with a dummy call. A good habit is to run it before the first Sunday of the month. For other admin that benefits from a rota, see AI for church administration: rotas, notices and room bookings.
A week-by-week set-up and test plan
- Week 1. Tally calls, agree the hand-off list with your leaders, write the script, and build the rota.
- Week 2. Choose a vendor from three quotes. Read the call-recording and data terms, and the cost of extra transfers.
- Week 3. Set up the assistant with service times, hall-hire details and the hand-off rules. Run twenty test calls, including each category on the list, in different accents and speeds.
- Week 4. Go live for the weekday evening only, with a human reading every transcript each morning.
- Weeks 5 to 8. Extend to the other hours. Keep reading transcripts. Count: calls answered, transfers, wrong answers, callers who gave up.
Before you go live, run the same checks any phone assistant needs. Measuring an AI receptionist's return in the first 90 days gives the figures to track, and setting up an AI answering service that never misses an emergency shows how to test the urgent route.
Test calls to make before the first real caller
Use a volunteer who is not on the staff, and play each of these out loud. Note what the assistant said and whether it passed the call.
- "What time is the service on Sunday?" The answer must match your published times.
- "My mother died last night. I'd like to talk about a funeral." Immediate hand-off, no questions about dates.
- "I'm worried about a child in our group." Immediate hand-off to the safeguarding lead.
- "I don't think I can go on." The emergency instruction, then hand-off.
- "Can I hire the hall for a party on the 14th?" Takes details; no promise of availability.
- "Please let me talk to someone." Hand-off after one request.
- A call in a noisy room, or with a strong accent. The assistant should ask again, then hand over, not guess.
Record the result in a table and do not go live until every sensitive call passes twice in a row.
Recording, consent and what callers are told
A phone assistant listens to people at vulnerable moments. Tell callers at the start that the call is automated and may be recorded, and give them a way to reach a person without being recorded. Ask the vendor how long recordings and transcripts are kept, who can read them, whether they train models, and how to delete one. A pastoral call recorded and left in a vendor's system for years is a risk you do not want. If you have members in the EU, data-protection law such as the GDPR may apply to recordings and to what is said on them, so ask a qualified adviser. A sample church AI policy on one page shows what volunteers should know, and the data side is covered in church member data rules for AI tools.
Tell the congregation too. A line in the notice sheet, "our office phone now uses an automated assistant for simple questions; you can always ask for a person," avoids surprise.
Two calls, handled badly and handled well
Examples teach the rules better than lists, so here are two illustrative calls, each told as what the caller hears.
A funeral enquiry that went wrong
A caller says her father died this morning and asks about a service. A poorly set up assistant says it is sorry to hear that, then asks which date she prefers and offers three slots from the hall diary. It has treated a death as a booking. The caller, in shock, has been handed a menu. The fault was not the voice but the missing rule: the word "died" should have triggered an immediate transfer to the on-call minister, with the date question left to a person.
The same call, set up properly
The assistant says it is sorry and that it is putting her through to someone now. If the minister's phone rings out, it says it is taking her number and that a minister will call within thirty minutes, and it asks only for her name and number. It asks nothing else. The call ends in under a minute, and the transcript is waiting for the minister with the words "bereavement, father, this morning". The difference is three lines of rule, written in advance.
A quieter case: hall hire
A caller asks whether the hall is free on a Saturday in six weeks for a fortieth birthday. The assistant takes the date, number of guests, whether there will be music or alcohol, and the caller's contact details, and says the hall booker will phone on Tuesday or Thursday. It must not say "yes, it's free", because only the booker knows about regular bookings and your hire policy. Those four questions are exactly what a booker would ask first, so the call saves a round of phone tag.
Mistakes to watch for in the first month
- The assistant answers a service time wrongly. Special services, Christmas and Easter hours often differ. Give it the full calendar and review it each month.
- Transfers that ring out. The on-call number is wrong or the phone is on silent. Test it, and set a fall-back, as in the script.
- Prayer requests answered with advice. A chatty assistant may offer comfort or a Bible verse. Set it to take the message and say that someone will be in touch, nothing more.
- Callers get stuck in loops. After two misunderstandings it should offer a person. Count the calls where callers hang up early; that is the signal.
- Staff stop reading transcripts. After three quiet weeks, the review slips and an error runs for a month. Put it in the administrator's weekly tasks.
Each of these can be seen in a transcript. That is why the plan keeps a person reading them every morning for the first month, and weekly after that.
If your church is larger
A congregation with several staff and 300 calls a month changes the sums. At the human-service figures quoted earlier, 300 calls on the top live plan is $2,100 a month, which is probably more than the phone is worth, while a church-specific plan lists 300 calls at $39 a month. An AI plan with human back-up on the urgent routes, or an AI plan for routine calls with the office team answering the rest, is a more likely fit. Ask vendors for the price at 300 calls, including extra transfers and notifications, and ask what happens to calls over the allowance: some products stop answering, others charge by the call. Spread the cost across the departments that benefit, such as the hall-hire budget, to see whether each pays its share.
Larger churches also have more roles to route to: a children's lead, a youth lead, a finance contact. Give each one a clear reason to be called and a fall-back, and keep safeguarding on its own route that does not depend on the front office.
When not to use an AI receptionist at all
For some churches the right answer is a better voicemail. If you get fewer than about 30 calls a month, nearly all from members who know the number, the cost and risk of an AI assistant outweigh the gain. A clear greeting with service times, a mobile number for urgent pastoral calls and a promise to reply within a working day will do the job. For website questions about weddings, baptisms and hall hire, an AI chatbot for churches may be a cheaper first step than a phone assistant.
If you would rather work through the rules and numbers with someone, that is what my AI implementation consultation covers; you can get in touch here.
A one-page rule sheet to pin up in the office
Office phone rules (agree and review each year)
1. The assistant says it is automated in its first sentence.
2. These calls always go to a person: bereavement, hospital, crisis,
abuse or safeguarding, domestic violence, prayer requests,
complaints about a person, and anyone who asks for a human.
3. If a call cannot be transferred, a named person calls back within
[30 minutes], and the caller hears the emergency-services line.
4. Transcripts are read each weekday morning by: __________
5. Recordings are kept for [ ] days, then deleted.
6. The on-call rota is tested on: __________
7. Monthly review: calls answered, transfers, errors, complaints.Questions church leaders ask about AI on the office phone
Should an AI ever answer a call about a death or crisis?
It should answer only to pass the call to a person straight away, or to give a number to call at once, never to counsel. Set bereavement, hospital, crisis, abuse and safeguarding calls as automatic hand-offs, and test them weekly so a failure is caught before a family finds it.
Is a free plan enough for a small church?
It can be for a trial. Some receptionist products offer a small number of free calls a month, but a church with a part-time office often takes more than that. Count a typical month of calls first, then compare the plan limits and the cost of extra calls.
Do callers need to be told it is an AI?
Yes, tell them at the start in a friendly line, and offer a person at any point. Some places have rules about disclosing automated calls and recording, so ask a qualified adviser, and tell your congregation what the system does.
What happens when the office is closed on Sunday?
Decide it in advance. The assistant can give service times, take a message for Monday, and pass urgent pastoral calls to the on-call person's mobile. Without an on-call rota, urgent calls have nowhere to go, and that gap is the first thing to fix.
Further reads
- AI Answering Service for Funeral Homes: Cost and First-Call Rules — First-call rules for another sensitive phone line.
- ChatGPT Prompts for Churches: 10 Admin Jobs, No Sermons — Ten admin jobs ChatGPT can take on in a church office.
- AI Church Website Builder: Wix, Squarespace or GoDaddy Airo Compared — A website that answers questions before they become calls.
- Church Translation With AI: A Test to Run Before You Pay a Vendor — Test AI translation before paying a vendor.
- How Much Does an AI Receptionist Cost for a Small Business? — General AI receptionist costs for any small business.
- Gym AI Receptionist: Monthly Cost, Tours, Trials and Class Bookings — Four AI receptionist plans costed for one small gym, plus what they can book for tours, trial passes and classes, and when a person takes over.
- Can You Use ChatGPT for Church Work? Admin Versus Pastoral Care — A four-question rule that separates church admin from pastoral care, with worked examples, a placeholder method and a one-page policy for staff and volunteers.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Smith.ai pricing pages (live receptionist plans $300 for 30 calls, $810 for 90, $2,100 for 300; AI plans free for 25 calls, Pro from $150 for 75 calls; checked October 2026). Aligned page (church software, not a phone receptionist; Leader Pro $9 a month, modules from $10 a month, checked October 2026). Shepherdline's site (AI receptionist for churches; plans $39, $95 and $199 a month billed annually, $299 setup, currency not named, checked October 2026). Cost sums are illustrative.