.png)
Nobody sat down and decided to build a confusing phone tree.
It started with two options. Then the youth pastor wanted his own. Then the preschool. Then someone added a submenu for the food pantry because the office kept fielding those calls. Six years later a first-time visitor calls to ask what time the service starts and hears forty seconds of options before hanging up.
That's how every bad phone tree gets built. Reasonably, one decision at a time.
If you've already concluded yours isn't working, this page is about what to do instead. Four real options, what each costs, and who each one actually fits.
Before comparing options, get specific about which problem you have. They need different fixes.
Nobody's available during office hours. One person answers, and they're often on another line or away from the desk.
Nobody's available after hours. Weekdays are covered; nights and weekends go dark.
The menu itself is the problem. Someone is there, but callers give up before reaching them.
Most churches have the second and third at once. Worth naming which one is actually costing you, because the answer changes what you should buy.
Someone answers every call during business hours.
Cost: roughly $800-1,500/month part-time.
Good for: churches large enough to already have office staff, where the phone is a real part of someone's job description.
The catch: business hours only. Evenings, weekends, holidays, sick days, and vacations are uncovered — and a meaningful share of church calls arrive outside 9 to 5, because that's when people are off work and thinking about their lives. Around 70% of U.S. churches have fewer than 100 weekly attendees and only about 20% have two or more paid staff, so for most congregations this isn't on the table anyway.
Skip the menu. One greeting, one beep, a real promise to call back within a set window.
Cost: $0.
Good for: churches with genuinely low call volume and someone disciplined enough to check messages twice a day, every day.
The catch: it runs straight into the 67% number. Roughly two-thirds of callers won't leave a message at all, so you never learn they called. This option is honest and free, but it only works if you're realistic that a large share of calls simply won't reach you.
Calls roll to the pastor's or office manager's mobile after hours.
Cost: $0.
Good for: very small churches with one person who genuinely doesn't mind.
The catch: burnout, and it's not hypothetical. The pastor takes "what time is the Christmas Eve service" during dinner and on vacation. It also gives out a personal number you can't easily take back. Churches try this constantly and quietly abandon it within a year.
The call is answered by something that talks instead of asking people to press numbers. It handles routine questions from a script you write, and routes urgent calls to a real person on your team.
Cost: roughly $20-60/month. ChurchCalls.ai is $19.99/month flat with 100 minutes included and no setup fee.
Good for: small and mid-size churches that need coverage outside office hours without adding payroll.
The catch: it isn't a person, and for genuinely pastoral conversations you want a person. The whole design question is how fast it hands off. Ask any provider to walk you through exactly what happens when someone calls about a death in the family. If they can't answer that in plain language, keep looking.
| Option | Cost/month | After hours? | Best fit |
|---|---|---|---|
| Live receptionist | $800-1,500 | No | Churches with existing office staff |
| Voicemail + callback | $0 | Delayed | Very low call volume |
| Forward to cell | $0 | Yes | Short-term only |
| Answering service | $20-60 | Yes | Most churches under 200 |
Sometimes replacing it isn't realistic this quarter. Three changes that cost nothing:
Cut to three options, no submenus. Pull the call logs. You'll likely find two categories cover most of the volume.
Put a human option first, not last. "Stay on the line to speak with someone" should come before the menu, not after forty seconds of it.
Say the service times in the greeting. If that's your most common question — and it usually is — answer it before anyone presses anything.
Those three take an afternoon and will measurably reduce hang-ups.
ChurchCalls.ai is option four. The answering is handled by AI, which is worth saying plainly rather than burying.
That word makes plenty of church leaders uneasy, and the caution is fair. So here's the honest version: the technology isn't the selling point. It's what makes flat-rate, around-the-clock coverage affordable for a church that could never staff a 2 a.m. phone. You write the script. You define what counts as urgent and who it goes to. It doesn't counsel anyone, and it isn't supposed to — when a call needs a human, its only job is getting there fast.
You don't need to understand it to use it, same as the copier.
Someone called your church last Tuesday at 7 p.m. What happened?
If you don't know, that's the actual problem — not the phone tree. You can't improve something you can't see. Pull your call logs this week and look at how many calls came in outside office hours and how many connected to anyone.
That number will tell you which option on this page you need. It might be free. It might be $20. Either way you'll be deciding with information instead of guessing.
See how ChurchCalls.ai answers your church's calls — or call it yourself first and hear how it handles a real question.
