Square: they kept my customer's money stating "high ris...
A Square customer review by GetHuman user ~FreeRenee from November 27th, 2017
Background on ~FreeRenee's case
GetHuman: ~FreeRenee - can you tell our other Square customers when your case took place?
~FreeRenee: Yeah. It was middle of the night, on November 25th.
GetHuman: Did you reach out to Square, and if so, how?
GetHuman: And which of these common Square customer issues best describes the reason you wanted to talk to them?
(Shows ~FreeRenee a list of common Square problems)
~FreeRenee: "Billing" was why I was trying to call.
~FreeRenee's review of Square customer service
GetHuman: So how would you sum up your experience for GetHuman's Square 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.
~FreeRenee: they kept my customer's money stating "high risk" after they verified all of my company information. They then closed my account and I cannot get through via phone. I have a travel agency. All of my transactions will be high! I've been with them for * months. Why was I subject to a "random" audit and then closed? Horrible.
GetHuman: Let's quantify your experience contacting Square. On a scale of 1 to 5, how easy is it go get help on a Square problem?
~FreeRenee: I'd give them a three 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?
~FreeRenee: I'd give them a two out of five on communication.
GetHuman: And what about Square's ability to quickly and effectively address your problem?
~FreeRenee: For that I would say one out of five.
GetHuman: And finally- any advice for other Square customers?
~FreeRenee: Call them early in the day or late. Don't forget any personal or account information you might need for Square to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~FreeRenee taken from his Square customer service problem that occurred on November 25th, 2017.