Motorola: BE PERSISTENT! I got disconnected * times, aft...
A Motorola customer review by GetHuman user ~jason from November 25th, 2017
Background on ~jason's case
GetHuman: ~jason - can you tell our other Motorola customers when your case took place?
~jason: Yeah. It was afternoon, on November 19th.
GetHuman: Did you reach out to Motorola, and if so, how?
GetHuman: And which of these common Motorola customer issues best describes the reason you wanted to talk to them?
(Shows ~jason a list of common Motorola problems)
~jason: "Replacement Part" was why I was trying to call.
~jason's review of Motorola customer service
GetHuman: So how would you sum up your experience for GetHuman's Motorola 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.
~jason: BE PERSISTENT! I got disconnected * times, after holding *-* minutes each time. The *th time, I got a person in about * minutes. That's pretty good, even counting all * calls, but GLAD I did not give up. IRONICALLY, This call-you-back, no holding thing, DID NOT WORK. It failed * time also, so I decided to call myself.*No hard feelings, GetHuman.
GetHuman: Let's quantify your experience contacting Motorola. On a scale of 1 to 5, how easy is it go get help on a Motorola problem?
~jason: 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?
~jason: I'd give them a five out of five on communication.
GetHuman: And what about Motorola's ability to quickly and effectively address your problem?
~jason: For that I would say five out of five.
GetHuman: And finally- any advice for other Motorola customers?
~jason: Call them early in the day or late. Don't forget any personal or account information you might need for Motorola to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jason taken from his Motorola customer service problem that occurred on November 19th, 2017.