Choosing a phone system for a school campus

The least glamorous thing a school buys, and one of the few that has to work during an emergency. What actually matters, in the order it will bite you.

Phone systems are the least glamorous thing a school buys and one of the few that has to work during an emergency. That combination produces a lot of bad purchasing.

Here is what actually matters, in roughly the order it will bite you.

1. What happens when the internet goes down

Almost every modern phone system is cloud-hosted, and almost every vendor will tell you their uptime is excellent. That is usually true and entirely beside the point.

The failure mode that matters is not the vendor going down. It’s your site losing connectivity: a contractor through a conduit, a carrier fault, a power event. In that scenario a fully cloud-hosted system means a campus with no internal phones at all.

Ask specifically: with the WAN link severed, can the office still call a classroom? Can the classroom call the office? Can anyone make an emergency call? For many deployments the honest answers are no, no, and only from a mobile if you have reception, which in a 1970s brick building is not a given.

This is solvable, with an on-site component or a hybrid design, but only if you ask before you buy.

2. Emergency and lockdown procedures

A school’s communications requirements during an incident are unlike anything in a commercial deployment.

  • Can you initiate a campus-wide announcement from more than one location, in case the office is the location of the problem?
  • Can you announce to a zone rather than the whole site, so you can direct one building differently to another?
  • Does the announcement reach outdoor areas? Ovals and yards are where children actually are at the times you most need to reach them.
  • Can a teacher signal the office silently from a classroom?
  • Who can trigger these, and does it require a password nobody remembers under pressure?

Test these annually with the people who would actually use them, not with the IT coordinator who set them up.

3. The relief teacher test

Someone who has never been in the building must be able to call the office, and answer a call, without instruction. That is the entire usability requirement, and it eliminates a surprising number of otherwise capable systems.

In practice this means physical handsets with a clearly labelled button in classrooms, not a softphone application that requires a login. It means the office extension being the same memorable number everywhere. It means not relying on a directory the person cannot navigate.

4. Integration with how the office actually runs

The school office handles a very specific and repetitive workload: absence notifications, sick children, late arrivals, parent enquiries, and a morning peak that is genuinely brutal.

Practical things that pay for themselves quickly: a dedicated absence line with voicemail-to-email or transcription so it doesn’t consume the main queue; call routing that puts the morning rush into a sensible order; and caller identification against the student information system where it can be done cleanly and lawfully.

The last one is worth a conversation about data handling before anyone gets excited about it.

5. Cabling, power and the boring physical layer

Handsets need power. Power over Ethernet means switches with enough PoE budget, which means checking the existing switch capacity before assuming a straight swap.

Older school buildings routinely have cabling that will not comfortably support what you are proposing, and the discovery that a building needs recabling should happen during quoting, not during installation week. Any provider who quotes a campus phone system without physically inspecting the comms rooms and a sample of classrooms is guessing.

6. Who owns it afterwards

Schools change IT coordinators. Systems that only one person understands become systems nobody understands.

Insist on documentation written for a successor: extension list, zone map, how to add a handset, how to change the announcement, who to call. It should be readable by a competent person who has never seen the system.

The short version

Buy for the bad day. A phone system that is elegant on a normal Tuesday and useless during an incident has failed at the only job that genuinely can’t be worked around.

Ask every vendor the same question: walk me through exactly what happens, handset by handset, when the site loses internet during a lockdown. The quality of that answer tells you everything.


Written by

Matt Rollins is a Melbourne-based technology founder. He runs TechAssist, a managed IT provider serving growing Australian businesses, and is building TeachingBlox, AussieWave Hosting and Self Storage Auctions.

Start a conversation or connect on LinkedIn.