Shaw Communications: Even after waiting over * hour, no common court...
A Shaw Communications customer review by GetHuman user ~Shawsucks from November 10th, 2017
Background on ~Shawsucks's case
GetHuman: ~Shawsucks - can you tell our other Shaw Communications customers when your case took place?
~Shawsucks: Yeah. It was afternoon, on November 1st.
GetHuman: Did you reach out to Shaw Communications, and if so, how?
GetHuman: And which of these common Shaw Communications customer issues best describes the reason you wanted to talk to them?
(Shows ~Shawsucks a list of common Shaw Communications problems)
~Shawsucks: "Overcharge/Strange charge" was why I was trying to call.
~Shawsucks's review of Shaw Communications customer service
GetHuman: So how would you sum up your experience for GetHuman's Shaw Communications 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.
~Shawsucks: Even after waiting over * hour, no common courtesy of saying sorry and simply unprofessional service. Just horrible. Switching to telus after an hour
GetHuman: Let's quantify your experience contacting Shaw Communications. On a scale of 1 to 5, how easy is it go get help on a Shaw Communications problem?
~Shawsucks: 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?
~Shawsucks: I'd give them a five out of five on communication.
GetHuman: And what about Shaw Communications's ability to quickly and effectively address your problem?
~Shawsucks: For that I would say five out of five.
GetHuman: And finally- any advice for other Shaw Communications customers?
~Shawsucks: Call them early in the day or late. Don't forget any personal or account information you might need for Shaw Communications to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Shawsucks taken from his Shaw Communications customer service problem that occurred on November 1st, 2017.