One of the most common questions we are asked during a switch is also one of the most expensive to get wrong: does the hardware have to go? A business with forty desks may have twenty or thirty thousand dollars of handsets bolted to those desks, bought within the last few years, working perfectly well. The idea that changing phone provider means skipping the lot is one of the main reasons businesses stay somewhere they have stopped being happy. It is also, in most cases, untrue. Uniden Voice Over Cloud runs standard SIP, the same published protocol every serious handset manufacturer implements, so Yealink, Fanvil, Grandstream, Snom, Poly, Cisco and a long tail of intercoms, paging speakers and analogue adapters will register and work. This is the detailed version: which brands and models, what auto-provisions and what needs configuring by hand, the provisioning lock a departing provider can leave behind, the five things that never carry across, and how to audit your own fleet in an afternoon.

You have the ABN, the business name, the logo and probably the website. Then somebody asks for your number, and you give them your mobile, because it is right there and the business is only you. Six months later that mobile number is on a hundred invoices, two hundred business cards, the van, three directory listings and every quote you have sent, and it is also the number your kids ring on. Untangling that is the single most annoying job in a growing small business, and it is completely avoidable. This is the whole phone setup for a new Australian business: which number type to choose and why, how many lines you actually need, what you have to buy versus what you can skip entirely, the five call flows to set up on day one, and the seven mistakes that cost real money later. It takes about a week and most of it takes an afternoon.

If you build your business on reselling and supporting 3CX, the last twelve months have been a series of conversations you did not want to have. A fair use policy that caps extensions against simultaneous call licences, with enforcement from April. An edition shake-up that retired Enterprise Plus and renamed Enterprise to AI Edition. Renewal quotes that need explaining. And underneath all of it, the same structural fact that was always true and is now harder to live with: you carry first line support for a platform whose roadmap, pricing and licensing terms you do not control. This is what actually changed, what it does to the margin on a typical Australian deployment, and what a partner program looks like when the vendor owns the network, the platform and the support queue, and pays you every month rather than once a year.

"Please listen carefully as our menu options have changed." Nobody has ever been pleased to hear that sentence. The phone menu is one of the few pieces of business technology that customers actively resent, that staff apologise for, and that almost every organisation running one privately admits is not very good, and yet it is still the front door to a large share of Australian businesses. The reason it survives is not that it works. It is that it solved a genuine problem in 1975, and until a couple of years ago there was nothing better to put in its place. That has now changed, and the change is not "a nicer menu". It is the removal of the menu entirely, in favour of something that simply asks the caller what they need. This covers why menus fail structurally rather than cosmetically, what replaces them, how to migrate off one in a fortnight, and the narrow cases where you should keep yours.

"I want AI to answer my calls." It is now one of the most frequent opening lines in any conversation about business phones in Australia, and it is a completely reasonable thing to want: you are missing calls, you cannot afford a full-time receptionist, and you have watched AI answer questions convincingly enough to think it could handle the twenty people a day who ring to ask what time you close. The complication is that four genuinely different products go by that name, they cost different amounts, they solve different problems, and picking the wrong one is how businesses end up with something their customers dislike. This is the plain-English version: what each option actually does, which of your calls to hand over first, what your customers will hear, the one design rule that decides whether they accept it, what it costs, and the Australian rules that apply.

Changing business phone providers has a reputation it mostly does not deserve. The great majority of changeovers are uneventful, and the ones that go wrong fail on a predictable short list: a contract with an exit term nobody read, a number range that could not be split, an alarm dialler that stopped reporting silently, and a cutover scheduled on a Friday afternoon. None of those are hard problems. They are just problems nobody looks for, because the conversation before a changeover is almost entirely about handsets and monthly cost: the two things least likely to cause trouble. This is the playbook: how to read your exit terms, what genuinely moves and what does not, the full inventory of devices quietly dependent on a phone line, a six-week timeline, and an hour-by-hour plan for the day itself.

Most business phone systems are a black box with a nice front end. Calls go in, calls come out, and the data those calls generate (who rang, when, how long, what was said, what happened next) stays locked inside a portal you can look at but not use. If you want to do something the vendor did not think of, you raise a request and wait. We took the opposite view. Every operation you can perform in our portal is available through an open REST API, every event that happens on your account can be pushed to your systems the instant it occurs, and every record we hold about your calls and messages is yours to pull out whenever you want. This is what that surface actually covers across voice and SMS, seven things teams build with it in about a week, the Australian compliance layer that applies once you start sending programmatically, and why openness is a commercial commitment rather than a feature.

If you run your business phones on Optus Loop, you have probably had a letter, an email, or a phone call about a migration. The service you bought is being replaced by a different platform, built by a different company, with a different app, a different admin console and a different way of doing almost everything. Optus calls it Optus Loop with RingCentral. Underneath the branding it is a platform replacement, and a platform replacement is not an upgrade: nothing carries across by itself, and everything you configured has to exist somewhere on the other side. This is what actually changes, what to check before your cutover date, what other businesses have reported about the experience, and the three options you have. One of them is only free for a short window, and that window is open right now.