Mozilla Firefox: I need to figure out why my multirow toolbar fo...
A Mozilla Firefox customer review by GetHuman user ~ldhkah from November 24th, 2017
Background on ~ldhkah's case
GetHuman: ~ldhkah - can you tell our other Mozilla Firefox customers when your case took place?
~ldhkah: Yup. It was middle of the night, on November 16th.
GetHuman: Did you reach out to Mozilla Firefox, and if so, how?
GetHuman: And which of these common Mozilla Firefox customer issues best describes the reason you wanted to talk to them?
(Shows ~ldhkah a list of common Mozilla Firefox problems)
~ldhkah: "Update account information" was why I was trying to contact.
~ldhkah's review of Mozilla Firefox customer service
GetHuman: So how would you sum up your experience for GetHuman's Mozilla Firefox 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.
~ldhkah: I need to figure out why my multirow toolbar for bookmarks is only * row now instead of *. I was told by my school to switch to IE. I imported all my bookmarks to IE from Firefox. Now the toolbars are gone.
GetHuman: Let's quantify your experience contacting Mozilla Firefox. On a scale of 1 to 5, how easy is it go get help on a Mozilla Firefox problem?
~ldhkah: 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?
~ldhkah: I'd give them a one out of five on communication.
GetHuman: And what about Mozilla Firefox's ability to quickly and effectively address your problem?
~ldhkah: For that I would say two out of five.
GetHuman: And finally- any advice for other Mozilla Firefox customers?
~ldhkah: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Mozilla Firefox to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~ldhkah taken from his Mozilla Firefox customer service problem that occurred on November 16th, 2017.