iTunes: I was shocked at how nice & helpful they were...
A iTunes customer review by GetHuman user ~Foulo from November 20th, 2017
Background on ~Foulo's case
GetHuman: ~Foulo - can you tell our other iTunes customers when your case took place?
~Foulo: Yup. It was middle of the night, on November 10th.
GetHuman: Did you reach out to iTunes, and if so, how?
GetHuman: And which of these common iTunes customer issues best describes the reason you wanted to talk to them?
(Shows ~Foulo a list of common iTunes problems)
~Foulo: "Dispute a Charge" was why I was trying to call.
~Foulo's review of iTunes customer service
GetHuman: So how would you sum up your experience for GetHuman's iTunes 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.
~Foulo: I was shocked at how nice & helpful they were. Initially I spoke with someone in India. Which I must say frustrated me bc they didn't seem to understand my question. Then she said she was going to transfer me. I though okay here we go.... Well I was wrong:). Not even a min later I spoke with a wonderful American who stayed on the phone until my issue was completely resolved.
GetHuman: Let's quantify your experience contacting iTunes. On a scale of 1 to 5, how easy is it go get help on a iTunes problem?
~Foulo: I'd give them a two 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?
~Foulo: I'd give them a three out of five on communication.
GetHuman: And what about iTunes's ability to quickly and effectively address your problem?
~Foulo: For that I would say five out of five.
GetHuman: And finally- any advice for other iTunes customers?
~Foulo: Call them early in the day or late. Don't forget any personal or account information you might need for iTunes to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Foulo taken from his iTunes customer service problem that occurred on November 10th, 2017.