Comcast: After * hours on hold and speaking to * differe...
A Comcast customer review by GetHuman user ~tired of the runaround from November 23rd, 2017
Background on ~tired of the runaround 's case
GetHuman: ~tired of the runaround - can you tell our other Comcast customers when your case took place?
~tired of the runaround : Yup. It was middle of the night, on November 15th.
GetHuman: Did you reach out to Comcast, and if so, how?
GetHuman: And which of these common Comcast customer issues best describes the reason you wanted to talk to them?
(Shows ~tired of the runaround a list of common Comcast problems)
~tired of the runaround : "Cancel Service" was why I was trying to call.
~tired of the runaround 's review of Comcast customer service
GetHuman: So how would you sum up your experience for GetHuman's Comcast 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.
~tired of the runaround : After * hours on hold and speaking to * different people the person at this number actually helped me try to resolve my issues.
GetHuman: Let's quantify your experience contacting Comcast. On a scale of 1 to 5, how easy is it go get help on a Comcast problem?
~tired of the runaround : 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?
~tired of the runaround : I'd give them a one out of five on communication.
GetHuman: And what about Comcast's ability to quickly and effectively address your problem?
~tired of the runaround : For that I would say five out of five.
GetHuman: And finally- any advice for other Comcast customers?
~tired of the runaround : Call them early in the day or late. Don't forget any personal or account information you might need for Comcast to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~tired of the runaround taken from his Comcast customer service problem that occurred on November 15th, 2017.