The helpdesk is the part of IT support your staff actually touch. Everything else can be well designed and it will still be judged on what happens in the ten minutes after somebody cannot print, cannot log in, or has clicked something they should not have. This page describes that — how a ticket reaches us, who picks it up, how it is prioritised, and when someone gets in a car. It does not describe the contract; that is on our managed IT services page.
Existing client or not, describe the problem and we will tell you what fixing it would involve. We are at 22 Frederick St, Suite 700, in downtown Kitchener.
We reply within one business day. We do not share your data.
24/7 managed IT for Kitchener businesses. Named engineers, flat monthly fee, no surprise invoicing.
Learn more →Kitchener IT support with a 15-minute critical response target. Real engineers answer, not scripted call-center staff.
Learn more →EDR, phishing simulation, and 24/7 SOC monitoring. Purpose-built for SMBs in Kitchener-Waterloo and across Ontario.
Learn more →Microsoft 365, Azure, and hybrid cloud built for Kitchener SMBs. Licenses managed, tenants hardened, migrations done right.
Learn more →Canadian-hosted backup with verified restores. Kitchener businesses stay running when ransomware, hardware failure, or outages hit.
Learn more →Quarterly roadmaps, budget planning, and vendor negotiation. The strategic layer above your Kitchener IT support desk.
Learn more →Our Kitchener HQ is central downtown. On-site attendance from a local team, not a call center overseas.
You get the same engineers who know your setup. Escalation to senior technicians when needed. No "first available" roulette.
Independently audited security controls. The same standard we apply for enterprise clients.
A quick reference for Kitchener businesses working with technology partners in the region.
Your staff should not have to remember a process in order to report a broken laptop. Four routes in, and every one creates the same ticket, in the same queue, with the same ownership.
On the phone, a person answers, and that person can begin working on the problem rather than taking a message for someone who can. The most common complaint we hear about a previous provider is not slowness — it is having to explain the same problem three times. By email, a ticket is created automatically with a reference, and replying to that acknowledgement adds to the existing ticket rather than opening a second one.
Covered devices carry a small support application: staff click it, describe the problem, and a technician can connect with permission and see what the user is seeing. Ad-hoc sessions for devices that are not covered use the tool on our remote support page. Where you run Teams, staff can raise a request from inside it, and for most office workers that becomes the default route within a fortnight.
One thing we ask. Route requests through the desk rather than to an individual technician’s mobile. Direct messages create work nobody else can see, cover, or escalate.
Every ticket is read and categorised on arrival, not when it reaches the front of a queue. Triage establishes what is affected, how many people are blocked, and whether it is a security matter — because a security matter leaves the standard queue immediately.
Nobody can work, or a critical system is unavailable. Everything else is put down.
One department cannot invoice, dispatch, or serve customers.
A degraded machine, a slow application, a failing peripheral.
A new starter, a mailbox change, a software installation, a permission adjustment.
Response and resolution targets against each band are written into your service agreement and reported monthly. No headline number appears on this page, for the reason given in the FAQs below.
A ticket has one named owner from the point it is triaged. If it needs a specialist, the specialist joins the ticket — the owner does not hand it over and stop caring. Tickets are closed when the person who raised them agrees they are fixed, not when the technician believes they are, and the closure note records what was actually wrong. That is what makes the pattern visible when the same fault turns up on four machines.
Ours is an ITIL certified service desk, which in day-to-day terms means incidents, requests, problems and changes are handled as four different things rather than all being called “a ticket”. That distinction sounds procedural until the third time the same fault appears and somebody has to decide whether to keep fixing it or find out why.
Technicians have your documentation open before they pick up: your environment, your standard build, your applications, and what has broken before. The desk is small enough that the same names recur, which is what allows someone to say “this is the third time on that switch”.
Where an issue exceeds first-line scope it moves to a senior engineer, and for infrastructure matters to the engineer who knows your environment. Escalation is triggered by the nature of the problem and by elapsed time, so a ticket cannot sit quietly with somebody who is stuck and does not want to say so.
Security alerts do not go into the general queue. Our Security Operations Centre runs separately and around the clock, because a compromised account is a containment exercise with a clock on it, not a support request. Our own handling of client data and access is covered by a SOC 2 Type 2 attestation — audited rather than self-declared. And where you have staff in Quebec, or francophone staff here, support is available in French — see bilingual technical support.
Most tickets are resolved remotely, and that is the faster outcome rather than the cheaper one — a technician connecting to a machine straight away beats one arriving in forty minutes.
Failed hardware and replacement swaps. Cabling and patching. A switch or firewall that has stopped responding to anything remote. New site builds and office moves. And the physical equipment that always turns out to be unplugged in a way nobody could see over a screen share.
We are at 22 Frederick St, Suite 700, in the downtown core — roughly ten minutes to uptown Waterloo, twenty to Cambridge, half an hour to Guelph. Short journeys rather than expeditions, which is the practical difference between a provider based here and one dispatching up the 401 from the GTA for an hour in each direction.
Emergencies get same-day attendance. Everything else is scheduled, usually grouping several jobs into one visit so your day is interrupted once rather than four times. Onsite attendance for covered sites is included in a managed agreement — see onsite IT support.
Home and hybrid workers are supported the same way as anyone at a desk. Two local details are worth stating. Staff out on the fringe — Baden, New Hamburg, Elmira, St. Jacobs, Wellesley, Ayr — are often on connections that behave nothing like the office link, and when a call drops or a file sync stalls the laptop is usually not the problem. Diagnosing that correctly the first time saves a wasted afternoon and an unnecessary drive in. And the morning after a storm closes the 401 or Highway 7 and 8, everybody works from home at once — which is the day a business discovers how much concurrent remote capacity it actually has. Better to know in advance than at 8:15 on a Monday.
A lot of Waterloo Region does not start at nine. Manufacturing, food processing, distribution and logistics run shift patterns that begin before six in the morning and change over mid-afternoon. An IT problem at 6:05am on a line that is starting up is not an after-hours inconvenience — it is the most expensive moment of the day to be stuck, and it falls well outside the hours any single internal person can reasonably hold. The desk is staffed around the clock, so a call at two in the morning reaches a person rather than a voicemail box checked at nine.
A business-down event. A suspected compromise or ransomware incident. A failed server. A connectivity loss at a site that is trading or running. One user with a slow laptop at nine on a Saturday evening is not an emergency, and we would rather say so here than have you discover the distinction during one.
Server reboots, firmware, major updates, migrations and cutovers are done outside working hours by design — and where you run shifts, “outside working hours” is a narrower window than most providers assume, so we set it against your actual pattern rather than a default Saturday night. Planned work carries a defined window and a stated fallback position.
Account administration is unglamorous and it is a large fraction of what any helpdesk actually does. It is also the thing most often left half-finished, and the half that gets skipped is always the leaver.
New starters are built from a checklist agreed with you: account, licence, security groups, machine build, applications, phone. Leavers run the same way in reverse on the date you specify — account disabled, sessions revoked, mailbox handled as instructed, licence released, machine collected.
Three times a year, in January, May and September, a large number of employers here turn over a meaningful share of their staff in the same fortnight. Co-op terms end and begin together. For a company running a dozen students that is a dozen builds and a dozen offboardings, twice a year — and it arrives as a wave rather than a trickle of individual tickets.
Handled casually, this is where an environment quietly rots. What we find on taking over is consistent enough to predict: licensed accounts belonging to people who left two intakes ago, a repository somebody still has access to, a personal laptop added to the network during a busy onboarding week and never removed.
So intake is treated as a scheduled operation rather than a queue of P4s. Machines are imaged and accounts provisioned before day one. The offboarding list runs on the last day of term whether or not anybody remembers to raise it. Licences come back, which is a recurring cost rather than a tidiness point. And a student returning for a second term is a restore rather than a rebuild.
Anything that changes the shape of your environment is a project rather than support: a server or firewall replacement, a Microsoft 365 tenant migration, an office move or a new site, a network redesign, rolling out a new line-of-business application. These are scoped and quoted separately, because project work done inside a support queue gets interrupted by support and both suffer. We flag that boundary as soon as we see it, rather than starting and raising the question halfway through.
Most Kitchener businesses under about eighty people have somebody who is not in IT but has become the person others walk over to when something breaks — an operations manager, a finance lead, or whoever was visibly competent with a computer in year one. They did not volunteer, they are interrupted constantly, and none of it appears in their job description. The change after a helpdesk is onboarded is that this person gets their own job back. If that describes somebody at your company, they should be on the first call.
Staff get one place to report a problem and an acknowledgement that confirms it landed. They are asked what they were doing when it broke rather than told to turn it off and on again by somebody who has not looked. Managers get monthly reporting: ticket volume, what the tickets were actually about, and how they were distributed. Recurring categories point at a fixable cause rather than a run of bad luck, and a business paying every month is entitled to see whether the underlying number is going down.
Yes. Ad-hoc and hourly support is a real option and plenty of clients start there — see IT support. What it does not include is the monitoring, patching and preventative work that stops tickets being raised at all. The comparison sits on our managed IT services page.
Yes — 22 Frederick St, Suite 700, in the downtown core. Remote support is unaffected by geography, but onsite attendance across Waterloo Region is dispatched from that office, and we would rather state where we are than imply a presence everywhere. Our general Kitchener page has the wider service picture.
Critical, business-down issues carry a 15-minute response target. The remaining priority bands are set in your service agreement and reported against each month. We publish that one figure with the priority definition attached, because a number quoted without a scope behind it is not a commitment to anything.
Largely, yes. Your account has a named team who hold the context. Around-the-clock and holiday coverage means it will not be the same individual every time, which is why the documentation matters.
Yes. The desk is staffed around the clock, and where you run shifts we set the escalation path against your pattern rather than against office hours — including who on your side can authorise what at five in the morning, when the usual approver is asleep.
We take it on. Dealing with a line-of-business vendor, an internet provider or a telephone carrier on your behalf is part of the service, and it saves your staff sitting in somebody else’s support queue describing a technical problem they did not cause.
Contact the desk immediately and say exactly that. Nobody here is interested in blame, and delay is the only thing that makes it materially worse. The account is contained first and investigated second. Reporting a phishing email that turns out to be harmless is always the right call — we would rather field ten of those than miss one.
401 Bay St, 16th Floor, Toronto Ontario
141 Main Street N, Markham, ON L3P 1Y2
1315 Pickering Parkway, Pickering, ON L1V 7G5
8815 Av du Parc #402, Montréal, QC H2N 1Y7
6700 Century Ave, 3rd floor, Mississauga, ON L5N 1V8
22 Frederick St, Suite 700, Kitchener Ontario
Describe what is going wrong and how it is affecting the business. We will tell you what fixing it involves, whether that is a single call-out or something that has been building for a while.
If you are comparing providers, ask each of them two questions: how a ticket gets escalated when the first person cannot fix it, and what happens at eleven at night. The answers are revealing, and they are usually short.
We reply within one business day. We do not share your data.
%20(1).avif){kind=logo}
%201.avif)
