John Hancock: good response time, horrible service. language...
A John Hancock customer review by GetHuman user ~anonymous from November 27th, 2017
Background on ~anonymous's case
GetHuman: ~anonymous - can you tell our other John Hancock customers when your case took place?
~anonymous: Yup. It was evening, on November 17th.
GetHuman: Did you reach out to John Hancock, and if so, how?
GetHuman: And which of these common John Hancock customer issues best describes the reason you wanted to talk to them?
(Shows ~anonymous a list of common John Hancock problems)
~anonymous: "Get financial advice" was why I was trying to call.
~anonymous's review of John Hancock customer service
GetHuman: So how would you sum up your experience for GetHuman's John Hancock 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.
~anonymous: good response time, horrible service. language barrier, seems like reading from script. keeped switching me back and forth to departments. felt like I was talking to someone who knew nothing in investments. will switch compaanies
GetHuman: Let's quantify your experience contacting John Hancock. On a scale of 1 to 5, how easy is it go get help on a John Hancock problem?
~anonymous: I'd give them a five 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?
~anonymous: I'd give them a four out of five on communication.
GetHuman: And what about John Hancock's ability to quickly and effectively address your problem?
~anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other John Hancock customers?
~anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for John Hancock to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anonymous taken from his John Hancock customer service problem that occurred on November 17th, 2017.