Fitbit: I had to call * times to resolve the issue. I s...
A Fitbit customer review by GetHuman user ~ANGEL from November 27th, 2017
Background on ~ANGEL's case
GetHuman: ~ANGEL - can you tell our other Fitbit customers when your case took place?
~ANGEL: Sure. It was middle of the night, on November 20th.
GetHuman: Did you reach out to Fitbit, and if so, how?
GetHuman: And which of these common Fitbit customer issues best describes the reason you wanted to talk to them?
(Shows ~ANGEL a list of common Fitbit problems)
~ANGEL: "Where to buy" was why I was trying to call.
~ANGEL's review of Fitbit customer service
GetHuman: So how would you sum up your experience for GetHuman's Fitbit 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.
~ANGEL: I had to call * times to resolve the issue. I sent the requested info in my email. After * days on no contact from them, I called them. They then tried to tell me that I purchased my fitbit in ****. I pointed out to them that the receipt was copied and pasted on the email I sent them clearly showing a purchase date of **********. They then replaced the entire package.
GetHuman: Let's quantify your experience contacting Fitbit. On a scale of 1 to 5, how easy is it go get help on a Fitbit problem?
~ANGEL: I'd give them a four 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?
~ANGEL: I'd give them a three out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
~ANGEL: For that I would say two out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~ANGEL: Call them early in the day or late. Don't forget any personal or account information you might need for Fitbit to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ANGEL taken from his Fitbit customer service problem that occurred on November 20th, 2017.