Victoria's Secret: Phone expierience was great, but through email...
A Victoria's Secret customer review by GetHuman user GetHuman-338320 from November 21st, 2017
Background on GetHuman-338320's case
GetHuman: GetHuman-338320 - can you tell our other Victoria's Secret customers when your case took place?
GetHuman-338320: Yes I can. It was morning, on November 19th.
GetHuman: Did you reach out to Victoria's Secret, and if so, how?
GetHuman: And which of these common Victoria's Secret customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-338320 a list of common Victoria's Secret problems)
GetHuman-338320: "Cancel or change order" was why I was trying to call.
GetHuman-338320's review of Victoria's Secret customer service
GetHuman: So how would you sum up your experience for GetHuman's Victoria's Secret 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-338320: Phone expierience was great, but through email it was exhausting as I got nothing solved in * months.
GetHuman: Let's quantify your experience contacting Victoria's Secret. On a scale of 1 to 5, how easy is it go get help on a Victoria's Secret problem?
GetHuman-338320: I'd give them a one 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-338320: I'd give them a one out of five on communication.
GetHuman: And what about Victoria's Secret's ability to quickly and effectively address your problem?
GetHuman-338320: For that I would say five out of five.
GetHuman: And finally- any advice for other Victoria's Secret customers?
GetHuman-338320: Call them early in the day or late. Don't forget any personal or account information you might need for Victoria's Secret to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-338320 taken from his Victoria's Secret customer service problem that occurred on November 19th, 2017.