Greyhound: I purchased a ticket for my Son and ** month ol...
A Greyhound customer review by GetHuman user ~Carolyn from November 2nd, 2017
Background on ~Carolyn's case
GetHuman: ~Carolyn - can you tell our other Greyhound customers when your case took place?
~Carolyn: Yup. It was evening, on October 27th.
GetHuman: Did you reach out to Greyhound, and if so, how?
GetHuman: And which of these common Greyhound customer issues best describes the reason you wanted to talk to them?
(Shows ~Carolyn a list of common Greyhound problems)
~Carolyn: "Insurance claim" was why I was trying to call.
~Carolyn's review of Greyhound customer service
GetHuman: So how would you sum up your experience for GetHuman's Greyhound 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.
~Carolyn: I purchased a ticket for my Son and ** month old grandaughter round trip from Detroit MI to Punxy Pa. It was a horrible trip. The attendents were very rude in Pittsburgh Pa. His name is Rick ********.The drink attendent was very rude and refused to give them their drink. We will never travel Greyhound again. Disgusting.
GetHuman: Let's quantify your experience contacting Greyhound. On a scale of 1 to 5, how easy is it go get help on a Greyhound problem?
~Carolyn: 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?
~Carolyn: I'd give them a two out of five on communication.
GetHuman: And what about Greyhound's ability to quickly and effectively address your problem?
~Carolyn: For that I would say three out of five.
GetHuman: And finally- any advice for other Greyhound customers?
~Carolyn: Call them early in the day or late. Don't forget any personal or account information you might need for Greyhound to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Carolyn taken from his Greyhound customer service problem that occurred on October 27th, 2017.