MapleTriage Full 30-year timeline →
About the Architect

Who created MapleTriage, and why?

MapleTriage is built by Joel Gathercole, founder of Joel & Nanz Inc. He spent 20 years at TriageLogic, rising from external VoIP solutions provider to Head of IT and ultimately Director of IT, architecting and scaling the infrastructure behind clinical nurse triage — systems where sorting an incoming contact correctly is a patient safety matter. Before that, he founded Netrique Inc. (2002-2006) and built call-centre routing engines when VoIP was still novel (2006 archive). MapleTriage brings that healthcare-grade triage discipline to ordinary business customer service.

Triage is a medical word, and it means something precise: when more things arrive than you can handle at once, you sort them by urgency, and you sort them correctly, because the cost of getting it wrong is not evenly distributed.

Joel Gathercole spent 20 years inside that discipline. At TriageLogic, a relationship that began in 2006 as a VoIP engagement became a two-decade career — external solutions provider, then Head of IT, then Director of IT. He architected, secured and scaled the infrastructure behind nurse triage: contacts arriving continuously, each needing to be routed to the right person at the right level of urgency, on systems that had to hold at 3am with sensitive patient data flowing through them.

The foundation was laid earlier still. In 2002 he founded Netrique Inc., developing VoIP and call-centre routing when most businesses had never heard of a call travelling over a data line. The 2006 site is preserved on the Internet Archive. Building routing engines then — where every call had to reach the correct queue, the correct skill group, the correct fallback — is the direct technical ancestor of everything MapleTriage does now.

Here is the observation that produced the product: every business runs triage, but almost none of them run it deliberately.

A plumbing company gets a burst pipe and a routine quote request in the same five minutes, and both sit in the same inbox. A property manager gets "no heat" and "how do I book the elevator" and the wrong one gets answered first. A clinic, a law office, a dealership, a landscaping crew — each one is triaging every day using nothing but whoever happens to check messages next. Enterprises solved this decades ago with routing engines and priority queues. Small businesses were never sold that capability at a price they could pay.

MapleTriage is that capability, rebuilt for Canadian SMBs and driven by AI. Incoming contacts — calls, forms, emails, messages — are read for urgency and intent, sorted, routed and escalated by rules the business actually controls. Emergencies surface immediately. Routine requests get handled routinely instead of drowning the emergencies. Nothing sits unread for two days because it arrived on a Friday.

The distinction worth naming is the standard it was built to. Most SMB tools in this category start from marketing automation, where the failure mode is a missed opportunity. MapleTriage starts from clinical triage architecture, where the failure mode was a patient waiting too long. Joel built to that second standard for 20 years, and did not lower it when he pointed the same logic at a plumbing company's phone line.

MapleTriage is part of the MapleWorkSuite ecosystem from Joel & Nanz Inc., built in New Brunswick, on Canadian infrastructure — because a triage record is a record of your customers' worst days, and that belongs at home.

Joel and Nancy, the two founders of Joel & Nanz Inc.
Joel and Nancy, Joel & Nanz Inc., New Brunswick.

Verified historical record

Independently timestamped on the Internet Archive — the evidence behind the 30-year claim:

The same architect, across the Maple network

Every product came out of a different part of the same 30-year timeline. Each page explains which experience produced it: