O2gearshop.com: It took a bit, but the solution was fairly simp...
A O2gearshop.com customer review by GetHuman user ~nightops from November 14th, 2017
Background on ~nightops's case
GetHuman: ~nightops - can you tell our other O2gearshop.com customers when your case took place?
~nightops: Yup. It was late at night, on November 10th.
GetHuman: Did you reach out to O2gearshop.com, and if so, how?
GetHuman: And which of these common O2gearshop.com customer issues best describes the reason you wanted to talk to them?
(Shows ~nightops a list of common O2gearshop.com problems)
~nightops: "Track order" was why I was trying to call.
~nightops's review of O2gearshop.com customer service
GetHuman: So how would you sum up your experience for GetHuman's O2gearshop.com 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.
~nightops: It took a bit, but the solution was fairly simple. I use GMail and it automatically marked o*gearshop emails as SPAM...should've checked that first. I did find that my order was confirmed, and Camden (sp?) cleared everything up quickly.
GetHuman: Let's quantify your experience contacting O2gearshop.com. On a scale of 1 to 5, how easy is it go get help on a O2gearshop.com problem?
~nightops: 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?
~nightops: I'd give them a two out of five on communication.
GetHuman: And what about O2gearshop.com's ability to quickly and effectively address your problem?
~nightops: For that I would say five out of five.
GetHuman: And finally- any advice for other O2gearshop.com customers?
~nightops: Call them early in the day or late. Don't forget any personal or account information you might need for O2gearshop.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~nightops taken from his O2gearshop.com customer service problem that occurred on November 10th, 2017.