Support

The dimension monitoring cannot see, and the one people change providers over.

Support is scored by reviewers and by nobody else. There is no measurement of it anywhere on this platform, and there is unlikely ever to be: what happens inside a ticket queue is not visible from the outside.

What reviewers are asked about

• How quickly a first response arrived.
• Whether the answer resolved the problem or restated the question.
• Whether the person answering understood the system they were supporting.
• What happened when something went genuinely wrong, as opposed to routine requests.
• Availability: hours, channels, and whether out-of-hours means anything.

Why it is worth reading carefully

Support is the dimension with the widest gap between the median experience and the experience that matters. Most tickets are routine and most providers handle them adequately; the score people remember comes from the one incident where it mattered.

It is also the dimension most affected by when the review was written. Support quality changes with staffing in a way hardware performance does not, so a two-year-old support score is a much weaker signal than a two-year-old performance score. Review dates are shown for this reason.

What a low support score does not tell you

It does not distinguish "slow" from "unhelpful", which are different problems with different consequences. A provider that answers in four hours with a real fix may score below one that answers in ten minutes with a template. The written reviews are where that distinction lives, which is why the scores are shown next to the reviews rather than instead of them.

Providers replying

A provider can reply to a review publicly. A reply is not a review: it does not affect the score, the review count or any monthly figure. It is there so a provider can give its side, and readers can see both.