My FitBit bit the dust after a year and a half...
A Fitbit customer review by GetHuman user ~Whitfield2000 from November 28th, 2017
Background on ~Whitfield2000's case
GetHuman: ~Whitfield2000 - can you tell our other Fitbit customers when your case took place?
~Whitfield2000: Yup. It was evening, on November 19th.
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 ~Whitfield2000 a list of common Fitbit problems)
~Whitfield2000: "Where to buy" was why I was trying to call.
~Whitfield2000'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.
~Whitfield2000: My FitBit bit the dust after a year and a half (charging issues that I've nursed along). Called customer care to see if I'd missed anything and WHAAAAT?: they're overnighting me a new one! Insanely FANTASTIC customer care at FitBit. If you're considering a fitness tracker, you'll be in good hands.
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?
~Whitfield2000: I'd give them a three 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?
~Whitfield2000: I'd give them a two out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
~Whitfield2000: For that I would say five out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~Whitfield2000: 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 ~Whitfield2000 taken from his Fitbit customer service problem that occurred on November 19th, 2017.