AI Answering Service: What It Costs and Where It Breaks

An AI answering service picks up the calls you can't take: while you're under a sink, after hours, or when two people ring at once. A good one books the caller in and sends you a short summary. A bad one puts a slow, stiff robot between you and someone who already has water on the floor. Which one you end up with depends less on the brand than on how the agent is set up and what it's allowed to do.

We build voice agents at PASMO, including a production receptionist for an appliance repair company that books jobs straight into its field service software. This guide covers what these products cost, where they tend to break, and how to start small. One disclosure: we build on Retell, one of the platforms below, so we have a stake in how it's described. We've kept that out of the numbers.

What an AI Answering Service Actually Does

Under the marketing, most products follow the same path.

1. Your number forwards calls to the service, always or only when you don't pick up.
2. A voice agent answers and works out what the caller wants.
3. It collects the facts: name, callback number, address, the problem, how urgent it is.
4. It acts through whatever it's connected to: books a slot, creates a customer record, texts a link, or transfers the call.
5. It sends you a summary, a transcript, and usually a recording.

Step four is where products differ. An agent that only takes messages is a friendlier voicemail. One that can see your availability and create the job works more like a part-time dispatcher, and the cheapest plan on paper may only do the first kind of work.

Three kinds of products

Ready-made services such as Rosie and Goodcall are sign-up products with a monthly plan. Hybrid services such as Smith.ai add live receptionists who can take over complex calls. Voice AI platforms such as Retell, Synthflow, or Bland are toolkits: you or a developer build the agent and connect it to your own systems, paying per minute plus the build and upkeep.

What It Costs in Late 2026

Vendors bill by four different units: minutes, unique callers, calls, or raw usage. The table shows one example of each, plus a human answering service for comparison.

Billing model	Example	Published price	What to watch
Bundled minutes	Rosie	$49/mo for 250 min, $149 for 1,000, $299 for 2,000. 7-day free trial.	The page doesn't say what happens once the bundle runs out. Ask.
Unique callers	Goodcall	$79/mo for 100 unique callers, then $0.79 each. $129 for 500, then $0.26. $299 for 2,000, then $0.15.	A phone number counts once a month, and spam and wrong numbers don't count. A month with lots of new callers costs more.
Per call	Smith.ai AI Receptionist	Free for 25 calls, then $3 per call. Pro from $150 for 75 calls, $270 for 150, about $500 for 300. Extra calls $2.17 to $2.50.	Every answered call counts by default. Known spammers are filtered, and you can remove up to 10% of calls per cycle as spam. The price of a live-agent transfer isn't on the page.
Per minute, build your own	Retell	Headline range $0.07 to $0.31/min. The site's own estimator example comes to $0.15/min. $2/mo per number.	The rate depends on the voice and AI model you pick. Building and maintaining the agent is extra.
Human answering service	Typical market rate	$0.75 to $1.50/min	Overage on virtual receptionist plans can run $1.75 to $5.40/min.

Vendor prices come from each vendor's own pricing page, read on November 11, 2026. The human rates come from OnceHub's September 2026 cost guide; OnceHub sells an AI receptionist, so it has a reason to make humans look expensive. And these prices aren't like for like: a plan that takes messages and one that books into your calendar are different products at any price.

A worked example

Say 200 calls a month go to the service, the average call lasts three minutes (600 minutes), and those calls come from 150 different numbers. These are made-up figures, so swap in your own.

• Rosie: the 1,000-minute plan covers it for $149.
• Goodcall: Starter is $79 plus 50 extra callers at $0.79, so $118.50. If all 200 calls come from different numbers, Starter rises to $158 and the $129 Growth plan becomes the cheaper choice.
• Smith.ai: the 150-call plan at $270 plus 50 extra calls at $2.30 comes to $385, before any live-agent transfers.
• Retell: 600 minutes at the estimator's $0.15 is $90 in usage plus $2 for the number. Its headline range would put it anywhere from $42 to $186. Build and upkeep come on top.
• Human answering service: $450 to $900.

That's the full-volume case. If you start the way we suggest below, with overflow and after-hours calls only, the bill is much smaller. At 50 calls and 150 minutes a month, Rosie's $49 plan covers it, Goodcall Starter stays at $79 (50 calls can't come from more than 50 numbers), Smith.ai's free tier plus 25 extra calls is $75, Retell usage is about $23, and a human service runs $112.50 to $225.

Notice what the example doesn't give you: a reason to build custom on price alone. At this volume Retell's usage is $59 a month below Rosie's plan, and building and testing a custom agent, which depends on your integrations and rules, has to be paid out of that gap. Against Smith.ai the gap is $295 a month. Mostly, custom pays off on what the agent can do, which is where the next sections come in.

Then hold the monthly fee against what one booked job is worth to you. If an average job leaves you $200 after costs and the agent books one call a week you would otherwise have lost, even the $385 plan is covered twice over. If it mostly takes messages that voicemail would have caught anyway, the cheapest plan is still too expensive.

Where AI Answering Breaks

In one small r/automation thread from March 2026 (about 41 comments, some possibly from vendors), people listed the worries you'd expect: slow responses, agents that fall apart off script, callers who want a person, sensitive data. Some of that depends on the product. In our experience building these agents, much of the rest comes from setup.

Latency

A pause before every reply feels like a bad line. Retell's own six-week test, with April 2026 data, measured about 600 ms average response time for Retell and about 1.1 seconds for Goodcall, whose pauses the test callers commented on. Retell wrote the test, ranked itself first, and doesn't describe its method, so treat this as one vendor's claim. What you can do: in any demo, listen for the gap before each reply.

Calls that don't fit the script

"I need to reschedule, the water heater is leaking again, and did your tech leave a part here last week?" Three requests in one breath, or one the agent has no tool for, is where trouble starts. In the same Retell test, Goodcall stalled when a caller tried to reschedule mid-call and sent them to voicemail. A longer script won't fix this. A rule for when to hand off will: if the agent can't do what the caller asks, it transfers the call or gives a specific callback time.

Interrogation instead of conversation

Some agents ask one question at a time, confirm each answer, and read the details back. That sounds like a form over the phone, and callers can hang up on it even when every answer was collected correctly.

Callers who want a person

In a Simply Business survey of 1,047 US small business owners, 86% said being able to speak with a human matters when they deal with AI-led services. That's owners speaking as customers, not your callers. We'd guess callers feel much the same, though the survey doesn't show it, so assume some of yours will ask for a person. An agent that won't transfer, or makes them fight for it, turns a missed call into an annoyed customer.

Recording, consent, and data

Recording rules differ by place. California, for example, requires the consent of everyone on a confidential call before it's recorded (Penal Code section 632), and your callers won't always be in the same state as you. In Canada, the Privacy Commissioner's guidance under PIPEDA says a business must tell callers the call is recorded, say why, and get their consent. The simple default for both countries: the agent says at the start that the call is recorded and why.

None of the sources we used make it a legal duty to tell inbound callers they're talking to AI. We recommend saying it anyway. It costs one sentence and removes the moment where a caller works it out halfway through.

Outbound calls are a separate matter: since a February 2024 FCC ruling, AI voices calling people need their prior consent, so check the current rules before the agent places callbacks or reminders. We're not lawyers. Run your setup past one.

What a Good Setup Looks Like

The receptionist we built for the appliance repair company runs on Retell and connects to the company's field service software through automations. During a call it qualifies the repair, creates the customer, takes the service address, checks availability, assigns a technician, and creates the scheduled job. The owner gets a booked job on the board instead of a note to call someone back.

A few design choices from that work separate a nice demo from something that runs every day:

• Let the caller tell their story first, pull several facts out of that answer, then ask two or three targeted follow-ups instead of marching through a list of fields.
• Don't ask again for what the caller already said. Confirm the address once and move on.
• Never fill a blank with a guess. If something is missing, ask for it.
• Write the hard rules down: service area, which jobs need a callback instead of a booking, what you don't work on. That's exactly where the model's judgment slips.
• Talk like a person: short sentences, a slightly brisk pace, no "Great, thank you for that" after every answer.

The other half of reliability happens after the call. Bookings have to survive reschedules and cancellations, which we cover in Build Appointment Reminders That Survive Schedule Changes. And every action the agent takes should be logged so you can see why it did what it did. That's the subject of The Minimum AI Agent Audit Trail for Production.

How to Roll It Out Without Annoying Customers

Several commenters in that Reddit thread gave the advice we'd give too: start with the calls you'd lose anyway, and widen the agent's job later. Here's the order we suggest.

1. Count what you're missing. Pull the last 30 days from your carrier or phone system and count missed and after-hours calls, and how many came from new numbers. That tells you which plan size fits and whether this is worth doing at all.
2. Start with overflow and after-hours. Ask your carrier to forward calls only when nobody answers within a few rings, or outside business hours. Regular customers still reach you, and you keep your number.
3. Decide what counts as an emergency, such as an active leak, no heat in freezing weather, or a gas smell, and what the agent does with one. Give it a fallback chain: transfer to the on-call phone, then a second number, and if nobody answers, text the details to the on-call tech and give the caller a firm callback time. The agent never says help is on the way unless someone has confirmed it. For a gas smell, it tells the caller to follow their gas utility's emergency instructions instead of waiting for you.
4. Keep the first version narrow: booking, basic questions, and messages. Leave quotes, complaints, and billing to people for now.
5. Make the handoff easy. Anyone who asks for a person gets transferred or gets a firm callback time. No loops.
6. Run about 20 test calls before going live, with real scenarios: an emergency, a transfer nobody picks up, someone with two problems, someone who mumbles their address. Listen to every recording.
7. Read transcripts every week for the first month and fix the rules wherever the agent guessed or stalled.

Then track four numbers: the share of calls answered, bookings the agent made, transfers to a person, and hang-ups in the first 15 seconds. The last one is the earliest warning that callers don't trust what they hear. These numbers are our starting points, not benchmarks.

Questions to Ask Before You Buy

• What happens past the plan limit? Rosie's pricing page doesn't say.
• Do our own test calls count? Smith.ai counts every answered call by default.
• Can it book into the calendar or job software we already use, or does it only take messages?
• What does a transfer to a person cost, and what happens when nobody picks up?
• How many calls can it take at once? Retell includes 20.
• Can we hear raw, unedited recordings, and change the business rules ourselves?
• Where are recordings stored, and can we delete them?
• What's the notice period? Smith.ai is month to month with 30 days' notice.
• Do we need to port our number? With forwarding you don't. Retell's comparison says Goodcall doesn't support porting, so confirm with Goodcall if you want the vendor to host the number.
• Is the trial long enough to include a busy week? Rosie's is 7 days; Smith.ai's free tier covers 25 calls a month.

If you're in Canada, the prices above are US list prices in USD. Also ask whether the vendor offers Canadian numbers, whether it bills in CAD or adds tax, whether recordings stay in Canada, and whether the agent can handle French if your callers use it.

Is an AI Answering Service Worth It?

If you lose calls while you're on jobs, it's worth testing, and the test is cheap if you keep it small: $23 to $79 a month in the overflow example above. A few weeks of recordings will show whether your callers accept it and whether the agent is booking work or just taking messages.

A custom agent makes sense when the ready-made options can't do the work: bookings have to land in your field service software, your rules are too specific for a settings page, or your volume makes per-call billing expensive. That's what we build at PASMO. If you want a straight answer on whether you need a custom receptionist or an off-the-shelf one, get in touch. We'll tell you when the cheaper product is the right call.