Fitbit: I was on hold to find out about returning a pro...
A Fitbit customer review by GetHuman user ~bitter from November 25th, 2017
Background on ~bitter's case
GetHuman: ~bitter - can you tell our other Fitbit customers when your case took place?
~bitter: Yup. It was middle of the night, on November 23rd.
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 ~bitter a list of common Fitbit problems)
~bitter: "Warranty claim" was why I was trying to call.
~bitter'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.
~bitter: I was on hold to find out about returning a product******€*Fitbit requires a "RMA" number for processing. I waited ** minutes for someone to answer. She couldn't generate a RMA and put me on hold. I was on hold for another ** minutes. The guy who then answered was nice, but that was ** minutes after I placed my call. Fitibit clearly doesn't care about customer 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?
~bitter: 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?
~bitter: I'd give them a five out of five on communication.
GetHuman: And what about Fitbit's ability to quickly and effectively address your problem?
~bitter: For that I would say five out of five.
GetHuman: And finally- any advice for other Fitbit customers?
~bitter: 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 ~bitter taken from his Fitbit customer service problem that occurred on November 23rd, 2017.