Toshiba's business practice of ignoring quality...
A Toshiba customer review by GetHuman user ~Noil from November 6th, 2017
Background on ~Noil's case
GetHuman: ~Noil - can you tell our other Toshiba customers when your case took place?
~Noil: Yes. It was morning, on November 4th.
GetHuman: Did you reach out to Toshiba, and if so, how?
GetHuman: And which of these common Toshiba customer issues best describes the reason you wanted to talk to them?
(Shows ~Noil a list of common Toshiba problems)
~Noil: "Technical Support" was why I was trying to call.
~Noil's review of Toshiba customer service
GetHuman: So how would you sum up your experience for GetHuman's Toshiba customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~Noil: Toshiba's business practice of ignoring quality issues is in stark contrast to their current ad campaign. Three week only laptop with a pressure crack from opening the lid * times without force, just normal usage and Toshiba hides behind the general warranty even after admitting there is a quality control issue. They refuse to fix it and wanted more that the cost of the laptop to repair it.
GetHuman: Let's quantify your experience contacting Toshiba. On a scale of 1 to 5, how easy is it go get help on a Toshiba problem?
~Noil: I'd give them a two out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~Noil: I'd give them a one out of five on communication.
GetHuman: And what about Toshiba's ability to quickly and effectively address your problem?
~Noil: For that I would say two out of five.
GetHuman: And finally- any advice for other Toshiba customers?
~Noil: Call them early in the day or late. Don't forget any personal or account information you might need for Toshiba to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Noil taken from his Toshiba customer service problem that occurred on November 4th, 2017.