Getting your business phone system right from the start matters more than most people realise. A poorly configured system means missed calls, confused customers, and staff who route calls manually because the automation never worked properly. Done well, your phone system becomes one of the most reliable parts of your operation — handling call routing, after-hours messages, and departmental queues without anyone needing to think about it. This guide walks through every step of setting up a professional business phone system, whether you are a sole trader taking your first calls through a business number or a growing team building out a multi-department phone structure.
Why Cloud Phone Systems Have Become the Standard
Before getting into the steps, it is worth understanding why cloud phone systems have largely replaced traditional PBX hardware for Australian businesses.
Traditional PBX systems required physical equipment on-site — a cabinet full of hardware, copper line connections, and an ongoing relationship with a technician every time you needed to add a user or change your call flow. They were expensive to install, expensive to maintain, and almost completely inflexible. If your team moved offices or started working remotely, the system struggled to keep up.
Cloud phone systems — also called hosted PBX or VoIP systems — handle all the switching and routing in the cloud. There is no on-site hardware beyond the phones or devices your team uses. Your call flow configuration, voicemail, IVR, and routing rules all live in a web portal you can update yourself, often in minutes. Users can make and receive calls on a desk phone, a laptop softphone app, or a mobile — from the office, from home, or from anywhere with a reliable internet connection.
For small businesses, remote teams, and hybrid workplaces, this flexibility is not a nice-to-have — it is the reason cloud systems now dominate new installations across Australia. If you want a deeper comparison, hosted PBX versus traditional phone systems breaks down the key differences in full.
Step 1: Choose Your Phone System Type
The first decision is whether to go cloud or stick with a traditional on-premise system. For the overwhelming majority of businesses setting up a phone system today, cloud is the right answer.
Cloud suits small and medium businesses that want to get up and running quickly without capital expenditure on hardware. It suits remote and hybrid teams because every user connects through the internet rather than a physical office extension. It suits businesses that expect to grow, because adding users is a matter of provisioning a new seat in a portal rather than running new cabling or expanding a hardware cabinet. And it suits businesses that want to manage their own system, because cloud portals are designed for non-technical administrators.
On-premise PBX still has a place in very specific scenarios — typically large enterprises with dedicated IT teams, existing hardware investments, or compliance requirements that mandate on-site call data storage. If that does not sound like your business, cloud is almost certainly the better path.
You can read more about what a business phone system actually is and how it works if you want to build your foundation before continuing.
Step 2: Choose Your Business Phone Number
Your phone number is part of your brand, and the type of number you choose sends a signal to customers before they even speak to anyone.
A local geographic number — 02, 03, 07, and so on — works well for businesses that primarily serve a local area and want to reinforce their regional presence. A local number signals that you are a nearby, accessible business, which can be important for trades, professional services, and retail.
A 1300 number is a shared-cost number that makes your business appear national. Callers pay a local call rate regardless of where in Australia they are calling from, and you pay the remainder. A 1300 number is well suited to businesses that serve customers across multiple states or that want the credibility of a national-looking number even if they operate from a single location.
A 1800 number is free for the caller, with the business absorbing the full cost. This makes sense for businesses that handle high inbound call volumes, particularly where removing the cost barrier encourages customers to call — support lines, healthcare providers, and customer service operations are common examples.
You can also use more than one number. Some businesses use a local geographic number as their primary line and a 1300 number in national advertising. The key is choosing intentionally rather than defaulting to whatever number your provider assigns. Pickle offers both 1300 numbers and 1800 numbers with full cloud integration.
Step 3: Map Out Who Receives Calls
Before you configure anything, draw a simple map of how calls should flow through your business. This step is skipped constantly, and it is the reason so many phone systems are reconfigured within months of going live.
Start with a single question: when a customer calls your main number, what should happen? The answer depends on your team structure. A sole trader or very small business might route every call directly to one person or one mobile number — no complexity needed. A two-to-four person team might use a ring group, where everyone's phone rings simultaneously and whoever picks up first takes the call. A larger business with distinct departments might need separate queues — one path for sales, one for support, one for accounts.
Think through what happens when no one is available. Does the call go to voicemail? Does it overflow to another person? Does it go to a mobile if the desk phone is unanswered? These overflow decisions matter enormously for customer experience, and they need to be mapped before you start configuring anything.
Capture this as a simple diagram or even a written description of each scenario: normal hours call answered, normal hours call unanswered, after-hours call, public holiday call. Having it documented makes configuration far easier and gives you a reference point when something behaves unexpectedly.
Step 4: Configure Your Call Routing
Call routing is the logic that decides where each incoming call goes — and when. Getting routing right is what separates a professional phone system from a number that just rings a single phone until someone picks up.
At its most basic, routing connects an inbound number to a destination: a person, a ring group, or an IVR menu. But the real value of a cloud phone system is conditional routing — rules that change call behaviour based on time, caller input, or the status of team members.
Time-of-day routing is one of the most important configurations you will make. It ensures that calls during business hours go to your team, and calls outside those hours go to a professional after-hours voicemail or an on-call number if you offer one. Without it, customers calling at 8pm on a Sunday either ring indefinitely or hit a voicemail that was never set up properly. Time-of-day call routing explains how to configure this effectively.
Overflow routing handles what happens when the primary destination does not answer. You might set a ring group to try three team members, then overflow to a fourth, then send the call to voicemail after 30 seconds if no one has picked up. Each of these rules is configured individually, so it is worth thinking carefully about the order and timing before you start.
For a broader explanation of how routing works as a concept, what is call routing covers the fundamentals clearly.
Step 5: Add an IVR Menu — If Your Business Actually Needs One
An IVR (Interactive Voice Response) system is the "press 1 for sales, press 2 for support" menu that callers hear before being connected. It is genuinely useful for some businesses and completely unnecessary for others — and the mistake most small businesses make is adding one because it sounds professional, when it actually just frustrates callers.
If you have two or three people in your business and everyone handles all types of calls, an IVR menu adds nothing except friction. Customers hear "press 1 for sales, press 2 for support," press a number, and get connected to the same person who handles both. Remove the menu and route calls directly.
IVR earns its place when you have genuinely distinct departments or functions — where a sales call and a support call need to go to different people or queues, and getting that routing right matters for both the customer and the team member. It also works well when you have enough call volume that some basic self-service is useful — hearing your business hours, your address, or your current promotions without waiting for a person.
If you do implement an IVR, keep it to two levels maximum and no more than four options at any level. Anything more than that and you start losing callers. How IVR phone systems improve customer experience covers best practice in detail if you are building out a more complex menu structure.
Step 6: Set Up Your Voicemail and Business Greetings
Your greetings are the voice of your business, and they deserve the same attention you would give your website copy. A poorly recorded, generic voicemail message undermines the professionalism of everything else you have built.
There are several distinct greetings to think about, and each one serves a different purpose.
Your main opening greeting is what callers hear when they first connect to your number — typically a brief welcome and an introduction to your business before the call is routed. Keep it to ten seconds or less. Callers want to speak to someone, not listen to a thirty-second introduction.
Your after-hours greeting tells callers clearly that you are unavailable, when you will be back, and what to do in the meantime — leave a message, send an email, or visit your website. Give them a specific timeframe: "We will return all calls the next business day before noon" is more reassuring than "we will get back to you soon."
Your voicemail greeting should prompt callers to leave their name, number, the best time to call back, and a brief reason for their call. That information makes returning calls far more efficient for your team.
If you have an IVR, each menu option that goes to a queue or department might also need a queue greeting — something brief that confirms the caller has reached the right place and sets expectations about wait time.
Professional business phone greeting has example scripts and guidance on what each type of greeting should include.
Step 7: Decide Which Devices Your Team Will Use
Cloud phone systems give you genuine flexibility in how your team makes and receives calls, and the right device choice depends on how your people actually work.
Desk phones are still the right choice for reception staff, call centre agents, or anyone who spends most of their working day at a fixed workstation. A physical handset is ergonomically familiar, has dedicated buttons for transferring, holding, and conferencing, and does not depend on a computer being on and running. Quality IP desk phones have dropped significantly in price and are well worth the investment for high-volume call handlers.
Softphone applications — installed on a laptop or desktop computer — make sense for team members who are mostly at their desk but do not take a high enough call volume to justify a dedicated handset. Calls come through a headset, and the software interface handles all the functions a desk phone would. Many businesses use softphones as their default and only purchase desk phones for specific roles.
Mobile applications allow team members to make and receive business calls on their personal or company smartphone, presenting the business number rather than their mobile number. This is ideal for field-based staff, remote workers, and anyone who moves between locations. The key limitation is call quality — mobile calls over VoIP depend on a stable data connection, and calls over poor 4G or public Wi-Fi can be unreliable.
Many businesses end up using a mix of all three. The important thing is to match the device to the working pattern rather than trying to standardise on one type across the whole team.
Step 8: Check Your Internet Connection
A cloud phone system runs entirely over your internet connection, which means call quality is directly tied to your network performance. Before going live, you need to verify that your connection can handle both your normal data usage and VoIP calls simultaneously without degradation.
The rule of thumb for VoIP bandwidth is approximately 100 kilobits per second per concurrent call using a standard codec. In practice, this means that even a basic NBN connection — 25 Mbps download and 5 Mbps upload — can technically support dozens of simultaneous calls. Raw bandwidth is rarely the issue for small and medium businesses on modern NBN plans.
The more significant issue is Quality of Service (QoS), which is the way your router prioritises different types of network traffic. Voice calls are extremely sensitive to latency and packet loss in a way that browsing or email is not. A sudden spike in bandwidth usage — a large file upload, a video call on another device, a software update downloading in the background — can momentarily degrade your VoIP calls even on a fast connection, unless your router is configured to prioritise voice traffic.
Check that your router supports QoS configuration and that VoIP traffic is set to high priority. If your internet connection is shared with other bandwidth-heavy activities, consider a dedicated VLAN for your phone system traffic. For businesses with multiple simultaneous callers, a business-grade NBN plan with guaranteed upload speeds is worth the additional cost.
Packet loss above one percent and latency above 150 milliseconds will produce noticeable call quality issues. Both are measurable before you go live — run a VoIP-specific speed test and review the results before committing to your go-live date.
Step 9: Test Your Call Flow Before Going Live
Testing is the step that most people rush, and the one that catches the most problems. Before you point your business number at the new system, run through every scenario your call flow is supposed to handle.
Call your main number during business hours and verify that it reaches the correct destination. Test each IVR option if you have one and confirm the routing is correct. Call from a mobile and from a landline, because they can behave differently depending on how your number is configured.
Call during business hours with everyone's phone unavailable and confirm that overflow routing and voicemail behave as expected. Call after hours and verify that your time-of-day routing kicks in immediately and that the after-hours greeting plays correctly.
Test call transfers — both attended transfers (where you speak to the receiving person before connecting the caller) and blind transfers (where you connect immediately). Test conference calls if your team uses them. Test the hold music or hold message, and listen to what callers actually hear rather than assuming it sounds acceptable.
Make notes of anything that does not behave exactly as intended and resolve each issue before going live. A small investment in thorough testing avoids the far more costly situation of customers experiencing a broken call flow on day one.
Step 10: Review and Improve Your System Over Time
A phone system is not a set-and-forget configuration. The businesses that get the most from their phone system are the ones that treat it as an ongoing tool to monitor and refine.
Most cloud phone systems provide call reporting and analytics that give you a clear view of what is happening. The metrics worth watching regularly include total inbound call volume by time of day and day of week (which tells you when to staff up), missed call rate (which tells you whether your routing and capacity are adequate), average ring duration before answer (which reveals whether your ring groups and overflow settings are calibrated correctly), and voicemail completion rate (which tells you how many callers are leaving a message versus hanging up).
If your missed call rate is high during specific windows, consider adjusting your ring group settings, extending your overflow timing, or rostering someone specifically for high-volume periods. If you are getting consistent calls outside your configured business hours, consider whether your hours need to change or whether an on-call option makes sense.
Revisit your greetings quarterly and update them when your business hours, team structure, or key messages change. A Christmas holiday greeting that plays in April because no one updated it after the break is a surprisingly common problem.
The goal is a phone system that keeps pace with your business — growing and adjusting as you do, rather than becoming a source of friction as your team and customer base evolve.
Frequently Asked Questions
Q: How long does it take to set up a cloud business phone system?
A: A straightforward cloud phone system can be provisioned and configured in a single business day once you have your number and a basic call flow mapped out. More complex setups involving IVR menus, multiple departments, and integration with existing software typically take two to five business days. Porting an existing phone number to a new provider adds time — typically five to ten business days depending on the losing carrier.
Q: Can I keep my existing business phone number if I switch to a cloud system?
A: Yes. Number porting allows you to transfer your existing landline or virtual number to a new cloud provider without changing your number. During the porting process, you can run your old and new systems simultaneously to avoid any gap in service. Your provider will manage the porting process, but you should expect it to take at least a week and plan your cutover date accordingly.
Q: Do I need a new internet connection to run a cloud phone system?
A: In most cases, no. A standard NBN connection is sufficient for small and medium businesses. The important factors are upload speed and network Quality of Service configuration rather than raw download speed. If your business runs multiple simultaneous calls alongside heavy data usage, a business-grade NBN plan with guaranteed speeds and a QoS-capable router will ensure consistent call quality.
Q: What happens to calls if my internet goes down?
A: This depends on how your system is configured. Most cloud phone systems support failover routing, which redirects calls to a mobile number or alternative number automatically if your primary destination is unreachable. Setting up failover routing before you need it is strongly recommended. Some businesses also keep a basic SIM-based mobile as a backup line for genuine outages.
Q: Is a 1300 number or a local number better for my business?
A: It depends on who you are trying to reach and what impression you want to make. A local geographic number works well for businesses with a clear local presence and a primarily local customer base. A 1300 number suits businesses that want national reach or a more corporate appearance, and is particularly effective in advertising where you want customers anywhere in Australia to call without hesitation. Many businesses use both.
Ready to Set Up Your Business Phone System?
If you are ready to move forward, Pickle can have your cloud phone system configured and live within days. Our team handles everything from number selection and porting through to call routing, IVR setup, and device provisioning — so you are not working through a setup wizard on your own.
Visit Pickle's business phone systems page to see plans and features, call us on 1300 688 588, or reach out at [email protected] and we will walk you through what your setup should look like before you commit to anything.