Royal Jordanian Airlines: worst trip ever. never traveling with RJ again...
A Royal Jordanian Airlines customer review by GetHuman user ~uskyblu from November 24th, 2017
Background on ~uskyblu's case
GetHuman: ~uskyblu - can you tell our other Royal Jordanian Airlines customers when your case took place?
~uskyblu: Yes. It was evening, on November 16th.
GetHuman: Did you reach out to Royal Jordanian Airlines, and if so, how?
GetHuman: And which of these common Royal Jordanian Airlines customer issues best describes the reason you wanted to talk to them?
(Shows ~uskyblu a list of common Royal Jordanian Airlines problems)
~uskyblu: "Frequent flyer program" was why I was trying to call.
~uskyblu's review of Royal Jordanian Airlines customer service
GetHuman: So how would you sum up your experience for GetHuman's Royal Jordanian Airlines 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.
~uskyblu: worst trip ever. never traveling with RJ again. The ** hours trip turned into a * days trip.Horrible
GetHuman: Let's quantify your experience contacting Royal Jordanian Airlines. On a scale of 1 to 5, how easy is it go get help on a Royal Jordanian Airlines problem?
~uskyblu: I'd give them a one 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?
~uskyblu: I'd give them a one out of five on communication.
GetHuman: And what about Royal Jordanian Airlines's ability to quickly and effectively address your problem?
~uskyblu: For that I would say one out of five.
GetHuman: And finally- any advice for other Royal Jordanian Airlines customers?
~uskyblu: Call them early in the day or late. Don't forget any personal or account information you might need for Royal Jordanian Airlines to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~uskyblu taken from his Royal Jordanian Airlines customer service problem that occurred on November 16th, 2017.