Megabus: We waited an hour to get on the bus to New York...
A Megabus customer review by GetHuman user ~Anonymous from November 18th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Megabus customers when your case took place?
~Anonymous: Yes. It was morning, on November 13th.
GetHuman: Did you reach out to Megabus, and if so, how?
GetHuman: And which of these common Megabus customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Megabus problems)
~Anonymous: "Cancel booking" was why I was trying to call.
~Anonymous's review of Megabus customer service
GetHuman: So how would you sum up your experience for GetHuman's Megabus 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.
~Anonymous: We waited an hour to get on the bus to New York City. Once on the bus it was jam packed so my whole family had to split up with a lady laid across the backseat not told to move. The next bus was on time and we left about the same time as them,so we could have taken that bus. All in all,this has put us behind schedule.
GetHuman: Let's quantify your experience contacting Megabus. On a scale of 1 to 5, how easy is it go get help on a Megabus problem?
~Anonymous: 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?
~Anonymous: I'd give them a two out of five on communication.
GetHuman: And what about Megabus's ability to quickly and effectively address your problem?
~Anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other Megabus customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Megabus to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Megabus customer service problem that occurred on November 13th, 2017.