When I was filling out the order for the tickets Kansas City Royals versus Chicago Whit...

GetHuman6069522's customer service issue with SeatGeek from May 2021

2 views | 739 similar | 0 following
Help with my SeatGeek issue
First: share to improve GetHuman6069522's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman6069522's next move: find and follow the right step-by-step guide.
SeatGeek doesn't have a customer phone number that is answered by an agent. Instead, GetHuman6069522 will need to dig through the advice provided by SeatGeek, other customers and consumer advocacy websites like GetHuman. Here are some instructions we've written for similar issues- hopefully GetHuman6069522 can let us know if they help or not.
If you don't see a guide here that matches the problem you are having, please see if SeatGeek has better answers for you: SeatGeek Help Center
Before contacting them, items GetHuman6069522 may need:
Username, Password, and Email address on the account
The issue in GetHuman6069522's own words
When I was filling out the order for the tickets Kansas City Royals versus Chicago White Sox I accidentally entered a wrong email address and I cannot get access to the tickets

GetHuman6069522 did not yet indicate what SeatGeek should do to make this right.

How GetHuman6069522 fixed the problem

We are waiting for GetHuman6069522 to fix the problem and share the solution with the rest of us customers.

Do you have a customer issue as well?
We can help you get SeatGeek's attention and get better help faster. Tap below to get started.
Having SeatGeek issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid
Follow this issue
See how GetHuman6069522 fixes it.
This email address isn't valid


Customer service issue
Reported by GetHuman6069522
May 14th, 2021 - a month ago
Not resolved
Seen by 2 customers so far
Similar issue to 739 others
0 customers following this


GetHuman6069522 started working on this issue
May 14th 6:20pm