Shark Vacuum: I live in Florida and they told me I have to se...
A Shark Vacuum customer review by GetHuman user GetHuman-134380 from November 25th, 2017
Background on GetHuman-134380's case
GetHuman: GetHuman-134380 - can you tell our other Shark Vacuum customers when your case took place?
GetHuman-134380: Yes I can. It was evening, on November 22nd.
GetHuman: Did you reach out to Shark Vacuum, and if so, how?
GetHuman: And which of these common Shark Vacuum customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-134380 a list of common Shark Vacuum problems)
GetHuman-134380: "Technical Support" was why I was trying to call.
GetHuman-134380's review of Shark Vacuum customer service
GetHuman: So how would you sum up your experience for GetHuman's Shark Vacuum 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-134380: I live in Florida and they told me I have to send it to North Carolina. The vacuum is worth $*** and for $** they offer to send me a new one. I ended buying a new one * **.** Shipping
GetHuman: Let's quantify your experience contacting Shark Vacuum. On a scale of 1 to 5, how easy is it go get help on a Shark Vacuum problem?
GetHuman-134380: 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-134380: I'd give them a five out of five on communication.
GetHuman: And what about Shark Vacuum's ability to quickly and effectively address your problem?
GetHuman-134380: For that I would say two out of five.
GetHuman: And finally- any advice for other Shark Vacuum customers?
GetHuman-134380: Call them early in the day or late. Don't forget any personal or account information you might need for Shark Vacuum to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-134380 taken from his Shark Vacuum customer service problem that occurred on November 22nd, 2017.