ViaGoGo: Not responding to e mails grave concerns about...
A ViaGoGo customer review by GetHuman user GetHuman53915 from December 8th, 2017
Background on GetHuman53915's case
GetHuman: GetHuman53915 - can you tell our other ViaGoGo customers when your case took place?
GetHuman53915: Yes I can. It was afternoon, on December 4th.
GetHuman: Did you reach out to ViaGoGo, and if so, how?
GetHuman: And which of these common ViaGoGo customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman53915 a list of common ViaGoGo problems)
GetHuman53915: "Trouble Selling Tickets" was why I was trying to contact.
GetHuman53915's review of ViaGoGo customer service
GetHuman: So how would you sum up your experience for GetHuman's ViaGoGo 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.
GetHuman53915: Not responding to e mails grave concerns about whether tickets are valid
GetHuman: Can you tell the rest of us a bit more from what happened on 12/04/17?
GetHuman53915: Sent * emails reviews are dreadful about this company none existence customer service
GetHuman: Let's quantify your experience contacting ViaGoGo. On a scale of 1 to 5, how easy is it go get help on a ViaGoGo problem?
GetHuman53915: 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?
GetHuman53915: I'd give them a three out of five on communication.
GetHuman: And what about ViaGoGo's ability to quickly and effectively address your problem?
GetHuman53915: For that I would say two out of five.
GetHuman: And finally- any advice for other ViaGoGo customers?
GetHuman53915: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for ViaGoGo to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman53915 taken from his ViaGoGo customer service problem that occurred on December 4th, 2017.