It's 10 PM and you have three pricing pages open in three tabs. One wants $1.10 a minute. One wants $1.50 a call. One wants $89 a month flat, with an asterisk you haven't clicked yet. You own a service business, not a spreadsheet, and all you wanted to know was: what does it cost to have someone - or something - answer my phone? An hour in, you still can't line the three numbers up, because they aren't measuring the same thing.
That's not an accident. Pricing models in this industry are shaped by what the provider's costs look like, not by what your outcome looks like. So before you compare quotes, it's worth understanding what each model is actually charging you for - and then converting all of them into the one number that matters: what you pay for a call that ends finished.
The three price tags you'll be quoted
Every quote you'll see is one of three models - per minute, per call, or flat monthly - and each one hides a different assumption about your phone traffic.
Per minute is the classic answering-service model, human or AI. Human services commonly advertise somewhere in the range of a dollar or two per operator minute; AI services advertise a fraction of that, often cents rather than dollars, because there's no operator payroll underneath. The assumption baked in: your calls are short. A chatty caller, a complex billing question, a caller who needs things repeated - all of it runs the meter.
Per call charges a fixed amount every time the line is answered, regardless of duration. The baked-in assumption is the mirror image: your calls are long enough that per-minute would hurt. Watch for what counts as a "call" - some providers bill wrong numbers, robocalls, and hang-ups at the same rate as a real customer.
Flat monthly bundles a pool of minutes or calls into one predictable price, usually with an overage rate above the bundle. The assumption: your volume is stable. The number to scrutinize isn't the headline price - it's the overage rate, because your busiest month is exactly when you'll exceed the bundle, and the busiest month is the one the service exists for.
None of these models is dishonest. But none of them, as quoted, tells you what you'll actually spend - and none tells you what you'll get for it.
Why the sticker price isn't the real cost
The advertised rate is the visible cost; the invisible costs live in what happens after the call is answered. Four of them show up on almost every bill, or worse, never show up on a bill at all.
- The relay tax. If the service takes a message instead of resolving the call, you've paid for the call and you still owe the labor: someone on your team reads the message, calls back, plays phone tag, and does the actual booking or answering. That callback time is a real cost that never appears on the answering-service invoice.
- Minimums and surcharges. Per-call minimums, holiday and after-hours surcharges, setup fees, and "patch-through" fees for transferring a caller to you. Standard in the human-service world; ask about all of them.
- Junk traffic. Spam calls, solicitors, and misdials get answered - and billed - like everything else under per-call pricing. Look at your call log and count how many of last month's calls you'd have happily sent to voicemail.
- The calls that never connect. If the service queues callers when its operator pool is busy, some hang up. You don't pay for those calls, which sounds like savings until you remember what a hung-up emergency call was worth.
The relay tax deserves the most attention, because it's the largest and the least visible. A message-taking service converts each call into a task for tomorrow morning. A platform that can book, quote, and answer during the call - the way modern AI voice agents do - eliminates that second cost entirely for the calls it resolves. Two services with identical per-minute rates can differ enormously in what they cost you once callback labor is counted.
The number that makes every quote comparable: cost per resolution
Divide everything you spend on answering by the number of calls that ended finished - no callback needed, no follow-up owed - and you can compare any two services on any billing model.
The formula is short enough to do on the back of the quote itself:
- Total monthly cost = platform or base fee + usage charges + overages + surcharges + (hours your team spent on callbacks × what an hour of their time costs you).
- Resolutions = calls that ended with the job done: appointment booked, question answered, payment taken, message that genuinely needed a human routed to one.
- Cost per resolution = the first number divided by the second.
Notice what this metric punishes. A cheap service that takes messages scores badly, because its resolution count is near zero - almost every call it touches still needs your labor to finish. A pricier service that completes the work scores well. And a service that answers instantly at 3 AM scores where it should, because the resolutions it captures after hours are ones the 9-to-5 alternative never gets to count.
Notice also what it ignores: minutes. Whether a resolution took ninety seconds or six minutes matters to the provider's cost structure, not to yours. You needed the appointment booked; it got booked.
Run your own numbers: a worked example
Don't take a vendor's ROI calculator at face value - including ours. The only numbers that matter come from your own call log. But here's the shape of the math, with deliberately round figures you should replace with your own.
Say a shop takes 300 calls a month, averaging 4 minutes. A human service at $1.25/minute bills $1,500. If it books nothing and relays everything, and each message costs your office 10 minutes of callback time at $25/hour of loaded staff cost, that's another 50 hours - $1,250 - of invisible labor. Total: $2,750. If roughly 250 of those calls end truly resolved after the callbacks, you're at about $11 per resolution.
Run the same traffic through an AI platform. Using published pricing as an example - a $100/month plan plus $0.50 per all-inclusive voice minute - 1,200 minutes runs about $700 total. If the agent resolves the routine 80% during the call and hands the genuinely human 20% to your team, callback labor shrinks to the transferred calls only. You're somewhere near $3 per resolution, and the after-hours calls that used to hit voicemail are now in the resolution count instead of the regret column.
Your numbers will differ - that's the point. Pull last month's call log, count the calls, estimate the minutes, and be brutally realistic about the callback time. Full-time staff deserve the same math, by the way: a receptionist's true cost is salary plus taxes and benefits - commonly 25% or more above the wage - divided by the calls they actually resolve, for the hours they're actually at the desk.
Start small enough that the math can't hurt you
You don't need to trust anyone's example - you can produce your own cost-per-resolution figure in a couple of weeks, with real calls, for almost nothing.
Put an AI agent on one line: the after-hours line, the overflow line, whatever rings out most often today. Let it run for two weeks. Then count three things - what you spent, how many calls it answered, and how many of those calls ended finished. Divide. That's your number, built from your traffic, and it will tell you more than any pricing page in any tab.
Verlingo's pricing is published, per-resolution-friendly, and has no quote call in front of it - plans start at $30/month with a 14-day free trial. Setup takes minutes, so the experiment costs you an afternoon at most. Run the numbers. If they don't beat what you're paying now, you've lost nothing - and you'll finally know what an answered call actually costs you.