Help Desk Claims in Chicago: What Our Data Shows
Chapters
Disclosure: this site is owned and operated by XL.net, a Chicago MSP that is itself ranked here. How we handle that conflict.
TL;DR
Help Desk is the delivery model published by more of the firms we track than any other — 54 of 65 among the firms that publish delivery models at all — so its presence in a proposal separates almost no one on our shortlists. Read against our Proactive Issue Reduction distribution, which has a median of 9.5 and a middle half of 0.0 to 25.0 across the 54 of 97 firms we could score, an advertised help desk says nothing about whether a firm's workforce mix leans proactive. The useful work is in the scope behind the line, not the line itself.
- Help Desk is the most-published delivery model in our records: 54 of 65 firms that publish any.
- Our Proactive Issue Reduction attainment has a median of 9.5 and a middle half of 0.0 to 25.0, scored for 54 of 97 firms.
- For 32 of 97 tracked firms we hold no published delivery models at all — silence in our records, not evidence of absence.
- Our position: a per-user rate without scope context is misleading, so press on what the help desk line actually covers.
- Our delivery-model crawl records claims firms publish about themselves; it is never a capability we assessed.
Why do help desk claims in Chicago separate so few providers?
Because it is the most common published delivery model in our records, so the claim does almost no comparison work. IT Support Chicago's records show Help Desk published by more tracked firms than any other delivery model, 54 of 65 among firms publishing any. The next most common line, 24/7 Monitoring, appears for 35 of 65, and Unlimited Support for only 6 of 65 — so the help desk line sits at the crowded end of the shelf.
Two caveats matter before a buyer reads anything into that. First, these counts come from what firms publish on their own websites, as read by our crawler: a claim we recorded, never a capability we assessed. A published help desk tells us a firm markets one. Second, the count is drawn from the 65 firms that publish delivery models at all, not from every firm we track, so it describes a pattern in published marketing language rather than a census of service desks across the metro area.
The practical consequence for a shortlist is simple. If three proposals all lead with a help desk, the claim has not told you which one to prefer, and the differences that matter — hours, escalation paths, who answers, what is excluded — are still unwritten. Treat the line as table stakes and spend your evaluation time on the sentences underneath it.
Does a published help desk tell you anything about reactive versus proactive staffing?
No. The two data points sit in different places in our records, and an advertised help desk says nothing about where a firm falls on the staffing measure we score. IT Support Chicago scored Proactive Issue Reduction for 54 of 97 firms, at a median of 9.5 and a middle half of 0.0 to 25.0. The mean is 14.9. That dimension carries a weight of 27 of 100 in our published score, and it is built by classifying employee job titles as proactive — architects, security engineers, consultants — against reactive ones such as help desk, network operations centre and support technician roles, using Apollo.io workforce data. Attainment rises as the reactive share of classified titles falls.
Our weakness records make the separation concrete. They carry entries worded exactly as a heavily reactive support model with the reactive share stated — one reads 86% reactive roles, sourced to Apollo. Our delivery-model crawl and our weakness column are separate datasets, and the denominators behind them differ, so a published help desk claim neither rules a reactive-workforce flag in nor rules one out.
The buyer-side move is to ask for the staffing mix directly rather than infer it from a services page. Ask how many people hold engineering, security or architecture titles versus dispatch and tier-one titles, who owns problem management when the same ticket recurs, and what share of tickets the firm expects to prevent rather than close. Our proactive IT staffing ratio guide walks through the same ratio we score and the limits of reading job titles from the outside — titles are a proxy, and a proxy can misread a small firm where one person wears several hats.
What silence in our delivery-model records does and does not mean
It means we hold nothing, and nothing more. IT Support Chicago holds no published delivery models at all for 32 of 97 tracked firms, which is silence in our records. A firm outside our Help Desk count is a firm we hold no such record for — never a firm we have established lacks a service desk.
That cuts both ways in an evaluation, and it is a limit on our data rather than a signal about the firm. Our crawler reads published pages; it does not observe staffing, ticket handling or coverage hours, and it cannot distinguish a firm that does not market a support model from one that describes it in wording we did not index.
So when our data shows no delivery models for a firm you are otherwise interested in, the right response is a question, not a deduction. Ask what the firm's support model is called internally, how tickets arrive, who triages them, during which hours, and what happens when the primary channel is unavailable — then compare that answer against the published claims of the firms you are weighing it against.
How should you evaluate what a help desk line actually covers?
By forcing the scope into writing before you look at any rate. IT Support Chicago's position is that a per-user rate quoted without scope context is misleading. Two proposals can price the same word and mean different services: a help desk covering only company-managed laptops during business hours and a help desk covering line-of-business application support, mobile devices and after-hours escalation are not comparable inputs to a spreadsheet, however similar their unit pricing looks.
A workable approach to help desk scope evaluation is to write the questions before the vendors write the proposals. Which devices and applications are in scope, and which are named exclusions? What are the coverage hours, and what happens outside them? Are on-site visits included or billed separately? How is third-party vendor liaison handled? Does any ticket-volume or project-hours cap apply, and how is the count of billable users or devices defined and adjusted mid-term? Our Chicago SMB IT scope checklist covers these in order and is built to be pasted into a request for proposal.
One limitation is worth stating plainly: we do not collect vendor pricing, so we cannot tell you what any of this should cost. What our data can do is show which claims are common enough to be uninformative, and which scored dimensions a claim has no bearing on. On terms, our view is that shorter agreements are generally better for the buyer, and that where scope is still uncertain, a workable exit is more useful recourse than a service credit.
Where delivery-model claims sit against the rest of our score
Published claims about delivery models carry no weight in our score at all. Our published ranking combines four criteria scored from public evidence — Client Reputation at 29 of 100, Proactive Issue Reduction at 27 of 100, Security Certification at 24 of 100 and Employee Reputation at 20 of 100 — and a help desk claim is not one of them. IT Support Chicago tracks 97 firms at an average vendor score of 19.5%, ranging from 0.8% to 77.6%. The average client rating across that set is 4.76 / 5.0, drawn from 7,884 reviews. Our breakdown of how scores spread across dimensions shows why two firms with similar totals can be built very differently.
The Security Certification criterion is worth reading carefully, because it is not a single yes-or-no test. Entries we hold third-party documentation for — a named third-party issuer's document, evidence hosted off the firm's own domain, or a public registry entry — are scored additively by tier, while a firm's own undocumented claims add 5 points each and cap at 25 out of 100. Both marks describe what we could obtain, never how secure a firm is.
If you want to check a framework yourself rather than rely on a mark in anyone's table, ask the provider for the issuing body, the scope statement, the observation period or certificate dates, and the report or registry entry you can read directly. Our certification verification checklist sets out the order to ask in, and it applies the same way whether the provider publishes a help desk or nothing at all.
Frequently asked questions
Is a Managed Service Provider (MSP) without a published help desk a weaker option?
Not on our evidence. We hold no published delivery models for 32 of 97 tracked firms, which is silence in our records rather than an established gap in service. Ask the firm how support requests arrive, who triages them and during what hours, then compare that answer against the published claims of other candidates.
Why does an advertised help desk not improve a firm's score with you?
Our four published criteria score client reputation, employee reputation, proactive staffing mix and security certifications, where documented entries are additive and a firm's own undocumented claims cap at 25 out of 100. Self-published delivery-model claims are recorded but unweighted. Proactive Issue Reduction, at 27 of 100, is the dimension closest to support delivery, and it is built from job-title classification rather than from website wording.
Can I just compare providers on their per-user help desk rate?
Our position is no. A per-user rate without scope context is misleading, because coverage hours, in-scope applications, on-site work and named exclusions vary between proposals that use identical wording. Define scope first, then compare rates against that fixed definition. We do not collect vendor pricing, so we publish no rates or ranges of our own.