Seagate Technology: Was on hold under ** sec after the first *. Fr...
A Seagate Technology customer review by GetHuman user GetHuman-127022 from November 1st, 2017
Background on GetHuman-127022's case
GetHuman: GetHuman-127022 - can you tell our other Seagate Technology customers when your case took place?
GetHuman-127022: Yeah. It was middle of the night, on October 31st.
GetHuman: Did you reach out to Seagate Technology, and if so, how?
GetHuman: And which of these common Seagate Technology customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-127022 a list of common Seagate Technology problems)
GetHuman-127022: "Returns" was why I was trying to call.
GetHuman-127022's review of Seagate Technology customer service
GetHuman: So how would you sum up your experience for GetHuman's Seagate Technology 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.
GetHuman-127022: Was on hold under ** sec after the first *. Free support only ** days after first registering the drive.
GetHuman: Let's quantify your experience contacting Seagate Technology. On a scale of 1 to 5, how easy is it go get help on a Seagate Technology problem?
GetHuman-127022: 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?
GetHuman-127022: I'd give them a three out of five on communication.
GetHuman: And what about Seagate Technology's ability to quickly and effectively address your problem?
GetHuman-127022: For that I would say two out of five.
GetHuman: And finally- any advice for other Seagate Technology customers?
GetHuman-127022: Call them early in the day or late. Don't forget any personal or account information you might need for Seagate Technology to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-127022 taken from his Seagate Technology customer service problem that occurred on October 31st, 2017.