LastPass: This number is only for assistance with Lastpas...
A LastPass customer review by GetHuman user ~Pamelagio from November 27th, 2017
Background on ~Pamelagio's case
GetHuman: ~Pamelagio - can you tell our other LastPass customers when your case took place?
~Pamelagio: Yup. It was middle of the night, on November 25th.
GetHuman: Did you reach out to LastPass, and if so, how?
GetHuman: And which of these common LastPass customer issues best describes the reason you wanted to talk to them?
(Shows ~Pamelagio a list of common LastPass problems)
~Pamelagio: "Overcharge/Strange charge" was why I was trying to call.
~Pamelagio's review of LastPass customer service
GetHuman: So how would you sum up your experience for GetHuman's LastPass 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.
~Pamelagio: This number is only for assistance with Lastpass's identity theft monitoring. They only help they give for site support is to tell you to go to the site and submit a ticket, and this even upon telling them I am having so much trouble with the site that I can't even submit a ticket!
GetHuman: Let's quantify your experience contacting LastPass. On a scale of 1 to 5, how easy is it go get help on a LastPass problem?
~Pamelagio: 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?
~Pamelagio: I'd give them a one out of five on communication.
GetHuman: And what about LastPass's ability to quickly and effectively address your problem?
~Pamelagio: For that I would say one out of five.
GetHuman: And finally- any advice for other LastPass customers?
~Pamelagio: Call them early in the day or late. Don't forget any personal or account information you might need for LastPass to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Pamelagio taken from his LastPass customer service problem that occurred on November 25th, 2017.