I have made a booking with the wrong email (.con instead of .com). I know which email I...

GetHuman817412's customer service issue with The Trainline from June 2018

2 views
 | 
72 similar
 | 
0 following
Help with my The Trainline issue
First: share to improve GetHuman817412's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman817412's next move: call The Trainline.
The best way to get your problem resolved is to tap the button below to start calling The Trainline. We will check on you later to see if it's fixed or needs to be escalated.
Before contacting them, items GetHuman817412 may need:
Who made the booking, Booking reference, Billing address, Email address on the account, and Loyalty program number (if applicable)
The issue in GetHuman817412's own words
I have made a booking with the wrong email (.con instead of .com). I know which email I used and also have my booking reference number and the card that I paid with. I would like to change the email to my own.
GetHuman817412 did not yet indicate what The Trainline should do to make this right.
I have an issue with The Trainline too
How GetHuman817412 fixed the problem
We are waiting for GetHuman817412 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 The Trainline's attention and get better help faster. Tap below to get started.
Having The Trainline issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would The Trainline email you?
This email address isn't valid
Follow this issue
See how GetHuman817412 fixes it.
This email address isn't valid

The Trainline

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