How I knew that, before you told me anything
If a stranger emails you a specific observation about your service desk, the reasonable first reaction is to wonder where they got it. This page answers that in full. Everything below is public, and none of it requires access to anything you run.
The four artefacts
| Artefact | Where it is read | What is inferred |
|---|---|---|
| Support-tier or service-level page | Your own website | The tiers you sell, and whether the table separates what first line closes from what it escalates. Usually it does not. |
| Response-time commitment | The same page, or your terms | The promise you have made to clients, quoted to the minute. |
| Open service desk roles | Your careers page or a public job board | Whether first-line load is currently being absorbed by people who were hired to do something else. |
| Named platform | Your stack, partner or integrations page | Which PSA or ticketing platform you run, and therefore what its automatic triage feature needs from you before it can do anything. |
The inference, stated plainly
A published response commitment is a promise about time. A tier table that names what is sold but not what first line may close is an absence of a rule. Where both are true on the same website, every first-line decision is being made from memory, and the cost of that lands on escalation engineers — which is why the careers page is the third artefact rather than a coincidence.
That is an inference, not a fact about your desk, and it is stated as one. It is also falsifiable: if you have the rules written down and simply do not publish them, the inference is wrong, and the honest thing is for you to say so in a reply. The pack is built to extend what exists rather than to assume nothing does.
What is never used
- No purchased contact data, intent data or enrichment vendor.
- No credential, login or access to any system you run.
- No scraping of anything behind a login, and nothing that is not published for the public to read.
- No tracking pixel in any message, so opening an email tells me nothing.
The free teaser you may have been sent is built from exactly these four artefacts and nothing else. It is given whether or not you ever buy anything, because when there is no call to build trust, proof has to do the work instead. The worked example shows the same method taken all the way to a finished pack.
We turn the service tiers an MSP already publishes into a written first-line triage system — taxonomy, replies, escalation rules — delivered in ten business days without a single call.
Buy the First-Line Triage Pack
From US$1,200 · fixed scope
Fixed scope · Ten business days · No calls, ever