Metlife Dental: MetLife uses careful attention to ensure that y...
A Metlife Dental customer review by GetHuman user ~dirigible from November 5th, 2017
Background on ~dirigible's case
GetHuman: ~dirigible - can you tell our other Metlife Dental customers when your case took place?
~dirigible: Sure. It was afternoon, on October 29th.
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 ~dirigible a list of common Metlife Dental problems)
~dirigible: "Make A Claim" was why I was trying to call.
~dirigible'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.
~dirigible: MetLife uses careful attention to ensure that you never get to speak ato them. Unable to access claims information online for days and even weeks at a time, but spend way too much time just to see if they know about it.
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?
~dirigible: 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?
~dirigible: I'd give them a three out of five on communication.
GetHuman: And what about Metlife Dental's ability to quickly and effectively address your problem?
~dirigible: For that I would say two out of five.
GetHuman: And finally- any advice for other Metlife Dental customers?
~dirigible: 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 ~dirigible taken from his Metlife Dental customer service problem that occurred on October 29th, 2017.