I received a receipt from TSP Travel that was...
A TSP Travel customer review by GetHuman user ~jango from November 22nd, 2017
Background on ~jango's case
GetHuman: ~jango - can you tell our other TSP Travel customers when your case took place?
~jango: Yeah. It was middle of the night, on November 13th.
GetHuman: Did you reach out to TSP Travel, and if so, how?
GetHuman: And which of these common TSP Travel customer issues best describes the reason you wanted to talk to them?
(Shows ~jango a list of common TSP Travel problems)
~jango: "Cancel booking" was why I was trying to call.
~jango's review of TSP Travel customer service
GetHuman: So how would you sum up your experience for GetHuman's TSP Travel 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.
~jango: I received a receipt from TSP Travel that was $*** less than what they charged my credit card. When I pointed this out, their solution was to send me a receipt with the higher amount! When I pointed out that what was in order was a refund, I get the runaround about how this will all be fixed with a new receipt! Learned my lesson! Never again!
GetHuman: Let's quantify your experience contacting TSP Travel. On a scale of 1 to 5, how easy is it go get help on a TSP Travel problem?
~jango: I'd give them a five 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?
~jango: I'd give them a five out of five on communication.
GetHuman: And what about TSP Travel's ability to quickly and effectively address your problem?
~jango: For that I would say five out of five.
GetHuman: And finally- any advice for other TSP Travel customers?
~jango: Call them early in the day or late. Don't forget any personal or account information you might need for TSP Travel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jango taken from his TSP Travel customer service problem that occurred on November 13th, 2017.