Every phone provider can show you a plan that is cheaper than the one you are on. That does not mean moving will save you money. The headline price leaves out the lease you still have to pay out, the three months' notice on the IT contract that looks after your PBX, the handset reception insists on keeping, and the month where you pay two providers while your numbers move. It also leaves out the other side of the ledger: the separate SMS tool, the meeting subscription and the seats for staff who left last year, none of which are on the phone bill at all. This guide reduces the decision to three numbers you can find with last month's bills and one phone call: what you spend now, what you would spend after, and what it costs to get out. Then it puts them through one payback sum, using an illustrative seven person physio clinic on a self hosted PBX, and shows how to tell whether to move now, move at renewal or stay and renegotiate.

If your phone system lives on a box in the comms cupboard, or on a virtual server your IT provider set up, today is a day to ring them. On 21 October the PHP project released emergency fixes for two flaws, now known as PHP2Shell, that let an attacker run their own code on a vulnerable server with a single web request and no password. Exploit attempts were recorded before the fixes were even public. PHP is the language behind the admin screens of a lot of self-hosted phone systems, FreePBX in particular, and those screens are often reachable from the internet so staff and installers can log in remotely. What sits behind them is your call recordings, voicemail, the record of who you call, and the credentials your system uses to make calls on your account. This guide gives you five questions to ask your IT person today and what good answers sound like, then the technical detail they will need.

When SUPA Networks opened its fibre network to retail providers, VOCPhone was the first to connect. That head start gave us the longest time of any retailer running real traffic across SUPA, tuning our setup and learning how the network behaves at 8pm when the whole street is streaming. We used it to build a better connection: a direct link into SUPA with no aggregator in the middle, IPoE instead of the older PPPoE, symmetric speeds up to 1 Gbps with typical evening speeds published for every plan, and capacity sized for peak hour rather than the brochure. Here's how each piece works and why it makes your fibre faster.

Around twenty brands sell SUPA Networks fibre, and many of them are the same: identical websites, the same plan cards, the same prices to the dollar, and the same fine print saying maximum potential speed is displayed, typical speed may vary. That's because a lot of internet brands aren't really networks at all. They're virtual ISPs, reselling a platform somebody else runs, which means they can't fix faults themselves, can't control how busy the network gets at 8pm, and often put you behind a shared IP address. VOCPhone owns and operates its own network and connects directly to SUPA. Here's what that changes for your speed, your support and your IP address, and five quick ways to tell whether your current provider is a VISP.

Every business phone system brochure says the same things: crystal clear calls, world class support, enterprise grade, trusted by thousands. The words cost nothing, which is why they are everywhere, and why they tell you almost nothing about the provider you are about to sign with for three years. A better test is to ignore the good days entirely. On a good day every business phone system rings, transfers and sends voicemail to email. What separates them is what happens when something goes wrong: who can actually see the fault, how long the fix takes, whether the price you were quoted is the price you pay, and whether a customer ringing after hours reaches anything useful. Judged that way, the things that make a provider lead are mostly underneath the app, in who owns the network, who answers the phone, and what is written down. This is VOCPhone's case on exactly those points, each one something you can verify before you speak to us, followed by the businesses we are honestly not the best fit for and a method you can use on any provider, including us.

You have a list of five to nine providers, and every website on it promises a business phone system with call routing, voicemail to email, a mobile app, call recording and some kind of AI. Every one has a comparison table where it wins. You could sit through nine demos of nine nearly identical dashboards, or spend one afternoon testing the things demos are designed not to show: who answers when you ring with a problem, who owns the network, what the bill really comes to, how hard it is to leave, and what happens to a ringing phone when your internet drops. All of it can be tested from your desk, without a salesperson. Here are the seven tests and a tally that turns a long list into two.

Ask what a business phone system is and you usually get a list: extensions, IVR, SIP, softphones, hunt groups. Accurate, and not much help, because nobody buys a phone system to own a list. You buy it for what happens when somebody rings: the customer at 7:10am while you are driving, the patient at 12:30 when the front desk is at lunch, the enquiry at 9pm from someone ringing whoever picks up first. Each is a moment where a call turns into work or quietly turns into nothing. So this guide starts with the calls, follows a day at three illustrative businesses, and only then names the feature that handles each moment.

Ring three AI receptionists and you will probably hear three pleasant voices. Underneath, they may be very different machines. One is a general chatbot wired to a phone number. One has been taught how phone calls work. One has also been taught your industry and loaded with your price list, your calendar and your rules about urgent jobs. The industry calls that last kind domain-specific AI, and it is where business AI is heading: Gartner predicts that by 2027 more than half of the generative AI models enterprises use will be specific to an industry or business function, up from about 1% in 2023. On the phone, domain-specific is best understood as a stack of five layers on top of a general model. This guide walks through each layer, the tell-tale symptom a caller notices when one is missing, how to test for it in ten minutes, and what it means for hosting, privacy and cost.

If you have looked at AI for your phones or website this year, you have probably noticed that everything is now an agent. The chatbot that used to sit in the corner of a website is an agent. The phone menu with a friendlier voice is an agent. Some products genuinely are: they can check a calendar, make a booking, send a confirmation and pass a call to a person with a proper summary. Others can answer questions and nothing more. Gartner has a name for the relabelling, agent washing, and estimates only about 130 of the thousands of vendors claiming agentic AI actually deliver it. This guide gives you a practical way to tell the difference: three categories to sort products into, a five call test you can run in fifteen minutes, three things to ask to see behind the demo, and a 24 point scorecard. Then we run VOCPhone through the same test.

Picture a cafe owner who switched off the surcharge on the terminals last night. This morning the first regular in the door asks, "So is the coffee dearer now?" That question is being asked all over Australia today. From 1 October 2026, businesses can no longer surcharge payments on eftpos, Mastercard or Visa, in store or online, and American Express has announced its own no-surcharge rules from the same date. For businesses that surcharged, the cost of accepting cards still has to be covered somewhere. This guide works through two illustrative examples, a cafe and a plumbing business that invoices, to show what the surcharge used to recover, what absorbing it costs over a year, how much a cheaper payment plan helps, and how small a price change usually needs to be. Then it covers the part most guides skip: making sure your phone greeting, on-hold message, AI phone agent and SMS all give customers the same clear answer.

Australia narrowly avoided a per capita recession in the June quarter, with real GDP growth of 0.4% doing little more than matching population growth, and on 29 September the Reserve Bank lifted the cash rate to 4.60%. Economists expect a slow finish to 2026. Every business owner is now deciding how to respond, and the instinct is to cut hard and wait. History suggests that is only half right. A Harvard Business Review study of 4,700 companies across three recessions found that 17% went bankrupt, were acquired or went private, and only about 9% came out stronger than before, and the difference was not how much they cut but what they cut. Australia's own downturns in 1991, 2008 and 2020 tell a similar story. This article looks at what the businesses that came out ahead did differently, why being easy to reach matters more when customers are ringing around, the mistakes to avoid, and a 30 day plan to put it into practice.

The Reserve Bank raised the cash rate to 4.60% on 29 September 2026, its fourth increase this year and a full percentage point since January. The Board was clear that it is not finished if inflation does not cooperate, saying it will act "including increasing the cash rate target further if needed". Most small business owners cannot do much about their loan rate beyond ringing the lender. What they can do is stop money leaking out through fixed costs that nobody checks, and the phone and internet bill is usually the worst offender. It is often split across three or four providers, it carries charges for staff who left and handsets bought years ago, and promotional prices end quietly. This guide sets out a 30 minute audit you can do this week, works through an illustrative eight person business that finds about $187 a month, lists the questions to put to your current provider, explains our half price nbn offer for new bundles, and flags the savings that end up costing more.

A physio clinic opens at nine. At 8.55 on a Monday the receptionist notices the phones are quiet, which is odd for a Monday, and then a patient walks in to say they have been getting a busy tone for twenty minutes. Somewhere between the clinic's internet, its phone provider and the platform that provider uses, something has gone wrong. What happens in the next hour depends almost entirely on one thing: who answers when the clinic calls for help. We walk through the same fault handled by three kinds of provider, a ticket only service, a reseller and a provider that runs its own network, to show why the experience differs so much. Then we set out what a tech partner who genuinely cares about your business does differently, how to interview a provider before you sign, the contract clauses to check, and where AI helps support rather than getting in the way.

When your ABN arrives, the internet hands you a checklist. Business name, GST, bank account, insurance, logo, website, socials, cards. The problem with a flat checklist is that it treats every item as equally important, and they are not. You can redesign a logo next month. You can rebuild a website in a weekend. But a few early decisions spread into places you do not control, and changing them later costs real money and lost customers. This guide sorts the usual post-ABN list by two simple questions: how hard is this to change later, and how much does it cost if I get it wrong? Move fast on the easy ones. Slow down on the few in the hard corner. Your business phone number sits right at the top of that corner, because within a year it lives in your customers' phones, your reviews, your listings and on the side of your van, and none of those copies can be updated.

A tenant rings a property management office at 10.40 on a Monday morning. The hot water system in their unit is leaking, there is water on the laundry floor, and they have a toddler. The property manager who answers is good at the job and she does what everyone does: she pulls up the tenancy, starts typing, asks the tenant to spell their surname, asks for the unit number again, types "HWS leaking", asks whether the water is hot or cold, types that, and somewhere in there misses the tenant saying the isolation valve is behind the washing machine and they cannot reach it. After the call she spends two minutes writing the note properly and booking a plumber, and during those two minutes two more calls go to the queue. Nothing about that call went badly. It is simply how phone work has always been done, and it costs more than it looks. In 2026 the phone system can write that note while the call is happening, with the valve detail in it, ready to check the moment the tenant hangs up. This article walks through what changes when it does: for the person on the call, for the customer waiting in the queue, and for the record. It also covers the habits that make AI notes trustworthy, the errors to check for, and the kind of AI note taking you should not allow anywhere near your customers.

Ask most business owners how old their phone system is and you get a shrug and a guess. Ask them what it costs each year and the guess gets vaguer. That is not carelessness. Phone systems are designed to be forgotten, and a good one is. The trouble starts when a system has been forgotten for so long that nobody notices it has stopped fitting the business. The receptionist keeps a notepad for messages because the voicemail is awkward. Two of the sales team give customers their mobile numbers because the desk phone cannot follow them. The after hours message still mentions a staff member who left in 2019. The maintenance invoice renews every year and nobody reads it. None of these is a fault, so none of them triggers a repair, and the system rolls on. This guide gives you a way to look at your own setup with fresh eyes in about twenty minutes. It is built around four simple tests: is the system still supported, is it secure, does it connect to how your people actually work now, and can it do what your callers expect. You walk the office, read the bill, ring yourself after hours, and write down what you find. By the end you will know whether to leave it alone, start planning, or move soon, and if it is time to move, you will know what to keep, what to retire and how to switch without losing a single call.

Picture the message as it landed. A work notification on a personal phone, apparently from the IT department: your password has expired, sign in here to reset it. Or, for some recipients, a note that their shift schedule had changed, with a link to check it. The link went to an address with the company name and the words "sso" or "okta" in it, and the page it opened looked exactly like the sign-in screen staff used every day. That is how the Twilio hack began in the first days of August 2022. A few employees typed in their username, password and one-time code, the attackers used those details on the real system within seconds, and from there they reached the internal tools Twilio staff use to support customers. Twilio detected the intrusion on 4 August, and the last unauthorised activity was on 9 August. By the time the investigation closed, 209 customer accounts had been accessed, 93 users of the Authy authenticator app had strange devices attached to their accounts, and Signal, the encrypted messaging app, had told around 1,900 of its users that their phone numbers or registration codes may have been exposed. There was no zero day exploit and no malware on a server. There was a text message, a copied page and a code that proved much less than everyone assumed. This article walks through the chain link by link, because each link has a direct equivalent in an Australian small business, and most of them can be fixed in a month.

Picture the call. Your phone buzzes with a sign-in approval you did not ask for, and a minute later somebody rings saying they are from support, that there is a problem with your account, and that they are sending a prompt to fix it. You are busy, the voice is calm and polite, and the prompts keep coming. That is more or less how Cisco was breached in May 2022, and the only unusual thing about it is that Cisco then published a detailed account of exactly how it happened. Two years later a different kind of problem hit Cisco's Webex platform: German journalists showed that meeting links for the Bundestag, ministries and the armed forces could be found by counting up and down, exposing the titles, times and attendee lists of thousands of meetings. The first incident came in through a person. The second came in through a product. Almost every communications security failure a business will face falls into one of those two buckets, and the fixes for both are cheaper than most people expect. This is a practical walk through both incidents, a thirty minute audit you can run yourself, and the questions worth asking whoever provides your phones and meetings.

Imagine the call. It is a Thursday afternoon and your office manager answers. The caller introduces themselves by name, says they are from your phone provider's security team, and mentions the incident that was in the news in July. They have your office manager's name, the business address and the main number, all correct. They explain that affected accounts need their admin access re-verified, and that a code will arrive by text in a moment. Could she read it back so they can confirm she is the account holder? Nothing about that call sounds wrong, which is the whole point, and it is the kind of call that becomes much easier to make after a breach like the one RingCentral disclosed on 28 July 2026. The data taken was contact information: names, emails, phone numbers and addresses for about 1.6 million records, verified independently in August. No passwords, no payment cards and no call recordings have been reported, and the platform itself was not affected. That makes it easy to dismiss. It should not be dismissed, because accurate contact details plus the name of the company to impersonate is exactly the combination a phone scammer needs, and the group responsible has spent two years showing that a well researched phone call gets further than almost any piece of malware.

Follow one customer through an ordinary week. On Tuesday they fill in the form on your website, which creates a lead in the CRM and sends somebody an email. On Wednesday they ring, because filling in a form and hearing nothing makes people ring, and whoever answers has no idea a form exists, takes the details again and writes them on a pad. On Thursday they text the mobile number from the van, which is a different number entirely and appears in no system at all. On Friday they message the business WhatsApp because the website has a button for it, and that message sits in an app on one person's phone. The following Tuesday they ring again and ask why nobody has got back to them, and the honest answer is that four different parts of your business each did roughly a quarter of the job and none of them knew about the others. Nobody was lazy. Every system worked exactly as designed. What failed is that there was no layer holding the thread, and adding AI to any one of those four systems would not have helped, because each of them would still have been reasoning about a quarter of the situation while sounding confident about all of it. That is the shape of the problem in most Australian businesses in 2026: plenty of intelligence, distributed across silos, with nothing in the middle. The fix does not involve replacing your CRM or your job management software, and it does not require a data project. It requires deciding which layer sits in the middle, and the answer is less obvious and more useful than most businesses expect.

The question gets asked backwards almost every time. People ask whether they should be using AI, which is a question about technology and therefore unanswerable without a sales pitch attached. The version that can actually be answered is narrower and duller: is there something in this business that happens often enough, similarly enough and expensively enough that a machine doing it would leave us better off after paying for the machine, the plumbing and the supervision. That has a number on the end of it, and the number is frequently small, which is a perfectly good outcome that nobody ever writes an article about. It is also sometimes very large, and the businesses where it is large tend to have one thing in common: they are leaking something they cannot see, usually calls that ring out, follow-ups that never happen, or notes that were never written. The leak does not appear in any report, because things that did not happen rarely do. So this is a worksheet rather than an argument. What the Australian evidence actually says once you understand why the adoption figures disagree so wildly, the four costs of which you will be quoted one, a payback calculation worked through three different shapes of business, the four situations where the answer should be no regardless of the arithmetic, and a thirty day sequence that costs almost nothing and ends with a number instead of an impression.

A business we spoke to earlier this year had an AI answering service running for five weeks and then turned it off. When we asked what went wrong the answer was interesting, because nothing did, exactly. It understood people fine. It booked appointments correctly. The problem was that nobody could say whether it was better than what came before, because what came before was a voicemail box that nobody had ever measured either. So when one customer complained about a call in week four, there was no counterweight. There were no transcripts anybody had read, no agreed number, no before and after, just one loud data point and a general unease, and the decision made itself. That story is far more common than the dramatic failures, and it is the reason a deployment plan is worth more than a better model. Gartner's estimate that more than forty per cent of agentic AI projects will be cancelled by the end of 2027 names escalating cost, unclear business value and inadequate risk controls, and the middle one is the quiet killer: not that the thing failed, but that nobody could demonstrate it had succeeded. The fix is boring and it works. Pick one narrow job. Write down what it may never do. Decide where a call goes when it stops. Write one sentence with a number in it that says what good looks like by day sixty. Then run it for a fortnight where no customer ever hears it, and read what it would have said. Everything after that is comparatively easy.

A customer rings on the twenty-ninth of December. They are not sure you are open, because it is that strange week where some businesses are trading normally, some are closed until the middle of January, and the shops are open but nothing else seems to be. Your phone rings out. There is no message, because whoever set the hours never thought about the twenty-ninth, which is not a public holiday and therefore behaves like an ordinary Tuesday as far as the system is concerned. So the caller hears eleven rings and nothing else, decides you are shut, and rings the next name on the list, who has a recorded message saying they are closed until the fourth but their on-call person can be reached by pressing one. The second business gets the job. Neither business will ever know that happened, because a call that rings out is not recorded as anything anywhere, and the only trace is a small unexplained difference in January revenue. That is the actual Christmas phone problem, and it has almost nothing to do with Christmas Day. It is about the four or five ambiguous days either side, the fact that public holidays and business closures are two different things that phone systems treat differently, and the reality that in most small businesses the person who understands the phone configuration finishes work on the nineteenth. All of it is preventable, none of it is difficult, and the work is much easier in October than in the week before.

There is a specific kind of blindness that affects every business about its own phone system. You cannot hear it. You know the options, you know which one you want, you know that operations handles bookings and that the second option is really for existing customers, and you have never in your life listened past the third option because you have never needed to. So when somebody suggests the menu might be a problem, it does not feel like one, and the conversation ends there. Meanwhile a caller who has never heard any of it is listening to forty seconds of talking, picking the option that sounds closest, waiting, reaching the wrong person, explaining the whole thing again, and quietly deciding something about your business that they will not tell you. The only way through that blindness is to stop looking at the configuration screen, which shows you what you intended, and start ringing your own number from a phone that is not part of your system, at times you would not normally ring, doing the things real callers do. Seven calls covers it. Most people find at least three things they did not know about, and roughly half find a path that rings forever and ends nowhere, which is the single most expensive fault in phone design and the one that never appears in a report. This is the audit, in order, with what each call is designed to expose, followed by the eleven fixes ranked by what they are costing you rather than by how easy they are.