SquareTrade: Waited more than spoke to someone. The person...
A SquareTrade customer review by GetHuman user ~Had it 15 from November 26th, 2017
Background on ~Had it 15's case
GetHuman: ~Had it 15 - can you tell our other SquareTrade customers when your case took place?
~Had it 15: Sure. It was afternoon, on November 23rd.
GetHuman: Did you reach out to SquareTrade, and if so, how?
GetHuman: And which of these common SquareTrade customer issues best describes the reason you wanted to talk to them?
(Shows ~Had it 15 a list of common SquareTrade problems)
~Had it 15: "Issue with a claim" was why I was trying to call.
~Had it 15's review of SquareTrade customer service
GetHuman: So how would you sum up your experience for GetHuman's SquareTrade 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.
~Had it 15: Waited more than spoke to someone. The person I spoke to thought he was helping, but did not let me finish a sentence. Promised a call back in ** mins. Asked repeatedly if I could call because I would NOT be available in ** mins and he just didn't get it.
GetHuman: Let's quantify your experience contacting SquareTrade. On a scale of 1 to 5, how easy is it go get help on a SquareTrade problem?
~Had it 15: 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?
~Had it 15: I'd give them a five out of five on communication.
GetHuman: And what about SquareTrade's ability to quickly and effectively address your problem?
~Had it 15: For that I would say four out of five.
GetHuman: And finally- any advice for other SquareTrade customers?
~Had it 15: Call them early in the day or late. Don't forget any personal or account information you might need for SquareTrade to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Had it 15 taken from his SquareTrade customer service problem that occurred on November 23rd, 2017.