Metlife Dental: Tried all kinds of numbers. Never made it throu...
A Metlife Dental customer review by GetHuman user GetHuman-294898 from November 9th, 2017
Background on GetHuman-294898's case
GetHuman: GetHuman-294898 - can you tell our other Metlife Dental customers when your case took place?
GetHuman-294898: Yup. It was middle of the night, on November 2nd.
GetHuman: Did you reach out to Metlife Dental, and if so, how?
GetHuman: And which of these common Metlife Dental customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-294898 a list of common Metlife Dental problems)
GetHuman-294898: "Make A Claim" was why I was trying to call.
GetHuman-294898's review of Metlife Dental customer service
GetHuman: So how would you sum up your experience for GetHuman's Metlife Dental 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.
GetHuman-294898: Tried all kinds of numbers. Never made it through. I have a simple question and it's not part of the menu options. Dialing "*" didn't work either.
GetHuman: Let's quantify your experience contacting Metlife Dental. On a scale of 1 to 5, how easy is it go get help on a Metlife Dental problem?
GetHuman-294898: 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?
GetHuman-294898: I'd give them a five out of five on communication.
GetHuman: And what about Metlife Dental's ability to quickly and effectively address your problem?
GetHuman-294898: For that I would say two out of five.
GetHuman: And finally- any advice for other Metlife Dental customers?
GetHuman-294898: Call them early in the day or late. Don't forget any personal or account information you might need for Metlife Dental to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-294898 taken from his Metlife Dental customer service problem that occurred on November 2nd, 2017.