Monday morning, 8:45 am. In a typical Australian school office, the scene is predictable. Two parents are at the counter waiting to discuss an enrolment, a student is sitting on the "sick bay" chair with a grazed knee, and the phones are ringing. Not just once, but on three lines simultaneously.
Most of these calls are parents reporting an absence or asking about the swimming carnival. They are important calls, but they don’t necessarily need a human to handle them right that second. This is where an AI receptionist steps in. But for many school business managers or IT owners in service businesses, the big question isn't "Does AI work?" — it’s "How on earth does it plug into our phones?"
At Yindi, we’ve spent a lot of time building our own telephony stack. We didn't just wrap a fancy interface around a basic API; we built a PBX-native system. This means we can connect to your existing setup in the way that actually makes sense for your school or business, not just the way that’s easiest for us.
Here is a plain-English guide to the three main ways we connect to your phone system: SIP Trunks, Extensions, and Call-Forwarding.
1. Cloud PBX AI Receptionist: The Extension Method
If your school or business is already using a modern cloud-based phone system (like 3CX, Microsoft Teams, or a hosted VoIP platform), the "Extension" method is often the cleanest way to go.
In this setup, Yindi simply becomes another "staff member" on your system. We are assigned an internal extension number — let's say extension 500. When a call comes in, your system can be programmed to ring the front desk first, and if nobody picks up after three rings, it automatically passes the call to Yindi at extension 500.
Why this works well:
- Visibility: You can see Yindi on your internal phone dashboard just like any other handset.
- Easy Transfers: Because Yindi is "internal," it can easily pass calls back to the registrar, the principal, or a technician without the caller ever leaving your phone system.
- Simple Management: You don’t need to change your main phone lines or move your numbers to a new provider.
For businesses using CommTrak integration, this extension method allows for seamless job logging because the call stays within your established ecosystem.
2. The Professional Standard: SIP Trunking
For larger schools, hospitals, or service businesses with dedicated on-premise hardware or more complex needs, we connect via a SIP Trunk.
Think of a SIP Trunk as a virtual "pipe" that connects your phone system directly to ours over the internet. Instead of Yindi being a single extension, the SIP trunk allows for multiple simultaneous calls to be handled at once.
If you are an IT manager for an MSP or a large trade business, you’ll recognise this as the most "robust" way to handle high call volumes. When your primary lines are busy, the overflow goes straight down the SIP trunk to Yindi.
The benefits of SIP Trunking:
- Capacity: You aren't limited to one "extension." Yindi can handle many calls at once during a morning rush.
- Cost Efficiency: Connecting via SIP often avoids the "per-minute" forwarding costs that traditional carriers charge when you divert a call to an external mobile or landline.
- Data Integrity: We keep the original "Caller ID" intact, so when you see the transcript in your Yindi dashboard, you know exactly who was calling without any "ghosting" from the phone network.
3. The "Quick Start": Simple Call-Forwarding
We’ll be honest: sometimes you just want it to work now without touching your PBX settings or calling your IT provider. Or perhaps you’re a smaller trade business or a boutique medical practice using a basic phone line.
In these cases, we use Call-Forwarding. We provide you with a unique Yindi number, and you simply set your phone to "Forward on Busy" or "Forward on No Answer" to that number. It takes about 30 seconds to set up.
When to choose forwarding:
- After-Hours Coverage: You can turn forwarding on when you leave the office at 5:00 pm and off when you arrive at 8:00 am.
- Emergency Overflow: If your team is heading into a three-hour staff meeting, you can "divert all" to Yindi instantly.
- Low Technical Barrier: No need for SIP configurations or extension mapping. It just works.
While some AI receptionist alternatives only offer this method, Yindi treats it as just one of many tools in the shed. We don’t force you into a divert if a native integration is better for you.
The Yindi Difference: PBX-Native vs. The "Wrapper"
Most AI receptionists on the market today are what we call "wrappers." They take a third-party AI voice API and a third-party phone API (like Twilio) and glue them together. The only way to use them is to forward your number to their platform.
If you want to transfer a call back to your office, these systems often have to "dial back out" to you, creating a fragile chain of calls that can drop, lag, or cost a fortune in carrier fees.
Yindi is PBX-native. We built our own telephony stack specifically for the Australian market. Because we understand the "language" of phone systems (SIP protocols, codecs, and trunking), we can sit inside your communication flow.
When Yindi answers a call for an Australian school, it’s not just a robot on the end of a diverted line. It’s an intelligent layer of your existing phone system that can recognise if a parent is calling about a sick kid and route that data to the right place.
Why Technical Integration Actually Matters to Your Bottom Line
It’s easy to think, "As long as someone answers, who cares how it's connected?" But the method of connection has real-world impacts on your daily operations:
- Caller ID Retention: Have you ever had a diverted call show up as "Private Number" or your own business number? It’s frustrating. Native integration ensures you always see the actual caller's number.
- Cleaner Transfers: There is nothing more "robotic" than a call being put on hold for 10 seconds while a system tries to bridge two external lines. Yindi's native stack makes transfers feel like they’re happening within the same building.
- Reliability: Fragile forwarding chains are prone to failure. If one link in the chain (the carrier divert) has an issue, the whole call fails. A SIP or extension-based connection is direct and stable.
- Australian Hosting: Because we built our stack here, your data stays here. For schools concerned about compliance and child safety, knowing that your telephony isn't bouncing through three different international data centres is a big deal.
Which one is right for you?
If you're unsure which method fits your setup, don't sweat it. Most of our customers aren't "phone people" — they just want the ringing to stop so they can get back to work.
- Schools: We usually recommend the Extension or SIP Trunk method to handle the heavy 8:30 am rush and ensure parents can be transferred to the right department.
- Service Businesses: If you're on the tools or in a ute, Call-Forwarding is often the easiest way to ensure you never miss a job lead while you're on a roof or under a sink.
- IT/MSPs: You’ll likely want the SIP Trunk to maintain full control over your call routing and client data.
Yindi is an AI receptionist for Australian schools and businesses that works on demand or always on — your choice. We aren't here to replace your team; we’re here to give them a hand when the phones won't stop.
Curious if Yindi could help your school or business? We’d love to show you how it works in a real environment — and connecting it is quick, whichever method suits you best.
Book a demo at yindi.com.au or give us a buzz on 1300 094 634.