Rogers Wireless: waiting for my phone to be delivered
A Rogers Wireless customer review by GetHuman user GetHuman41765 from December 7th, 2017
Background on GetHuman41765's case
GetHuman: GetHuman41765 - can you tell our other Rogers Wireless customers when your case took place?
GetHuman41765: Sure. It was morning, on November 27th.
GetHuman: Did you reach out to Rogers Wireless, and if so, how?
GetHuman: And which of these common Rogers Wireless customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman41765 a list of common Rogers Wireless problems)
GetHuman41765: "Cancel service" was why I was trying to call.
GetHuman41765's review of Rogers Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Rogers Wireless 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.
GetHuman41765: waiting for my phone to be delivered
GetHuman: Can you tell the rest of us a bit more from what happened on 11/27/17?
GetHuman41765: it was ordered Monday and they said it would be here yesterday
GetHuman: Let's quantify your experience contacting Rogers Wireless. On a scale of 1 to 5, how easy is it go get help on a Rogers Wireless problem?
GetHuman41765: 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?
GetHuman41765: I'd give them a five out of five on communication.
GetHuman: And what about Rogers Wireless's ability to quickly and effectively address your problem?
GetHuman41765: For that I would say five out of five.
GetHuman: And finally- any advice for other Rogers Wireless customers?
GetHuman41765: Call them early in the day or late. Don't forget any personal or account information you might need for Rogers Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman41765 taken from his Rogers Wireless customer service problem that occurred on November 27th, 2017.