Ikea: I called and was disconnected before ever reach...
A Ikea customer review by GetHuman user GetHuman-363764 from November 21st, 2017
Background on GetHuman-363764's case
GetHuman: GetHuman-363764 - can you tell our other Ikea customers when your case took place?
GetHuman-363764: Yes. It was afternoon, on November 18th.
GetHuman: Did you reach out to Ikea, and if so, how?
GetHuman: And which of these common Ikea customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-363764 a list of common Ikea problems)
GetHuman-363764: "Refunds and returns" was why I was trying to call.
GetHuman-363764's review of Ikea customer service
GetHuman: So how would you sum up your experience for GetHuman's Ikea 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-363764: I called and was disconnected before ever reaching a human at least * times. Once I finally got through to listen to elevator music I was on hold for ** minutes still never speaking to a human. After waiting on the phone for ** minutes on hold it hung up on me. Still can't reach a human.
GetHuman: Let's quantify your experience contacting Ikea. On a scale of 1 to 5, how easy is it go get help on a Ikea problem?
GetHuman-363764: 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-363764: I'd give them a four out of five on communication.
GetHuman: And what about Ikea's ability to quickly and effectively address your problem?
GetHuman-363764: For that I would say five out of five.
GetHuman: And finally- any advice for other Ikea customers?
GetHuman-363764: Call them early in the day or late. Don't forget any personal or account information you might need for Ikea to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-363764 taken from his Ikea customer service problem that occurred on November 18th, 2017.