Clear: the phone says for english is **.. but when you...
A Clear customer review by GetHuman user ~pollyan from November 22nd, 2017
Background on ~pollyan's case
GetHuman: ~pollyan - can you tell our other Clear customers when your case took place?
~pollyan: Yup. It was morning, on November 19th.
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 ~pollyan a list of common Clear problems)
~pollyan: "Complaint" was why I was trying to call.
~pollyan'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.
~pollyan: the phone says for english is **.. but when you push it it is still spanish as is all the other numbers did it * times..... can't get any reaction from chat....... bad way to get business...........so this has happened a lot ... how in the world do we reach you..... i don't speak spanish it actually says push *... no * and we did... many times and * doesn't help either..
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?
~pollyan: 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?
~pollyan: 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?
~pollyan: For that I would say three out of five.
GetHuman: And finally- any advice for other Clear customers?
~pollyan: 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 ~pollyan taken from his Clear customer service problem that occurred on November 19th, 2017.