Clear: After * calls routed to overseas I called the c...
A Clear customer review by GetHuman user GetHuman-202676 from November 10th, 2017
Background on GetHuman-202676's case
GetHuman: GetHuman-202676 - can you tell our other Clear customers when your case took place?
GetHuman-202676: Sure. It was late at night, on November 3rd.
GetHuman: Did you reach out to Clear, and if so, how?
GetHuman: And which of these common Clear customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-202676 a list of common Clear problems)
GetHuman-202676: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-202676's review of Clear customer service
GetHuman: So how would you sum up your experience for GetHuman's Clear 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.
GetHuman-202676: After * calls routed to overseas I called the corporate office and got their CS. In * min GE determined my modem was bad and is overnighting a replacement. There never was a tower down or maintenance going on. Call corporate for the best service. Customer care * is a joke.
GetHuman: Let's quantify your experience contacting Clear. On a scale of 1 to 5, how easy is it go get help on a Clear problem?
GetHuman-202676: 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?
GetHuman-202676: I'd give them a one out of five on communication.
GetHuman: And what about Clear's ability to quickly and effectively address your problem?
GetHuman-202676: For that I would say two out of five.
GetHuman: And finally- any advice for other Clear customers?
GetHuman-202676: Call them early in the day or late. Don't forget any personal or account information you might need for Clear to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-202676 taken from his Clear customer service problem that occurred on November 3rd, 2017.