What Is a Virtual PBX (Cloud PBX)?

Why "virtual"

Because there's no physical box that belongs to you. The PBX is software running on the provider's servers in data centers, and the provider is responsible for the hardware, backup, updates and the connection to the telephone network. You get the service — not the equipment.

In English it's called a Cloud PBX or a Hosted PBX (a PBX that is "hosted" at the provider). In Hebrew, the names "virtual PBX" and "cloud PBX" are used for the same thing.

For the caller there's no difference at all. They dial the organization's number, hear a menu, wait in a queue and speak with a representative — exactly as with a PBX that sits in the office. The whole difference is on your side: where the PBX is located, who maintains it, and where you can answer from.

How it works behind the scenes

The PBX runs in the cloud, and two things connect to it: on one side the telephone network, through which calls come in from your numbers and go out; and on the other side the employees' devices, which connect over the internet.

Every phone in the office, mobile app or computer software "registers" with the PBX using the SIP protocol, with an extension name and password. From the moment of registration, the PBX knows where the device is and can ring it. What's important to understand: the PBX doesn't care whether the device sits in an office in Bnei Brak or at home in Jerusalem — as far as it's concerned, it's the same extension.

All the decisions — where the call goes, what time it is, which menu, which queue — are made in the cloud. So even when the office is closed or disconnected, the route keeps working: the PBX can play a message, take a message in voicemail or forward the call to a mobile.

What you gain

• No investment in PBX equipment. No server to buy, no expansion cards, and no technician coming to fix a box.
• Flexibility. Add an extension when a new employee arrives, and remove it when they leave. Before an event you can add temporary extensions and remove them the next day.
• Work from anywhere. An extension on a mobile, on a computer at home or at another branch — all in the same system, with the same internal extensions and the same outgoing number.
• Resilience. When the office has no power or internet, the PBX itself keeps working and forwards the calls.
• Self-management. Changing a message, updating hours or moving an extension to another employee is done from a browser, without waiting for a technician.
• Several branches — one PBX. A branch in Bnei Brak and a branch in Elad can share a menu, a queue and internal extensions, without any special connection between them.

What you need for this

A stable internet connection. Stability matters more than speed: a call uses little bandwidth, but is very sensitive to latency and jitter. In an office with many calls, consider a backup internet connection.

Devices that speak SIP. A desk IP phone, an app or software on a computer, or a SIM extension that works on a regular mobile phone. An old (analog) phone can be connected through a SIP adapter.

An orderly network in the office. A suitable router, a switch — preferably with PoE, which powers the phones through the network cable — and proper cabling. In most small businesses the existing network is enough; in a large office it's worth planning.

Moving from an old PBX: how to do it without stopping the business

1. Mapping. Write down what exists today: numbers, extensions, who answers where, what the menu says, what the hours are and what happens outside hours.
2. Building in the cloud. Build the same route on the new PBX — and usually improve it too, since it's a chance to clean out extensions no one uses.
3. Equipment. New phones arrive preconfigured, or you connect the existing ones through adapters.
4. Testing. You dial a temporary number and confirm that every route works: menu, queue, voicemail box, hours.
5. Number porting. Only when everything is ready do you move the numbers. From that moment, calls reach the new PBX.

The common mistake is to port first and build afterward. The result is that in the first days, customers reach a half-configured PBX.

Real-life examples

An office with people working from home. Some of the staff work two days a week from home. The desk phone in the office and the app on the mobile phone are the same extension, so the call reaches the employee wherever he is, and the customer doesn't know the difference.

A nonprofit on a campaign night. For one evening you need twenty volunteers who answer from home, from their mobile phones, or from the call center. You add temporary extensions before the event, connect them to a queue, and the next day you remove them — without buying equipment that would sit in a closet all year.

A yeshiva with several buildings. The office, the dormitory and the beit midrash are in separate buildings, but they are all extensions on the same PBX. An internal call between them is a three-digit dial.

Limitations worth knowing

A cloud PBX depends on the Internet at the office: when it goes down, the phones in the office can't answer — even if the PBX itself keeps working and forwards calls to a mobile phone. So it's worth defining in advance where calls go in that case.

A weak Internet connection or a router that isn't suited for calls can cause choppy audio or a call that is heard on one side only. In most cases the solution is in the network settings, not in changing the provider.

Preparation checklist: what to gather before moving to the cloud

The steps of the move were described above. What makes moves fail in practice is not the steps, but small details that nobody gathered in advance. This is the preparation list worth completing before you set a date:

• The list of numbers and who owns them. Every number that reaches the business, including fax numbers and numbers you no longer advertise. Porting requires that the owner registered with the previous provider be the one who makes the request, so you need the latest invoice and the customer details as they are registered there. A business whose number is registered under a previous owner usually finds this out too late.
• The extension table. Name, role, which device (desk phone, app, SIM), and where physically. This is the chance to delete extensions of employees who have left.
• What the messages say today. The opening recording, the menu, the after-hours message. You can re-record them or use the existing ones — but you need a written text.
• Business hours and holidays. Including the eves of Yom Tov, Fridays, and exceptions such as Yom Kippur, when the office is closed but you may want a different message.
• Where messages go. An email address for each voicemail box, and who gets a notification about a missed call.
• What else is on the old lines. Fax, alarm, elevator, an old credit card terminal. These stop working if you disconnect the analog line without planning a solution for them (virtual fax, an adapter, or keeping one line).
• The network in the office. Is there a network cable for every workstation? Is there a switch with PoE? Is the router suitable? Who is the Internet provider, and what happens when it goes down?
• Who the administrator is. One person who knows the control panel, can add an extension and change a message, and receives the notifications.
• The right date. Not the night of a campaign, not the week before a holiday. A regular day in the middle of the week, with someone available to fix small things the next day.

A business that comes to the setup meeting with this list filled in finishes the build on the same day. A business that comes without it spends the day looking for invoices and guessing what the menu message was.

What the cost is made of (without numbers)

The amounts vary between providers and between businesses, but the structure of the cost is almost always similar, and it's worth knowing so you can compare quotes correctly. In a cloud PBX the cost is divided into three parts:

• One-time. The equipment at the workstations — phones, headsets, adapters — and infrastructure in the office if it's missing: a switch, cables, a communications cabinet. This is the only part that is truly a purchase, and it stays yours.
• Fixed monthly. The service itself: the extensions, the numbers, and the features you chose (recording, queues, conference rooms). Usually this is tiered by the number of extensions, so the cost grows and shrinks with the team.
• By usage. Minutes of outgoing calls, especially to mobile phones and abroad, SMS messages, outgoing faxes. Internal calls between extensions cost nothing, even between branches.

By contrast, with a physical PBX most of the money goes out at the start: the server, the line cards, licenses for every extension and feature, and the installation. After that come an annual maintenance contract, technician visits for every change, and electricity and air conditioning for the cabinet. And at the end of the equipment's life — another big purchase. So the fair comparison is not "how much per month" but how much over five years, including the changes you'll make along the way.

Three things affect the total more than it seems: the number of channels (how many simultaneous calls you really need — usually fewer than the number of extensions), the pattern of outgoing calls (a business that dials many mobile phones is different from one that only receives calls), and the equipment (a desk phone for every employee, or an app for those who spend most of the day in the field). These three are worth thinking about before you ask for a quote, not after.

Myths versus facts

Around the cloud PBX, several beliefs have built up that were once true, or never were. These are the most common:

• "Voice quality is worse in the cloud." Not true when the office network is sound. A call in the cloud goes through the same codecs as in an IP PBX at the office, and sometimes at higher quality than an analog line. Choppy audio almost always comes from the local network — Wi-Fi, a home router, a damaged cable — and not from the distance to the server.
• "My number will change." No. Your existing number is ported to the new PBX, and customers keep dialing it as usual.
• "I need a special Internet line." In most small businesses the existing connection is enough: a single call uses very little bandwidth. What does matter is stability, and in an office with many calls — a backup line.
• "If the Internet goes down, the business is deaf." The phones in the office indeed won't work, but the PBX keeps receiving the calls and forwards them to a mobile phone or a voicemail box according to what you defined in advance. With a physical PBX, a line that goes down is truly silent.
• "The cloud is only for big companies." The opposite. A business of two people benefits the most, because it gets a menu, voicemail to email, and answering from a mobile phone without buying a PBX.
• "Anyone can listen to my calls." Access to recordings and to the log is set by user permissions, and the devices connect with a password for each extension. The real risk is a weak password that someone guesses and then dials on your account (toll fraud), not eavesdropping.
• "I lose control." Quite the opposite: with a physical PBX every change goes through a technician; in the cloud you change a message or add an extension from the browser.
• "The fax won't work." An analog fax indeed doesn't like packet networks, but the solution is a virtual fax — sending from the browser and receiving by email — which is usually more convenient than the old machine.

What is true: a cloud PBX moves responsibility for the network in the office to you. A good router, cables instead of Wi-Fi, and a switch with PoE are not a recommendation — they are the condition for clean calls.