Continental One Pass: After waiting for ** minutes for an answer rega...
A Continental One Pass customer review by GetHuman user ~ssmerc from November 14th, 2017
Background on ~ssmerc's case
GetHuman: ~ssmerc - can you tell our other Continental One Pass customers when your case took place?
~ssmerc: Yes. It was middle of the night, on November 8th.
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 ~ssmerc a list of common Continental One Pass problems)
~ssmerc: "Cancel flight" was why I was trying to call.
~ssmerc'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.
~ssmerc: After waiting for ** minutes for an answer regarding baggage I was disconnected. When I called back I was transfered and waited over ** minutes and hung up very frustrated.
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?
~ssmerc: I'd give them a four 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?
~ssmerc: 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?
~ssmerc: For that I would say four out of five.
GetHuman: And finally- any advice for other Continental One Pass customers?
~ssmerc: 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 ~ssmerc taken from his Continental One Pass customer service problem that occurred on November 8th, 2017.