Blackberry: I have been trying for * weeks to get BB to res...
A Blackberry customer review by GetHuman user GetHuman-105547 from November 25th, 2017
Background on GetHuman-105547's case
GetHuman: GetHuman-105547 - can you tell our other Blackberry customers when your case took place?
GetHuman-105547: Yeah. It was afternoon, on November 19th.
GetHuman: Did you reach out to Blackberry, and if so, how?
GetHuman: And which of these common Blackberry customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-105547 a list of common Blackberry problems)
GetHuman-105547: "Where to buy" was why I was trying to call.
GetHuman-105547's review of Blackberry customer service
GetHuman: So how would you sum up your experience for GetHuman's Blackberry 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-105547: I have been trying for * weeks to get BB to respond to my order that was never shipped. I get the same response, "I will write a ticket" No one ever follows up!!! I paid for a phone that was never shipped to me.
GetHuman: Let's quantify your experience contacting Blackberry. On a scale of 1 to 5, how easy is it go get help on a Blackberry problem?
GetHuman-105547: I'd give them a four 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-105547: I'd give them a one out of five on communication.
GetHuman: And what about Blackberry's ability to quickly and effectively address your problem?
GetHuman-105547: For that I would say two out of five.
GetHuman: And finally- any advice for other Blackberry customers?
GetHuman-105547: Call them early in the day or late. Don't forget any personal or account information you might need for Blackberry to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-105547 taken from his Blackberry customer service problem that occurred on November 19th, 2017.