British Telecom: Greg Downham *********. Fantastic engineer. Cou...
A British Telecom customer review by GetHuman user ~philly from November 7th, 2017
Background on ~philly's case
GetHuman: ~philly - can you tell our other British Telecom customers when your case took place?
~philly: Yes. It was middle of the night, on November 5th.
GetHuman: Did you reach out to British Telecom, and if so, how?
GetHuman: And which of these common British Telecom customer issues best describes the reason you wanted to talk to them?
(Shows ~philly a list of common British Telecom problems)
~philly: "None of those really matches why I wanted to call British Telecom that day." was why I was trying to call.
~philly's review of British Telecom customer service
GetHuman: So how would you sum up your experience for GetHuman's British Telecom 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.
~philly: Greg Downham *********. Fantastic engineer. Couldn't have asked for better. Polite, friendly, imformative and fixed the problem in no time. A pleasure to deal with! Thanks again
GetHuman: Let's quantify your experience contacting British Telecom. On a scale of 1 to 5, how easy is it go get help on a British Telecom problem?
~philly: 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?
~philly: I'd give them a five out of five on communication.
GetHuman: And what about British Telecom's ability to quickly and effectively address your problem?
~philly: For that I would say five out of five.
GetHuman: And finally- any advice for other British Telecom customers?
~philly: Call them early in the day or late. Don't forget any personal or account information you might need for British Telecom to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~philly taken from his British Telecom customer service problem that occurred on November 5th, 2017.