Atlasphones.com: Had a question about installing a Cisco IP tele...
A Atlasphones.com customer review by GetHuman user ~TelephoneDoc from November 22nd, 2017
Background on ~TelephoneDoc's case
GetHuman: ~TelephoneDoc - can you tell our other Atlasphones.com customers when your case took place?
~TelephoneDoc: Yes. It was afternoon, on November 12th.
GetHuman: Did you reach out to Atlasphones.com, and if so, how?
GetHuman: And which of these common Atlasphones.com customer issues best describes the reason you wanted to talk to them?
(Shows ~TelephoneDoc a list of common Atlasphones.com problems)
~TelephoneDoc: "Overcharge/Strange charge" was why I was trying to call.
~TelephoneDoc's review of Atlasphones.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Atlasphones.com 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.
~TelephoneDoc: Had a question about installing a Cisco IP telephone set I had purchased from a atlasphones.com. Salesperson answered all my questions immediately.
GetHuman: Let's quantify your experience contacting Atlasphones.com. On a scale of 1 to 5, how easy is it go get help on a Atlasphones.com problem?
~TelephoneDoc: 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?
~TelephoneDoc: I'd give them a one out of five on communication.
GetHuman: And what about Atlasphones.com's ability to quickly and effectively address your problem?
~TelephoneDoc: For that I would say three out of five.
GetHuman: And finally- any advice for other Atlasphones.com customers?
~TelephoneDoc: Call them early in the day or late. Don't forget any personal or account information you might need for Atlasphones.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~TelephoneDoc taken from his Atlasphones.com customer service problem that occurred on November 12th, 2017.