The short version: while auditing a Melbourne business’s phone system recently, we found its after-hours rules had been running an hour out of step with reality for roughly half of every year — for as long as anyone could remember. Nobody had noticed. Nobody could have noticed, because the only people affected were the ones calling when the office was shut.
The number that couldn’t be true
The audit started the way ours do: export the call logs, and let the data argue. Thirteen months of records, every call to the main line, cross-checked against the advertised opening hours.
One number stopped us: 349 after-hours calls answered by a person. For a business with no after-hours staff, no on-call roster and no answering service, that’s not impressive — it’s impossible. Either someone was secretly working nights, or the data was lying.
The data was lying, in a very specific way. The phone system was a tenant on a shared, multi-tenant hosted PBX, and the tenant’s clock was set to fixed UTC+10 — no daylight saving. Melbourne runs on AEDT from October to April. So for half of every year, every timestamp in the system — and every time-based rule built on it, including “we’re closed now” — was an hour wrong.
Re-run the same analysis with a clock that actually knows where Melbourne is, and the 349 answered after-hours calls collapse to exactly one — a single call, in thirteen months, that genuinely reached a human outside opening hours. The other 348 were ordinary business-hours calls, mislabelled by a phone system that didn’t know what city it was in.
Why nobody caught it
Think about what this defect looks like from inside the business: it looks like nothing. The phones work. Callers get through during the day. The staff go home.
But from October to April, the after-hours greeting was switching on an hour late every evening — an hour in which callers heard ringing, then voicemail, while the system’s own logs recorded business as usual. And every morning it was switching off an hour late, in the other half of the year. The people affected were, by definition, the ones calling when nobody was there to see it. The complaint never comes, because the caller who hits a dead line at 5:15pm doesn’t file a bug report — they call the next business on the list.
This is why the defect survives: it’s invisible from the inside and routine from the outside. We’ve written before that most off-the-shelf phone and voice-AI products ship with clocks and holiday tables configured for somewhere else — a national template, a fixed offset chosen by an offshore vendor, a default nobody reviewed. We put it on our Melbourne and Brisbane pages as a warning. A fortnight later, a live audit handed us a textbook case.
The fix is boring. Finding it is the work.
The remediation is genuinely trivial — a timezone setting, corrected in minutes as part of a system migration. There’s no product to buy and no AI involved in the fix. That’s rather the point.
The finding is the product. It fell out of a fixed-fee audit — the same audit, analysis and report we run for any business, from $800 ex GST — because the analysis treated the business’s own call data as evidence rather than taking the system’s word for it. (In this case the heavy lifting on 13 months of logs was done by the same AI tooling that builds and runs this website — supervised, as always, by a human who has run phone systems for 32 years.)
Two questions worth asking about your own setup this week:
- What timezone does your phone system actually think it’s in? Not your desk phone’s display — the PBX itself, where the after-hours rules run. If you’re in a daylight-saving state and the answer is a fixed UTC offset, your rules are wrong for half the year, right now.
- Who would notice if your after-hours handling silently broke? If the honest answer is “nobody”, that’s not a staffing failure — it’s just what happens when nobody is measuring. It’s also the first thing an AI receptionist changes: every after-hours call gets answered, logged and visible.
We’ll say it plainly: most businesses don’t need to hire anyone to check this.
Log into your PBX, find the timezone setting, and look. If it says UTC+10
and you’re in Melbourne, you’ve just found an hour of every summer evening
you didn’t know you were losing.