Instagram: I have been trying to log in but it won't let m...
A Instagram customer review by GetHuman user ~sarina740 from November 27th, 2017
Background on ~sarina740's case
GetHuman: ~sarina740 - can you tell our other Instagram customers when your case took place?
~sarina740: Sure. It was afternoon, on November 23rd.
GetHuman: Did you reach out to Instagram, and if so, how?
GetHuman: And which of these common Instagram customer issues best describes the reason you wanted to talk to them?
(Shows ~sarina740 a list of common Instagram problems)
~sarina740: "Recover account" was why I was trying to contact.
~sarina740's review of Instagram customer service
GetHuman: So how would you sum up your experience for GetHuman's Instagram 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.
~sarina740: I have been trying to log in but it won't let me because there is a connection error! ******** I know my connection is working because I ran an app that only can be used when there ulis WiFi! Please sort this out as it us the only way I can communicate with my friends from primary!!!
GetHuman: Let's quantify your experience contacting Instagram. On a scale of 1 to 5, how easy is it go get help on a Instagram problem?
~sarina740: 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?
~sarina740: I'd give them a one out of five on communication.
GetHuman: And what about Instagram's ability to quickly and effectively address your problem?
~sarina740: For that I would say two out of five.
GetHuman: And finally- any advice for other Instagram customers?
~sarina740: Call them early in the day or late. Don't forget any personal or account information you might need for Instagram to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~sarina740 taken from his Instagram customer service problem that occurred on November 23rd, 2017.