Bay Area Fastrak: We need replacement HOV stickers. We have to ph...
A Bay Area Fastrak customer review by GetHuman user ~nlbknitter from November 4th, 2017
Background on ~nlbknitter's case
GetHuman: ~nlbknitter - can you tell our other Bay Area Fastrak customers when your case took place?
~nlbknitter: Yup. It was evening, on November 1st.
GetHuman: Did you reach out to Bay Area Fastrak, and if so, how?
GetHuman: And which of these common Bay Area Fastrak customer issues best describes the reason you wanted to talk to them?
(Shows ~nlbknitter a list of common Bay Area Fastrak problems)
~nlbknitter: "Complaint" was why I was trying to call.
~nlbknitter's review of Bay Area Fastrak customer service
GetHuman: So how would you sum up your experience for GetHuman's Bay Area Fastrak 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.
~nlbknitter: We need replacement HOV stickers. We have to physically appear at the Fastrak office in SF to prove that we have registered a new Prius. Toll is $*, parking is $**. STUPID, STUPID STUPID!!!!
GetHuman: Let's quantify your experience contacting Bay Area Fastrak. On a scale of 1 to 5, how easy is it go get help on a Bay Area Fastrak problem?
~nlbknitter: 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?
~nlbknitter: I'd give them a two out of five on communication.
GetHuman: And what about Bay Area Fastrak's ability to quickly and effectively address your problem?
~nlbknitter: For that I would say five out of five.
GetHuman: And finally- any advice for other Bay Area Fastrak customers?
~nlbknitter: Call them early in the day or late. Don't forget any personal or account information you might need for Bay Area Fastrak to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~nlbknitter taken from his Bay Area Fastrak customer service problem that occurred on November 1st, 2017.