Xbox: Called on Sunday Feb *th **** at **:**am. Henry...
A Xbox customer review by GetHuman user ~JonG37S from November 20th, 2017
Background on ~JonG37S's case
GetHuman: ~JonG37S - can you tell our other Xbox customers when your case took place?
~JonG37S: Yeah. It was morning, on November 17th.
GetHuman: Did you reach out to Xbox, and if so, how?
GetHuman: And which of these common Xbox customer issues best describes the reason you wanted to talk to them?
(Shows ~JonG37S a list of common Xbox problems)
~JonG37S: "Account access" was why I was trying to call.
~JonG37S's review of Xbox customer service
GetHuman: So how would you sum up your experience for GetHuman's Xbox 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.
~JonG37S: Called on Sunday Feb *th **** at **:**am. Henry answered the phone and all my billing related questions in a very polite and timely manner. Solving several questions and billing issues in a matter of ** mins...*XBOX Live is up and running again! THANKS!*Very satisfied with the prompt professional service of Henry. *I would highly recommend using this number!*Thanks again Henry!*Jonathan C
GetHuman: Let's quantify your experience contacting Xbox. On a scale of 1 to 5, how easy is it go get help on a Xbox problem?
~JonG37S: 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?
~JonG37S: I'd give them a two out of five on communication.
GetHuman: And what about Xbox's ability to quickly and effectively address your problem?
~JonG37S: For that I would say five out of five.
GetHuman: And finally- any advice for other Xbox customers?
~JonG37S: Call them early in the day or late. Don't forget any personal or account information you might need for Xbox to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~JonG37S taken from his Xbox customer service problem that occurred on November 17th, 2017.