What each of them actually buys
A virtual switchboard buys routing. It receives the call and decides where it goes: which handset rings, in what order, with what menu, and what happens if nobody answers. Its ground is internal organisation: several lines, several people, rules.
Outsourced call answering buys hours. It exists because there are moments when nobody can pick up: evenings, nights, weekends, holidays, or simply while you are working. Its ground is cover, and the sorting of whatever arrives during those hours.
The confusion comes from both of them answering the phone. But a virtual switchboard installed on an absent team only moves the silence around, and call answering plugged into a present team that does not know who should take the call does not fix the disorder.
| Virtual switchboard | Outsourced call answering | |
|---|---|---|
| What it buys | Routing | Hours |
| Its ground | Internal organisation: several lines, several people, rules | Cover: evenings, nights, weekends, holidays, service hours |
| What it decides | Which handset rings, in what order, with what menu | What is handled, what is noted, what comes back to you |
| What it does not fix | Nobody being there at the end of the chain | The disorder of a present but badly coordinated team |
The test that settles it in one question
Take last month’s missed calls and look at the hour they landed. If they land mostly during your opening hours, your problem is routing: somebody was there, the call did not find them. What you need is a switchboard, virtual or otherwise.
If they land outside, before opening, at lunchtime, after closing or on a Saturday, your problem is cover, and no switchboard setting will fix it: there is nobody to route to. What you need is call answering.
Plenty of small businesses find both in their statement. In that case the order matters: cover first, because an unanswered call is lost with no recourse, whereas a badly routed call often ends up finding somebody.
The test runs to three moves and is done on your carrier’s statement, not on a brochure.
- 1 Pull last month’s missed calls, with the time of each.
- 2 Count the ones that land during your opening hours: somebody was there, the call did not find them. That is a routing problem.
- 3 Count the ones that land outside, before opening, at lunchtime, after closing, on a Saturday: there was nobody to route to. That is a cover problem.
What a virtual switchboard does not do
A virtual switchboard does not understand the request. It knows where to send it, not what it contains. At the end of its chain of rules, if nobody has picked up, there is still voicemail, and the call is lost exactly as it would have been without it.
Nor does it sort urgency. A keypad menu asks the caller to file themselves, which they do badly: in an emergency, everybody presses the « urgent » key, and the queue becomes a queue again.
Three things a virtual switchboard will never do, whatever its settings.
- Understand the request. It knows where to send it, not what it contains.
- Create availability. At the end of its chain of rules, if nobody has picked up, there is voicemail and the call is lost as it would have been anyway.
- Sort urgency. A keypad menu asks the caller to file themselves, and in an emergency everybody presses the same key.
What call answering does not do
Call answering does not reorganise your team. It takes the call and passes it to you; who handles it next, and in what priority, stays your business. In a set-up where three people pass the same case around, call answering will change nothing about that back and forth.
Nor does it replace a direct line. A customer who needs to reach their usual contact does not need their message taken: they need to be put through. That is a routing setting, not a cover one.
Two more things call answering will not fix, and that it is often asked to.
- Reorganise your team. It takes the call and passes it to you; who handles it next, and in what order, stays your business.
- Replace a direct line. A customer who wants their usual contact does not need their message taken, they need to be put through.
What each costs, and why they are not comparable
A virtual switchboard bills per seat per month: the price follows the number of people to reach, not the number of calls received. A team of three taking three hundred calls pays less than a team of ten taking fifty. That is coherent with what it sells, routing between handsets.
Call answering bills by time or by call: the price follows the traffic, not the headcount. Two offers therefore do not compare on their price lists but over twelve months of your own activity, and the right question to ask a provider is not their rate but their unit of account.
One practical consequence: if your missed calls land mostly outside hours, adding seats to a switchboard will only raise the bill without handling a single extra call.
| Virtual switchboard | Outsourced call answering | |
|---|---|---|
| What is counted | The number of seats to reach | Traffic: time, or calls |
| What pushes the bill up | Headcount | Activity |
| Consequence | A team of three taking a lot pays less than a team of ten taking little | Two months of identical traffic cost the same, whatever the headcount |
The right question to ask a provider is not their rate, it is their unit of account.
When the answer is neither one nor the other
Sometimes the statement shows few missed calls and a lot of calls badly routed internally, with the same case passing from hand to hand. That is neither a cover problem nor a routing problem: it is a question of ownership, and it is settled by deciding who handles what, not by buying another line.
Conversely, a very low volume concentrated in a few hours often justifies neither: forwarding to a mobile is enough, and costs what the forward costs. A provider who does not tell you that is selling you something you do not need.
Taking them together
The two stack without getting in each other’s way, and that is the most common configuration: the switchboard stays in charge during opening hours, and a conditional forward sends to call answering whatever found no answer, outside hours or after three rings into the void.
Cantya plugs in at that point. It can hold the answering role behind an existing switchboard, or replace both when there is no reason to keep the installation. What does not change: it is the forward that decides, and you change it without us.
1
The call arrives
On your usual number, unchanged.
2
Your handsets ring
The switchboard stays in charge during your opening hours.
3
Conditional forward
Outside hours, or after a number of rings you set.
4
Call answering takes it
The call is handled instead of being recorded.
Common questions
- Can you keep your switchboard and add call answering?
- Yes, and it is the simplest arrangement. Your handsets ring first; a conditional forward switches to call answering after a number of rings you set, or outside your hours.
- Is a virtual switchboard enough to stop missing calls?
- Only if somebody is available to pick up at the end of the chain. The switchboard optimises the call’s route; it does not create availability where there is none.
- Do you need two providers to have both?
- No. Some services cover both roles, and Cantya is one of them. The question to ask a provider is what it does at the end of the chain: route again, or handle the call.
