Only wake up for the burst pipe, not the leaky tap.

When a call, text or email comes in outside business hours, the workflow gathers the details and works out how urgent it actually is. A burst pipe with water everywhere gets escalated immediately, with the full details sent straight to whoever's on call. A leaky tap gets the same courteous response and its details captured, but is booked in for the next business day instead of waking anyone up.

It's configured around your business, not a generic keyword list — for a plumber, a burst pipe or flooding is urgent and a dripping tap isn't; for an IT provider, a server outage is urgent and a password reset isn't. We work through what genuinely needs an immediate call versus what can safely wait until morning before anything goes live.

No — this triages business enquiries like a burst pipe or a server outage, not life-threatening emergencies. Anyone with a genuine emergency should always call 000 directly, not your business number. This solution is about protecting your own after-hours availability for business-critical issues, not emergency response.

Yes — the same triage logic applies regardless of which channel someone uses to reach you after hours, so urgency is judged consistently rather than depending on how the contact came in.

That's specifically what this is built to prevent — the whole point is fewer unnecessary wake-ups, not more alerts. Genuinely routine contacts are captured with full details and queued for the next business day instead of escalated.

Yes — it's built to route the urgent alert to whoever is actually on call, rather than assuming one fixed person. If you already rotate who's on call, that rotation is respected.

It's tuned specifically to your business's real definition of urgent before it goes live, and refined if something gets misclassified early on. It's not perfect on day one for every possible scenario, which is why the definitions are reviewed with you rather than left as a generic default.

Yes — that's the actual setup work. What counts as urgent for a plumber (flooding, no water, no power) is different to what counts as urgent for an IT provider (a server down versus a slow laptop), so this is configured around your specific business rather than a one-size-fits-all rule.

Often, yes — the two are commonly run together. Missed Call Text-Back handles the immediate response and qualification; After-Hours Triage adds the layer that decides whether that contact needs someone woken up right now or can genuinely wait.

Because the urgent/routine definitions have to be worked out specifically for your business before anything goes live, it typically takes one to two weeks from your call to a tested, live workflow.

For many businesses, yes — it does the specific job of deciding who needs to be woken up, without a human answering service in between. Some businesses keep both; that's a fit conversation, not a fixed rule.

Indicative pricing is $950 to set up and configure, then $179 a month to run and monitor. See the pricing section above for what's included, and we'll confirm your exact number on a short call once we understand your after-hours volume and what genuinely counts as urgent for your business.