David's Bridal: Rated * of * on both measures because I could n...
A David's Bridal customer review by GetHuman user ~jennytto from November 23rd, 2017
Background on ~jennytto's case
GetHuman: ~jennytto - can you tell our other David's Bridal customers when your case took place?
~jennytto: Sure. It was morning, on November 21st.
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 ~jennytto a list of common David's Bridal problems)
~jennytto: "Cancel order" was why I was trying to call.
~jennytto'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.
~jennytto: Rated * of * on both measures because I could not get through to anyone.**As previously stated by another reviewer, customer service is non existent (online) and it is impossible to get in touch with anyone if you have any questions.
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?
~jennytto: 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?
~jennytto: I'd give them a one out of five on communication.
GetHuman: And what about David's Bridal's ability to quickly and effectively address your problem?
~jennytto: For that I would say four out of five.
GetHuman: And finally- any advice for other David's Bridal customers?
~jennytto: 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 ~jennytto taken from his David's Bridal customer service problem that occurred on November 21st, 2017.