BP Chase Card Services: Could not understand agents. Went thru * differ...
A BP Chase Card Services customer review by GetHuman user ~taboo from November 5th, 2017
Background on ~taboo's case
GetHuman: ~taboo - can you tell our other BP Chase Card Services customers when your case took place?
~taboo: Yes. It was evening, on October 31st.
GetHuman: Did you reach out to BP Chase Card Services, and if so, how?
GetHuman: And which of these common BP Chase Card Services customer issues best describes the reason you wanted to talk to them?
(Shows ~taboo a list of common BP Chase Card Services problems)
~taboo: "Question" was why I was trying to contact.
~taboo's review of BP Chase Card Services customer service
GetHuman: So how would you sum up your experience for GetHuman's BP Chase Card Services 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.
~taboo: Could not understand agents. Went thru * different people with no luck resolving problem. Cut up card and will never use anything from bp*chase again.
GetHuman: Let's quantify your experience contacting BP Chase Card Services. On a scale of 1 to 5, how easy is it go get help on a BP Chase Card Services problem?
~taboo: I'd give them a four 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?
~taboo: I'd give them a five out of five on communication.
GetHuman: And what about BP Chase Card Services's ability to quickly and effectively address your problem?
~taboo: For that I would say two out of five.
GetHuman: And finally- any advice for other BP Chase Card Services customers?
~taboo: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for BP Chase Card Services to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~taboo taken from his BP Chase Card Services customer service problem that occurred on October 31st, 2017.