David's Bridal: I had a very small issue to resolve and the wai...
A David's Bridal customer review by GetHuman user GetHuman-343313 from November 26th, 2017
Background on GetHuman-343313's case
GetHuman: GetHuman-343313 - can you tell our other David's Bridal customers when your case took place?
GetHuman-343313: Yup. It was afternoon, on November 20th.
GetHuman: Did you reach out to David's Bridal, and if so, how?
GetHuman: And which of these common David's Bridal customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-343313 a list of common David's Bridal problems)
GetHuman-343313: "Make a purchase" was why I was trying to call.
GetHuman-343313's review of David's Bridal customer service
GetHuman: So how would you sum up your experience for GetHuman's David's Bridal 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-343313: I had a very small issue to resolve and the wait was outrageous. I was polite and informed them of how long I had been waiting and they blew me off. Not very happy.
GetHuman: Let's quantify your experience contacting David's Bridal. On a scale of 1 to 5, how easy is it go get help on a David's Bridal problem?
GetHuman-343313: 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?
GetHuman-343313: I'd give them a five out of five on communication.
GetHuman: And what about David's Bridal's ability to quickly and effectively address your problem?
GetHuman-343313: For that I would say one out of five.
GetHuman: And finally- any advice for other David's Bridal customers?
GetHuman-343313: Call them early in the day or late. Don't forget any personal or account information you might need for David's Bridal to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-343313 taken from his David's Bridal customer service problem that occurred on November 20th, 2017.