PASS
Observed working
The path held
The test ran and what you publish is what happened. It is dated and kept on the page alongside everything else.
Diagnostic evidence
How we check your calls and contact options
The diagnostic checks your published phone and website paths from outside, dates what it sees, and gives you the finding whether or not you buy anything.
Here are the 8 tests, how a result becomes a finding, and what the diagnostic will not conclude.
What gets tested
8 inbound paths, from two kinds of evidence
Each test says what it can see and what it will not conclude from it.
OBSERVED CALLS · 3 TESTS
One call inside the hours set by a fixed test procedure, from a number that identifies itself as a diagnostic. Never recorded, never repeated to pressure a line, and never posed as a customer.
Observed calls · test 01 of 8
Business-hours call
What it observes
Whether a call placed inside your own published hours is answered, and by what — a person, an attendant or a menu.
It will not say
A call that does not connect is not counted against you until a second, independent path confirms the technical failure.
Observed calls · test 02 of 8
After-hours call
What it observes
Whether a call placed outside those hours reaches the path you publish for it.
It will not say
Being closed after hours is not a fault. This only becomes a finding where what is published and what happens disagree.
Observed calls · test 03 of 8
Missed-call follow-up
What it observes
Whether an unanswered call is followed up — by call, text or email — inside the window your own hours imply.
It will not say
The follow-up is observed on the number that placed the call. Nothing is inferred from silence elsewhere.
PUBLISHED SURFACES · 5 TESTS
Your own site and listings, fetched the way a visitor would on a desktop and on a phone. Read only: nothing is submitted, nothing is booked, nothing is bought.
Published surfaces · test 04 of 8
Booking path
What it observes
Whether a booking or service-request path exists and resolves, at desktop width and at phone width.
It will not say
The path is established, never traversed. A menu that has to be opened before a path appears is recorded as unknown, not as broken.
Published surfaces · test 05 of 8
Repair and replacement routing
What it observes
Whether repair and replacement have distinct published paths, or share one intake.
It will not say
One intake path is an observation, not a fault. Public evidence alone can never establish a routing failure.
Published surfaces · test 06 of 8
Urgent path
What it observes
Whether an urgent path is published, and whether it is clear enough to follow.
It will not say
Absence of a published urgent path is read against what you claim, not against what we would supply.
Published surfaces · test 07 of 8
Contact friction
What it observes
How many steps stand between a visitor landing and a way to reach you.
It will not say
Friction is a weak signal and is treated as one. It never founds a finding on its own.
Published surfaces · test 08 of 8
Published claims
What it observes
Whether the claims you publish about hours, urgency and response agree with each other.
It will not say
A contradiction needs both sides quoted and a stated reason. One ambiguous sentence is ambiguous, not contradictory.
How observations become findings
Three beats, and a stop
Nothing is weighed by hand. The same steps run for every business we check, and they stop where the evidence stops.
-
Observe
A call placed once inside the hours set by a fixed test procedure, or a page fetched the way any visitor would fetch it. Every observation is stamped with the moment it happened, and that stamp is what you see on the finding.
-
Classify
Each observation resolves to one state by the written rule for that test. No human impression is added, no result is edited afterwards, and where the rule does not reach, the state is unknown.
-
Corroborate
A call the engine cannot attribute to your own handling — a carrier fault, a degraded line, a screened number — cannot found a finding, and cannot be the only thing a finding rests on.
How to read your results
Four states, and one of them is not a verdict
Every test resolves to one of these. They are the same four words on your finding, in the same colours, with the same glyphs, whichever test produced them.
PARTIAL
Requires attention
The path held partly
It exists but did not hold as published. Partial is not a softened failure and not a near miss; it is its own observation.
FAIL
Observed failure
The path did not hold
It failed, and the engine can attribute what happened to your own handling. This is the only state that can support a finding.
UNKNOWN
Not tested · not evidence of failure
The test did not reach an answer
A screened number, a degraded line, a menu that has to be opened first. Unknown is never counted, coloured or sold as a failure.
OBSERVED
Not a fifth state. Where a test finds something HVAC Uptime would supply and you have not, that is an observation, not a fault — one intake path for repair and replacement, or being closed after hours with no claim to the contrary. It takes the same muted styling as unknown, with its own words: Tested · nothing adverse observed. It is never adverse and never counts toward a finding.
What we do not infer
What our check can and cannot tell you
These are the conclusions the diagnostic will not draw about your business.
-
Unknown is not failure
An outcome we cannot attribute to your own handling is recorded as unknown. It is never styled, counted or sold as a failure, and it never makes you a better prospect.
-
A gap we would fill is not a fault
The absence of something HVAC Uptime would supply is not evidence that you are failing. Those show as neutral observations, and they carry no weight either way.
-
Nothing is submitted
The diagnostic establishes that a path exists and resolves. It never fills a form, never completes a booking and never poses as a customer. A test call is short and bounded by the fixed procedure: a set number of calls, a capped ring time, and a hang-up on voicemail without leaving a message.
-
No call is ever recorded
Calls are not recorded, transcribed or kept as audio. What survives is the outcome, the timestamp and the reason code — the same things printed on your evidence page.
-
No number we did not observe
No estimated leakage, no industry benchmark, no projected response time, no modelled close rate. If we did not observe it, it is not on the page.
-
No score
You get a dated finding with the evidence behind it, not a grade out of ten. A number would be easier to sell and impossible to check.
A worked example
What the finding actually looks like
Below is the evidence behind one result on the sample diagnostic, exactly as it renders on the page a prospect receives. Two observations, both dated, on two different days.
FAIL
Missed-call follow-up
- 15 Sep 2026, 18:40 ET No follow-up to the missed call inside the window — No call back, text or email inside the recovery window
- 18 Sep 2026, 18:12 ET No follow-up to the missed call inside the window — Second observation, a different number, same window
Illustrative sample. Built by running the engine against invented inputs, not a customer outcome.
What a finding leads to
Six things we put in place
A diagnostic points to the one its evidence supports, and that is the example we show you. Core includes the functions listed on the Pricing page.
Missed-call follow-up
A call nobody could take gets a follow-up inside a written response time, and the follow-up is recorded with the rest of the call.
After-hours handling
Calls outside business hours follow a written path, so what is published and what happens are the same thing.
Booking path
A booking path that stays reachable on a desktop and on a phone.
Emergency routing
An urgent call follows a defined path to the person who handles it, instead of the general queue.
Repair and estimate routing
Repair and replacement go to the people who handle each, so an estimate request does not wait behind a service call.
Everything under one setup
Call answering, missed-call follow-up, routing and booking under one written setup, with what happened recorded against it.
What to do now
Ready for HVAC Uptime?
Request setup. If we sent you a diagnostic, include its reference.
Or start with the free review campaign. A finding, if you have one, is yours either way.