Fitbit: Called the number, got a human within *mins. C...
A Fitbit customer review by GetHuman user ~SandyR from November 22nd, 2017
Background on ~SandyR's case
GetHuman: ~SandyR - can you tell our other Fitbit customers when your case took place?
~SandyR: Sure. It was evening, on November 12th.
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 ~SandyR a list of common Fitbit problems)
~SandyR: "Repairs" was why I was trying to call.
~SandyR'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.
~SandyR: Called the number, got a human within *mins. Carlos was very helpful and responsive to my problem. Went through some steps and informed me that my Aria Scale wad defective and going to send me a email with information to get the scale to them to check the situation further and if they can't resolve, a new scale will be sent to me. Way to go customer service...that's service!!
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?
~SandyR: I'd give them a five 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?
~SandyR: I'd give them a four out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
~SandyR: For that I would say five out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~SandyR: 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 ~SandyR taken from his Fitbit customer service problem that occurred on November 12th, 2017.