Star Wars: The Old Republic: I think the service is quite okay, now i just h...
A Star Wars: The Old Republic customer review by GetHuman user ~Luke from November 22nd, 2017
Background on ~Luke's case
GetHuman: ~Luke - can you tell our other Star Wars: The Old Republic customers when your case took place?
~Luke: Yup. It was afternoon, on November 15th.
GetHuman: Did you reach out to Star Wars: The Old Republic, and if so, how?
GetHuman: And which of these common Star Wars: The Old Republic customer issues best describes the reason you wanted to talk to them?
(Shows ~Luke a list of common Star Wars: The Old Republic problems)
~Luke: "Cancel order" was why I was trying to call.
~Luke's review of Star Wars: The Old Republic customer service
GetHuman: So how would you sum up your experience for GetHuman's Star Wars: The Old Republic 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.
~Luke: I think the service is quite okay, now i just have to wait for ** hours to get my problem is solve or not.
GetHuman: Let's quantify your experience contacting Star Wars: The Old Republic. On a scale of 1 to 5, how easy is it go get help on a Star Wars: The Old Republic problem?
~Luke: I'd give them a four 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?
~Luke: I'd give them a five out of five on communication.
GetHuman: And what about Star Wars: The Old Republic's ability to quickly and effectively address your problem?
~Luke: For that I would say four out of five.
GetHuman: And finally- any advice for other Star Wars: The Old Republic customers?
~Luke: Call them early in the day or late. Don't forget any personal or account information you might need for Star Wars: The Old Republic to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Luke taken from his Star Wars: The Old Republic customer service problem that occurred on November 15th, 2017.