Toshiba: Called C*S * replacement cord * TV. Was transf...
A Toshiba customer review by GetHuman user ~greenerday from November 27th, 2017
Background on ~greenerday's case
GetHuman: ~greenerday - can you tell our other Toshiba customers when your case took place?
~greenerday: Sure. It was middle of the night, on November 25th.
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 ~greenerday a list of common Toshiba problems)
~greenerday: "Account Access" was why I was trying to call.
~greenerday'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.
~greenerday: Called C*S * replacement cord * TV. Was transferred ***x's and ended up back where I started at C*S. PAZ C*S rep. transferred me back to sales. Who told me to call another *. Was told no parts available. That sucked.*I spent ** min. in transfers and additional ** min. waiting for sales to pick up.
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?
~greenerday: 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?
~greenerday: I'd give them a five out of five on communication.
GetHuman: And what about Toshiba's ability to quickly and effectively address your problem?
~greenerday: For that I would say two out of five.
GetHuman: And finally- any advice for other Toshiba customers?
~greenerday: 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 ~greenerday taken from his Toshiba customer service problem that occurred on November 25th, 2017.