Guides and Articles

Nobody sets out to build a bad phone menu. They get built one reasonable decision at a time. Somebody adds an option because accounts kept getting sales calls. Somebody adds a second layer because the first one grew to six options. Somebody records a message about the website because it seemed helpful. Somebody adds a note about a public holiday in 2023 and never takes it out. Two years later a caller with a simple question listens to forty seconds of talking, chooses the option that sounds closest, waits, gets the wrong person, is transferred, explains the whole thing again, and forms a permanent opinion about your business that has nothing to do with what you actually do. The uncomfortable part is that everyone inside the business thinks the menu is fine, because everyone inside the business already knows which option they want and has never once listened past the second one. There is a better way to design this and it is not just a shorter menu. It starts from what people actually ring about, in the proportions they actually ring about them, opens by telling the caller what is going to happen rather than presenting a list, uses a menu only where a menu genuinely earns its place, and defines what happens at every dead end rather than letting the phone ring into nothing. This is that design: the wording for the greeting, the rules for menus and when to skip them entirely, queue and hold settings that people tolerate, overflow, after hours, and seven test calls that will show you exactly what is broken in about fifteen minutes.

Ask a business that dislikes its phone system what is wrong with it and you will rarely hear about the platform. You will hear that calls go to the wrong person, that nobody knows how to transfer, that the after-hours message still has last year's opening hours, that half the team never installed the app, that the second office was never really finished, and that the reports do not match what anyone believes is happening. None of that is a product fault. All of it is a setup fault — and specifically, a sequencing fault. Somebody ordered before deciding, ported before designing, went live before testing, and then trained people afterwards, if at all. The uncomfortable part is that a badly cut-over system stays badly cut over for years, because once a business is limping along on a phone system nobody wants to touch it again. So the setup is not a formality that happens between signing and using; it is the part that determines what you actually own for the next five years. This is the whole runbook, in order, for a business that already has numbers and staff and habits: the six decisions that must be settled before anything is ordered, the porting plan that is almost always the critical path, the call flow drawn on paper before anybody opens a console, the network check nearly everyone skips, the test script, cutover day itself with a defined point of no return, the first week, and the thirty-day review that turns an installation into a working system.

There is a particular kind of silence that has now been officially explained. If you dial Triple Zero from a mobile and your own carrier's network is unavailable, your handset will try to place the call through another carrier's network instead. That process is called emergency camp-on, it is the reason emergency calls can be made with no credit, no active service and no SIM card at all, and it takes time. According to advice published today by the federal government and the mobile carriers, it can take up to sixty seconds — and during a Telstra outage earlier this year the maximum stretched to ninety. For the whole of that time there is generally nothing on the line. No ringing, no message, no reassurance. The advice being circulated is specific and slightly counter-intuitive: if the first attempt does not connect within about five seconds, hang up and immediately try again; on that second attempt, stay on the line for up to a minute. This article explains what camp-on actually is, what the screen indicators mean, where the advice came from and what it does not cover — and then does the part the news coverage does not, which is work out what an Australian business should actually change on the strength of it.

Every year the same thing happens and every year it is a surprise. Somebody remembers on about the twenty-third that the phones need doing, so a message gets recorded quickly, in a hurry, by whoever is still in the office, and it says the business is closed and will reopen in the new year. It does not say which day. It does not say what to do if something is genuinely urgent. It sits on a mailbox nobody will check for two weeks, and by the fifth of January there are thirty-one messages in it, eleven of which are from people who have already gone elsewhere and four of which needed answering on the twenty-eighth. Meanwhile two staff members have spent their break taking calls diverted to their personal mobiles because it seemed easier at the time, and one customer has rung four times, each time hearing an unbounded ring, and has quietly stopped being a customer. None of that is a Christmas problem. It is a scheduling problem that Christmas exposes, and the whole thing is preventable with about ninety minutes of work done in October rather than ninety seconds of work done on Christmas Eve. The 2026 to 2027 run has a particular shape worth planning around: Christmas Day is a Friday, Boxing Day is a Saturday, most states will observe a substitute public holiday on the following Monday, and New Year's Day is a Friday, which produces two consecutive short weeks where the honest answer to "are they open?" is that nobody is sure. Here is how to make sure your customers are not among the people wondering.

Almost nobody designs a multi-site phone estate. It grows. The second location opens and somebody local arranges a phone line because that is the urgent thing that week. The fourth location inherits whatever the previous tenant had. The seventh is acquired and comes with its own system, its own numbers and its own contract with eighteen months to run. By the eleventh, the organisation is paying eleven separate bills, running three or four different platforms, holding numbers registered to at least two entities and possibly to a former franchisee, and cannot answer the two questions that matter most: how many calls did the network miss last month, and which sites are missing them. Meanwhile the operational absurdities pile up. A queue in Perth overflows at 4pm while two staff in Adelaide sit idle, and there is no path between them. A customer rings the Newcastle branch, gets no answer, and never learns that the Maitland branch would have taken the booking. Head office publishes a standard for how calls are answered and has no way to know whether it happens. None of this is a technology problem — one platform across many sites has been ordinary for a decade. It is a design problem and, in a franchise network, a governance problem: which decisions belong to the centre and which belong to the site. This article covers both.

Every conversation about AI and security in the last two years has been about AI as the threat, and that framing is not wrong. The Australian Signals Directorate has assessed that AI almost certainly enables malicious actors to execute attacks at greater scale and speed, and the numbers behind that assessment are not subtle: more than 84,700 cybercrime reports in a year, roughly one every six minutes, with the average cost per incident rising fifty per cent to $80,850. Convincing phishing used to require somebody who could write. Convincing voice impersonation used to require an impressionist. Neither is true now. What gets far less attention is that the same technology is unusually good at the defensive side of exactly this problem, and that some of the most valuable places to deploy it are on the layer businesses think about least — the phone. Voice is where the social engineering actually lands. It is where the authorisation gets given, where the invoice detail gets changed, where the urgent request from the boss arrives, and it is almost always the least monitored channel in the business. This article sets out eight specific gaps that AI closes on that layer, states plainly the four it does nothing for, and covers the governance you need before you switch any of it on — including the obligation that lands on 10 December 2026 and applies to more businesses than expect it.

Two quotes land in the same week. One is for a cloud phone system, and it is about what you expected. The other is for contact centre software, and it is three or four times the price per person, from a salesperson who was very clear that you need it. Both documents describe calls arriving and being answered. Both mention AI, reporting, and integration with your CRM. Neither explains the actual difference, because the actual difference is not a feature, it is a shape. Unified communications exists to connect one named person to another named person: you ring Sarah, Sarah answers, and if Sarah is out you leave her a message. Contact centre software exists to take a stream of interactions and distribute them across a pool of people who, for the purposes of that call, are interchangeable: you ring the business, somebody qualified answers, and nobody involved cares which somebody it was. Those are different problems, and a product built for one does the other badly. The good news is that working out which you have takes one question rather than a consultant, and the answer is usually obvious once the question is put properly. The complication in 2026 is that the two categories are converging, mostly because AI has arrived in both, which means the line is moving and some of what used to require an expensive licence no longer does. This is where the line sits, how to tell which side you are on, what changes when you cross it, and how to avoid paying contact centre prices for a business that simply has a busy Monday.

The email is always reassuring and usually accurate. Your service is moving to a new platform as part of an exciting transition, your plan and pricing are unchanged, and no action is required from you. Sometimes that is completely true and the right response is to file it. Sometimes it is the first notice of a migration that will change your call quality, your support path, your admin interface and, at renewal, your price — and the moment to do something about it is now rather than in eleven months. The difficulty is that four genuinely different events produce almost identical emails. A corporate acquisition, where somebody bought your provider and the service itself does not change. A platform migration, where the technology under your service is being replaced. A product retirement, where what you are on is being switched off on published dates. And a licensing or commercial change, where nothing technical happens but the terms do. Australia has had a great deal of all four in 2026: an energy retailer's telco base absorbed by a listed broadband provider with migrations running through the middle of the year, enterprise fibre and wholesale assets changing hands between major carriers, takeover activity among the mid-tier, a small-business voice platform being rebuilt on a partner's technology, and a list of legacy products with published end dates. This article separates the four, sets out what survives a change of ownership and what does not, and gives you a ninety-day checklist worth running whichever one you have received.

Ask a business owner who supplies their phone system and they will answer instantly. Ask who supplies the cameras on the yard, the doorbell at the trade counter, the dash cams in the vehicles and the UHF radios in the cabs, and the answer usually takes a while, involves at least three companies, and ends with somebody checking an old invoice. That fragmentation is not free. It shows up as four apps nobody has taught the new staff member, four warranty processes, four support numbers with four different hold times, and a monthly subscription line for each device that quietly outgrows what the device cost to buy. This article does two things. First, it lists every product in the Uniden Australia range that talks to a network or an app as at August 2026 — the wire-free cameras and their solar, pan-tilt and 4G variants, the video doorbell, the indoor cameras, the dash cam families, the smart UHF radios and the EVOC2 desk phone. Second, it states plainly what a business gains by running that estate on one brand alongside Uniden Voice, including the subscription-free arithmetic that most buyers never do, and the two places where a single brand buys you nothing at all.

Somewhere around the start of 2026 the industry stopped saying chatbot and started saying agent, and the phone vendors were not far behind. Ask three providers what their AI agent does and you will get three answers that sound identical and mean completely different things. One means a recorded menu with speech recognition bolted on. One means a system that reads your website and answers questions about your opening hours. One means something that takes a booking, moves it, cancels it, and writes the result into the software your staff actually use. All three are called an agent, and only the third one takes work off anybody. The distinction matters more than the marketing does, because the first two get judged by your customers as a phone menu with delusions of grandeur, and the third gets judged as service. There is a single question that separates them, it takes one test call to answer, and almost nobody asks it: at the end of the call, did anything change in a system of record, or did the caller simply have a pleasant conversation with a computer and then have to ring back during business hours? This is what an AI agent is, what agentic actually means when it is not doing marketing work, which calls suit one and which will embarrass you, how the handover to a human has to be built, what the Australian rules require, and how to roll one out over six weeks without discovering the problems in front of your best customer.

Two things happen in a real estate office on the same Tuesday. At 11:20am a buyer rings about a property they saw on a portal twenty minutes ago; nobody picks up, the call rolls to a mailbox, and by the time it is returned at 2:45pm they have booked an inspection with another agency and stopped answering unknown numbers. At 6:40pm a tenant rings about water coming through a ceiling; the office closed at 5:30pm, the recorded message gives a mobile number for emergencies, that mobile is on silent because its owner is at their child's concert, and the tenant — reasonably — arranges a plumber themselves. Those two failures look like the same problem, which is why agencies keep trying to solve them with the same fix. They are not. The first is a speed problem in a competitive market where the enquiry is worth thousands and the window is minutes. The second is a compliance and liability problem, because tenancy legislation across the states requires a landlord or agent to arrange urgent repairs quickly — commonly within twenty-four hours of being notified, with tighter timeframes for essential services in some jurisdictions — and generally allows a tenant who cannot reach the agent to arrange the repair and recover the cost. One is about winning work. The other is about what a tribunal will make of your evidence. This article treats them separately, because designing an agency phone system as one undifferentiated flow is the reason both keep happening.

Every business with a 1300 number has, at some point, been told it is theirs. It appears on the van, on the invoices, on the shopfront, in the Google listing and on ten years of printed material. And then one day the business decides to change provider, and discovers that the arrangement is more complicated than anyone mentioned at the start. All Australian phone numbers are a national resource managed by the ACMA on behalf of the Commonwealth, so nobody owns one outright — not you, and not your provider. What exists instead is a right of use, held by somebody, recorded somewhere. Which raises the only question that matters: is that somebody you? The good news is that the answer is knowable, the porting rules are considerably stronger than most business owners realise, and the whole check takes about twenty minutes. The less good news is that a number of Australian businesses have never asked, and a small number of them are going to be unhappy with the answer.

Most small Australian businesses do not want a phone system. They want three things: a business number that is not their personal mobile, some assurance that calls get answered when they are on a roof or with a client or asleep, and a record afterwards of who rang and what they wanted. Everything else on a traditional phone system quote — the handsets, the cabling, the comms cupboard, the licences for features nobody will configure — is overhead attached to those three things. A virtual phone system is what you get when you remove the overhead and keep the three things. The number lives in the network rather than on a wire, the "system" is an app on the phones people already carry, and there is nothing to install anywhere. Add AI and the third piece changes character entirely: instead of a voicemail nobody listens to, something answers every call, has a short useful conversation, captures the details in a structured way, answers the questions you get asked twenty times a week, books the appointment, and leaves you a summary you can read in ten seconds between jobs. That combination — a virtual number, an app, and an AI that answers — is now the single most cost-effective communications setup available to an Australian business of one to twenty people. It is also frequently misunderstood, occasionally oversold, and genuinely wrong for a few kinds of business. This is what it is, what to look for, what it costs, and where it stops.

A business rings a customer back about a quote. The customer never sees the call, because their carrier dropped it at the network edge for presenting a caller ID the business does not hold rights of use to. Another business rings the same customer an hour later and does reach the handset — where it displays under a red warning banner suggesting the call may be a scam, and goes unanswered. Neither business did anything wrong on purpose, neither was told what happened, and both concluded that outbound calling "does not work any more". It does work. What has changed is that two independent systems now sit between your dialler and the person you are calling: a network-level blocking regime under Australia's registered scam-reduction code, which is a rules-based system you can comply with precisely, and a reputation-labelling layer applied by carrier screening, handset software and third-party call-identification apps, which is a statistical system nobody publishes the internals of. They have different causes, different symptoms and different remedies, and treating them as one problem is why so many attempted fixes achieve nothing. This article separates them, sets out the six configuration and behaviour patterns that actually cause failed calls, gives you a diagnostic you can run in an afternoon with your own numbers and two handsets, and orders the remedies by how much difference each one makes.

Telecommunications reporting in Australia has a habit of stopping at the interesting bit. A carrier posts a result and the coverage is about the share price. A regulator sets a spectrum price and the coverage is about the lobbying. NBN Co changes an eligibility rule and the coverage is about consumer broadband. What almost nobody does is follow the numbers all the way down to the thing a business actually holds in its hand, which is an invoice. So that is what this does. Telstra's full-year results landed on 13 August 2026. The ACMA has settled the renewal price for mobile spectrum licences expiring between 2028 and 2032 at $7.32 billion, over industry objection. NBN Co has removed a requirement that kept several hundred thousand premises off full fibre. Each of those has a path to your phone bill, some of them shorter than you would expect and one of them much longer. Here is the chain, the timing, and the part where a business actually has some leverage.

The most common business phone arrangement in Australia is a mobile in a pocket, and the second most common is a business number diverted to that same mobile. Both work, in the narrow sense that calls arrive. Both also produce the same four problems, and the problems are so familiar that most people have stopped noticing they are problems at all. Your personal number goes out on every call you make, so customers store it and ring it directly — at 6am on a Sunday, forever, and there is no way to take it back. You cannot tell a work call from a personal one before you answer, so you either answer everything in work voice or answer a customer the way you would answer your brother. Nobody else can help: if your phone is flat or in the ute or already on a call, that enquiry is simply gone, and you will never know it existed. And there is no record of anything — no missed call log, no note of what was agreed, nothing to look at when you wonder why the phone feels quieter this month. All four are fixable in about twenty minutes, and the fix is not a new phone. It is putting a proper business number on the phone you already carry, in a way that keeps the business identity separate from the personal one and gives the call somewhere to go when you cannot take it. This is the whole setup: the four available methods and which to choose, the settings that actually matter, what to do about after-hours, what happens when a staff member leaves, and the six things that break when this is done casually.

PBX stands for private branch exchange, and the original problem it solved is easy to picture: a business with twenty staff could not afford twenty telephone lines, so it bought a cabinet that let twenty internal telephones share four external ones, and let those twenty people ring each other without using a line at all. Everything else — extension numbers, transfers, hold, hunt groups, a receptionist's console — grew out of that one idea. A century later the cabinet has usually disappeared into a data centre, but the vocabulary has not, which is why a 2026 quote still talks about extensions, trunks and concurrent calls. The difficulty is that the word now covers at least five genuinely different architectures. A traditional PBX and a multi-tenant cloud platform have almost nothing in common except the function they perform, and yet both are sold as "a PBX", and the middle categories — IP PBX, hosted PBX, virtual PBX, cloud PBX — are used interchangeably by vendors who mean different things by each. That matters commercially, because the five models differ in who owns the equipment, who is responsible when it breaks, what happens to your calls when your internet drops, how you are charged, and what you can take with you when you leave. This article defines each one plainly, sets out what you are actually buying, and gives you the questions that reveal which architecture is hiding behind a quote.

Australian telecommunications does not usually produce a busy fortnight. This one did. Between 29 July and 13 August 2026, the Telecommunications Industry Ombudsman published a systemic report drawing on nearly 28,000 complaints and told the government the regulatory framework needs overhauling; the ACCC launched a twelve-month inquiry into whether wholesale mobile access, including domestic roaming, should be regulated; the ACMA commenced Federal Court proceedings against Optus Mobile over the September 2025 emergency call outage; and the same regulator published a report ranking 33 telcos on how well they handle complaints. Add the transparency rules that came into force on 30 June and the messaging rules that started on 1 July, and you have six separate developments pointing in one direction. None of them were written with a forty-person business in mind. All of them change what you can verify about a provider before you commit to one, which is the practical point of this article.

Every supplier will answer "how much does a business phone system cost?" with a per-user-per-month figure, and every one of those figures is true and almost none of them are useful. They are true because that is genuinely the headline rate. They are not useful because the headline rate is only one of nine things on your invoice, and because two quotes with identical per-user rates routinely produce monthly bills thirty or forty per cent apart. The reasons are dull and completely knowable: one quote assumed every person needs a full seat when a third of your team only ever uses a mobile app; one included AI in the seat price while the other charges it per minute, which is fine until an outage or a campaign doubles your inbound calls; one bundled recording storage at thirty days and the other at twenty-four months; one absorbed porting and integration and the other quoted them as professional services after you signed. None of that is deception. It is the ordinary consequence of a market where the headline number is the thing being compared, so the headline number is the thing that gets optimised. This article does not give you a price list — we publish one of those separately and it is linked below. It gives you a worksheet: nine lines, filled in with your own facts, producing a monthly figure and a five-year total you can put in front of any supplier and ask them to check. Then three worked examples at four, twelve and forty users so you can see what the arithmetic looks like when it is done properly, and the eight places where invoices diverge from the quotes they came from.

Here is a sentence that tells you nothing: "our platform is powered by AI." It is now true of almost every business communications product on the market, and it is compatible with at least five completely different architectures, five different accountability structures and five very different answers to the only questions that matter. At one end sits a company that operates its own network, its own platform and its own infrastructure, and can tell you where a particular call was processed on a particular Tuesday. At the other sits a product built in a few months on a public model API, where the entire technical estate is somebody else's and the company you are contracting with cannot change a thing about how your data is handled — because it does not control the thing handling it. Both companies can pass a feature comparison. Both can run an impressive demonstration, because the demonstration is of the model, and the model is very good. The difference only surfaces in three situations: when a data residency review asks where your customer conversations were processed, when something goes wrong and you need it fixed rather than escalated, and when a regulator asks you — not your supplier — to account for an automated decision. This article sets out the five kinds of company, the layers your call audio actually passes through, and ten questions that separate them in about fifteen minutes.

Ask most business owners what their phone system does and they will describe something that rings. That description was accurate for about a hundred years and stopped being accurate somewhere around 2023, but the language has not caught up — which is why so many Australian businesses are paying separately for software their phone platform already includes. A cloud voice platform in 2026 answers calls without a human, writes the customer record as it goes, distributes work across a team, creates the follow-up, offers the appointment, hosts the video meeting, sends the confirmation text and then reports on every one of those things in one place. That is eight product categories, most of which are sold separately by somebody, and several of which appear on Australian business bank statements twice. This is an honest inventory of what a phone platform now covers, what it does not, and how to work out which of your subscriptions you are paying for out of habit.

Two years ago, "AI" on a business phone quote meant something, because only a handful of providers had it. In 2026 it means almost nothing, because all of them do — or say they do, which from the outside is indistinguishable. Put four Australian cloud phone quotes side by side today and all four will offer an AI receptionist, AI transcription, AI summaries and AI call scoring, in roughly the same words, at roughly the same price. The feature lists have converged. What has not converged is what happens on the call. One of those systems will handle a caller who interrupts halfway through a sentence; another will keep talking over them. One will transcribe "Kariong" and "Ngunnawal" and "MYOB" correctly; another will produce something unrecognisable and then summarise the unrecognisable version as fact. One knows it does not know, and says so, and puts the caller through; another invents an answer with complete confidence. None of that is visible in a feature list, a demo or a pricing table, and all of it is visible within about two hours of structured testing. This article is about that testing. It is not a ranked list of providers — we publish one of those separately and it is linked below. It is the layer underneath a ranked list: the four layers behind any AI phone feature, the nine tests that separate a real capability from a bolted-on one, the questions about data residency and retention that most buyers only ask after signing, and a scorecard you can fill in during a trial. Run it against us as well as everyone else. That is rather the point.

Ask an Australian business what kind of phone system they have and the answer is usually a brand name, occasionally a technology, and almost never a generation. That is a problem, because the generation is the part that determines what happens next. A business on analogue copper lines, a business running an ISDN PBX in a comms cupboard, a business that bolted SIP trunks onto that same PBX in 2016, and a business on a cloud platform are four genuinely different situations with four different sets of options, four different risk profiles and four different bills. They are also, awkwardly, four situations that can all be described as having a phone system that works. This article lays out the four eras of business telephony — analogue POTS, digital ISDN with an on-premises PBX, VoIP, and Voice over Cloud — and what actually changed at each transition. It spends time on the distinction most buyers get wrong, which is that VoIP describes how voice travels and Voice over Cloud describes where the system lives, meaning they are separate decisions that get sold as one. And it finishes with a diagnostic you can run in five minutes to work out which era you are in, plus the honest arithmetic on when moving is worth it and when it is not.

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.