Greyhound: The agent understood my concerns, and gave me g...
Una recensione del cliente Greyhound da parte dell'utente GetHuman ~ehart20 da novembre 20º, 2017
Background on ~ehart20's case
GetHuman: ~ehart20 - can you tell our other Greyhound customers when your case took place?
~ehart20: Yup. It was middle of the night, on novembre 13º.
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 ~ehart20 a list of common Greyhound problems)
~ehart20: "Loyalty program" was why I was trying to call.
~ehart20'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.
~ehart20: The agent understood my concerns, and gave me good, clear answers. He ensured me that the Milwaukee, WI, and Kenosha terminals would be contacted in regard to not answering their phone on many tries. I had to do a search on "working Greyhound phone number" to get this done.
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?
~ehart20: 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?
~ehart20: I'd give them a one out of five on communication.
GetHuman: And what about Greyhound's ability to quickly and effectively address your problem?
~ehart20: For that I would say two out of five.
GetHuman: And finally- any advice for other Greyhound customers?
~ehart20: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Greyhound sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~ehart20 taken from his Greyhound customer service problem that occurred on novembre 13º, 2017.