Continental One Pass: Awesome! It took me about ten times longer to s...
A Continental One Pass customer review by GetHuman user ~dena from November 5th, 2017
Background on ~dena's case
GetHuman: ~dena - can you tell our other Continental One Pass customers when your case took place?
~dena: Yes. It was morning, on November 1st.
GetHuman: Did you reach out to Continental One Pass, and if so, how?
GetHuman: And which of these common Continental One Pass customer issues best describes the reason you wanted to talk to them?
(Shows ~dena a list of common Continental One Pass problems)
~dena: "Make a booking" was why I was trying to call.
~dena's review of Continental One Pass customer service
GetHuman: So how would you sum up your experience for GetHuman's Continental One Pass 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.
~dena: Awesome! It took me about ten times longer to search in vain on the company website for a phone number than it did to get through to a person using gethuman. This is the best new tool I've found in ages!
GetHuman: Let's quantify your experience contacting Continental One Pass. On a scale of 1 to 5, how easy is it go get help on a Continental One Pass problem?
~dena: 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?
~dena: I'd give them a five out of five on communication.
GetHuman: And what about Continental One Pass's ability to quickly and effectively address your problem?
~dena: For that I would say two out of five.
GetHuman: And finally- any advice for other Continental One Pass customers?
~dena: Call them early in the day or late. Don't forget any personal or account information you might need for Continental One Pass to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~dena taken from his Continental One Pass customer service problem that occurred on November 1st, 2017.