They answered at 3 AM, but gave wrong information

It is my humble opinion that perhaps I should share a recent experience with Vultr support, though I apologize in advance if this observation is unwelcome.

At 2:47 AM local time on November 18, I submitted a ticket regarding a failed RAID rebuild on a HostHatch dedicated server. To my surprise, I received a response at 3:12 AM — a response time of twenty-five minutes, which is commendable. However, the technician instructed me to run `mdadm --create` with the `--force` flag, which would have destroyed the existing array metadata and rendered recovery impossible. It is my humble opinion that perhaps this individual was not fully trained in RAID recovery procedures.

I do not wish to seem ungrateful. Twenty-four-hour coverage is a blessing. Yet I find myself uncertain whether speed without accuracy is preferable to a delayed but correct answer. Let us discuss this balance, if you would be so kind.

The support fast but the information bad! It is problem of the coverage 24h no? The technician of night maybe is student new, not engineer senior. In my company we have team tier1 and team tier2, the tier1 answer fast and close! But tier2 has knowledge real. You prefer answer slow but correct, or fast but wrong? I think money for training is solution no? The server network needs expert not apprentice at 3am!