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