Baltimore Gas and Electric: Getting help at BGE depends on the customer ser...
A Baltimore Gas and Electric customer review by GetHuman user ~j6z3 from October 24th, 2017
Background on ~j6z3's case
GetHuman: ~j6z3 - can you tell our other Baltimore Gas and Electric customers when your case took place?
~j6z3: Yup. It was afternoon, on October 21st.
GetHuman: Did you reach out to Baltimore Gas and Electric, and if so, how?
GetHuman: And which of these common Baltimore Gas and Electric customer issues best describes the reason you wanted to talk to them?
(Shows ~j6z3 a list of common Baltimore Gas and Electric problems)
~j6z3: "Change appointment" was why I was trying to call.
~j6z3's review of Baltimore Gas and Electric customer service
GetHuman: So how would you sum up your experience for GetHuman's Baltimore Gas and Electric 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.
~j6z3: Getting help at BGE depends on the customer service rep you are connect with* some are excellent while most ****.
GetHuman: Let's quantify your experience contacting Baltimore Gas and Electric. On a scale of 1 to 5, how easy is it go get help on a Baltimore Gas and Electric problem?
~j6z3: I'd give them a five 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?
~j6z3: I'd give them a two out of five on communication.
GetHuman: And what about Baltimore Gas and Electric's ability to quickly and effectively address your problem?
~j6z3: For that I would say five out of five.
GetHuman: And finally- any advice for other Baltimore Gas and Electric customers?
~j6z3: Call them early in the day or late. Don't forget any personal or account information you might need for Baltimore Gas and Electric to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~j6z3 taken from his Baltimore Gas and Electric customer service problem that occurred on October 21st, 2017.