eBay: Waited on hold for ** minutes until I had to gi...
Eine eBay Kundenbewertung durch GetHuman-Benutzer ~Anonymous von November 26., 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other eBay customers when your case took place?
~Anonymous: Yes I can. It was middle of the night, on November 20..
GetHuman: Did you reach out to eBay, and if so, how?
GetHuman: And which of these common eBay customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common eBay problems)
~Anonymous: "Refund" was why I was trying to call.
~Anonymous's review of eBay customer service
GetHuman: So how would you sum up your experience for GetHuman's eBay 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.
~Anonymous: Waited on hold for ** minutes until I had to give up. Trying gain now. Was told my wait time should be * minutes. It's now been ** minutes and still waiting with a computer voice telling me repeatedly that a representative will get to me shortly. What a lie. Guess that gives me time to finish this review about them.
GetHuman: Let's quantify your experience contacting eBay. On a scale of 1 to 5, how easy is it go get help on a eBay problem?
~Anonymous: I'd give them a three 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?
~Anonymous: I'd give them a four out of five on communication.
GetHuman: And what about eBay's ability to quickly and effectively address your problem?
~Anonymous: For that I would say three out of five.
GetHuman: And finally- any advice for other eBay customers?
~Anonymous: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit eBay weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his eBay customer service problem that occurred on November 20., 2017.