Answering service or phone system software: which do you need?

Usually both, because they are not the same purchase. Phone system software — a cloud PBX or VoIP platform — owns the line: it carries the call, rings the right extension, holds the queue, keeps the recording, and gives you a number your staff can answer from anywhere. An answering service owns the conversation: something picks up, finds out what the caller wants, and does the next thing about it. A phone system with nobody behind it still sends callers to voicemail at 6pm, and so does a very good one. BotsDontSleep sits behind whatever system you already run, answers on the first ring 24/7 in 90+ languages, and bills $0.60 CAD per answered minute by the second, with no setup fee and no contract. You forward a number. You do not replace your phone system.

What is the difference between phone system software and an answering service?

One moves calls. The other answers them.

Phone system software is the plumbing: extensions, hunt groups, an auto-attendant, voicemail boxes, call recording, softphones, number porting and an admin panel where you set the rules. It decides where a call goes.

An answering service is labour. Someone — a person at a desk, or an AI on your line — picks up, listens, asks the three questions that matter for your business, and books, screens, transfers or takes a message. It decides what happens to the caller.

The confusion is almost always the auto-attendant. A menu that says "press 1 for service, press 2 for parts" feels like answering, because a voice spoke. It routed. If the extension it routed to is empty, the caller has spent twenty seconds pressing buttons to reach the same voicemail box they would have reached by waiting. A menu in front of an unstaffed line is a slower voicemail, and callers treat it that way.

Which problem are you actually trying to solve?

Write down the symptom first. The symptom picks the product, and the two fail at different things.

Two rows send people to the wrong purchase. If calls ring at the wrong desk, that is a routing problem inside software you already pay for, and no answering service will fix it. If the second caller gets voicemail while you are on the first, a phone system can only queue them. It has nobody spare to hand them to.

What does an auto-attendant do with a call at 2am?

It routes it to an extension nobody is sitting at, then plays your after-hours greeting and records a voicemail.

That is correct behaviour, and it is the whole problem: the caller at 2am is rarely browsing. A tenant with water coming through a ceiling, a homeowner whose pipe has gone in February — these are people who will ring the next number on the list rather than leave a message. On a Winnipeg plumbing line, the 2am call is worth more than the 2pm one and is the one most likely to be lost, which is an awkward combination to leave to a greeting.

An answering service changes one thing about that call: somebody is there. The useful version captures the address, what is happening, whether the water is off, and a number to ring back, then decides by your rules whether this wakes the on-call person or waits until seven. The rules are yours. The system only has to follow them without getting tired at 4am.

Can you run both, and how do they connect?

Yes, and the connection is a forwarding rule you set in the phone system admin panel you already have. It takes about ten minutes, and nothing on your website, cards or Google listing changes.

Three patterns cover nearly everyone:

After-hours only. Your system forwards to the service outside business hours and on holidays. Your team keeps every call they are there for. This is the smallest version and the one to start with, because it is made entirely of calls you are currently losing.

Overflow. Forward on busy, or after four rings with no answer. Your front desk is still the first stop; the service catches the second and third simultaneous call instead of queueing it. A clinic running departmental options on its Ottawa medical line can forward just the option that keeps going unanswered and leave the rest exactly as configured.

Full-time. Everything answers first, screens, and transfers what qualifies. This suits businesses where the phone interrupts the work being sold — a service advisor at an Edmonton auto shop is under a hood, not at a desk.

What flows back is the part worth checking before you buy. The booking should land in your actual calendar, the message should arrive as a text or email with a transcript, and the caller record should reach whatever you use to follow up. How that wiring is done is covered in our piece on how an AI receptionist connects to your systems.

Why are the two bills shaped differently?

Because one charges for capacity and the other charges for work.

Phone system software bills per seat, per month, whether that seat takes four calls or four hundred, and a seat you forget to remove bills for a year. Annual commitments are common, so the price is usually a year-long decision.

An answering service bills for calls answered. At $0.60 CAD per answered minute, billed by the second, a 90-second after-hours message call is 90 cents. A business taking 300 answered minutes a month pays about $180 — 300 multiplied by $0.60 — with no setup fee, no monthly minimum, no per-seat charge and no contract. The rate and the billing rules belong together, because per-second billing is what keeps that figure honest: on a service that rounds every call up to the next minute, that 90-second call is billed as two.

We use two minutes as a planning figure for a booking call and about forty seconds for a screened robocall. Those are assumptions for sizing, not promises. A month of real calls will tell you more than any estimate.

The practical difference is what happens in a quiet month. Seats cost the same. Answered minutes do not.

What about the AI receptionist add-ons phone system vendors now sell?

They are real, they are priced separately from your seats, and you should ask them the same questions you would ask anyone.

Checked 17 October 2026: major cloud phone vendors list AI receptionist or AI answering capability on their own pricing pages as a paid add-on sitting beside the per-seat plan, not inside it. Figures and packaging move quickly in this category, so read the vendor's current pricing page rather than a comparison article, including this one.

Four questions sort them out. What does it do when it does not know the answer: transfer, take a message, or guess? Can it write to your real calendar, or only send you a notification to do it yourself? Which languages, and can it handle a caller switching mid-sentence? And how is it billed: per seat, per call, per minute, or per "resolution", a unit worth having defined in writing before it appears on an invoice.

If you already pay that vendor and your needs are a greeting, a message and an email, the add-on may well be the shortest path and we would not argue you out of it. The reason businesses end up looking elsewhere is usually the booking: a receptionist that cannot read your calendar is a message-taker with better marketing. Where that matters, adding a Calgary virtual receptionist layer in front of an existing system is the alternative.

When is a phone system alone enough?

Four cases, and they are common enough that we would rather say so here than after an invoice.

Your volume is genuinely small and you answer it yourself. Under roughly twenty calls a month, answered from your pocket, the phone in your pocket is already doing the job. Buy nothing.

Your problem is routing, not coverage. If the complaint is that calls reach the wrong person during business hours, that is a configuration afternoon inside the system you already own. An answering service layered on top will not fix a hunt group, and it will bill you while not fixing it.

You already have reception covering the hours anything comes in. Test that before assuming it. Pull the log and see what lands after close. But if the log is empty after 5pm, then it is empty, and coverage is not your constraint.

A meaningful share of your callers will not deal with an automated voice. Then capture rate is beside the point: the message is perfect and the caller is gone. Some practices know this about their callers, and they are usually right. Where a person on every call is the requirement, a staffed service is the better purchase — our Nexa comparison sets out what that difference buys, and how fast a staffed service actually picks up is the number to compare it on.

The fifth case is not ours to rule on: where your profession has rules about how calls are recorded, retained or disclosed, that is a question for your own compliance advisor, not for a phone system.

How do you decide in an afternoon?

Five steps, a call log and a sheet of paper.

1. Export last month's call log from your phone system's admin portal. Every cloud system has one. You want the calls that ended in voicemail or an abandoned ring, with their timestamps.
2. Sort those into two piles: wrong-desk and nobody-there. Wrong-desk is a call that reached the business and reached the wrong person. Nobody-there is a call that reached nothing at all.
3. If the wrong-desk pile is bigger, fix the routing first and buy nothing. Change the hunt group, shorten the menu, set the ring order. Measure again next month.
4. If the nobody-there pile is bigger, read its timestamps and forward only those hours. Most of them cluster in two bands: after close, and the middle of your busiest working hour. Those are different fixes and you can buy one without the other.
5. Test it on a live line before you forward anything. Call an AI receptionist as your own customer and listen to what it does at the edge of what it knows. Ours is Maryann, on +1 437-494-9110, at any hour.

The output is a one-page routing table: which calls, which hours, who gets woken up. That is also what any provider needs from you at setup, so the afternoon is not wasted whichever way you decide. What happens to calls when your team is busy covers the overflow band once you know how big it is.