Too much happened to explain in text. The main reason I am requesting a refund is becau...

GetHuman763542's customer service issue with Greyhound from June 2018

2 views
 | 
615 similar
 | 
0 following
Help with my Greyhound issue
First: share to improve GetHuman763542's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman763542's next move: talk to a Greyhound rep without waiting on hold.
Always use the GetHuman Phone tocall Greyhound. We wait on hold and get a rep on the line for you faster and for free!
Before contacting them, items GetHuman763542 may need:
Name on ticket, Reservation number, Ticket number, Dates of Travel, Confirmation number, Destination, Email address on booking, Billing address, and Billing phone
The issue in GetHuman763542's own words
Too much happened to explain in text. The main reason I am requesting a refund is because our driver abandoned us on the bus at *:**am in the middle of Kansas City. *I am demanding a call back. All passengers on my bus are going to the news media
GetHuman763542 did not yet indicate what Greyhound should do to make this right.
I have an issue with Greyhound too
How GetHuman763542 fixed the problem
We are waiting for GetHuman763542 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
Do you have a customer issue as well?
We can help you get Greyhound's attention and get better help faster. Tap below to get started.
Having Greyhound issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Greyhound email you?
This email address isn't valid
Follow this issue
See how GetHuman763542 fixes it.
This email address isn't valid

Greyhound

Customer service issue
Reported by GetHuman763542
Jun 8th, 2018 - 4 mons ago
I have an issue with Greyhound too
Not resolved
Seen by 2 customers so far
Similar issue to 615 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman763542 started working on this issue
Jun 8th 4:25pm