Thunderbird: have not received email for two days
A Thunderbird customer review by GetHuman user GetHuman-nelsene from December 8th, 2017
Background on GetHuman-nelsene's case
GetHuman: GetHuman-nelsene - can you tell our other Thunderbird customers when your case took place?
GetHuman-nelsene: Yes. It was middle of the night, on December 1st.
GetHuman: Did you reach out to Thunderbird, and if so, how?
GetHuman: And which of these common Thunderbird customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-nelsene a list of common Thunderbird problems)
GetHuman-nelsene: "Cancel service" was why I was trying to contact.
GetHuman-nelsene's review of Thunderbird customer service
GetHuman: So how would you sum up your experience for GetHuman's Thunderbird 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.
GetHuman-nelsene: have not received email for two days
GetHuman: Can you tell the rest of us a bit more from what happened on 12/01/17?
GetHuman-nelsene: have not received email for two days
GetHuman: Let's quantify your experience contacting Thunderbird. On a scale of 1 to 5, how easy is it go get help on a Thunderbird problem?
GetHuman-nelsene: I'd give them a one 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?
GetHuman-nelsene: I'd give them a one out of five on communication.
GetHuman: And what about Thunderbird's ability to quickly and effectively address your problem?
GetHuman-nelsene: For that I would say one out of five.
GetHuman: And finally- any advice for other Thunderbird customers?
GetHuman-nelsene: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Thunderbird to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-nelsene taken from his Thunderbird customer service problem that occurred on December 1st, 2017.