TSP Travel: First time I called got on the audio loop...NO...
A TSP Travel customer review by GetHuman user GetHuman-264890 from November 12th, 2017
Background on GetHuman-264890's case
GetHuman: GetHuman-264890 - can you tell our other TSP Travel customers when your case took place?
GetHuman-264890: Yes I can. It was morning, on November 6th.
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 GetHuman-264890 a list of common TSP Travel problems)
GetHuman-264890: "Change booking" was why I was trying to call.
GetHuman-264890'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.
GetHuman-264890: First time I called got on the audio loop...NO HELP. Read this advise about pushing * and the **********. A real person come on immediately and answered my question quickly. How sad you have to use this type of gimick.
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?
GetHuman-264890: I'd give them a four 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?
GetHuman-264890: 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?
GetHuman-264890: For that I would say five out of five.
GetHuman: And finally- any advice for other TSP Travel customers?
GetHuman-264890: 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 GetHuman-264890 taken from his TSP Travel customer service problem that occurred on November 6th, 2017.