Bay Area Fastrak: poor notification of withdrawal of funds.*NO be...
A Bay Area Fastrak customer review by GetHuman user ~oresteskid from November 16th, 2017
Background on ~oresteskid's case
GetHuman: ~oresteskid - can you tell our other Bay Area Fastrak customers when your case took place?
~oresteskid: Yes I can. It was afternoon, on November 11th.
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 ~oresteskid a list of common Bay Area Fastrak problems)
~oresteskid: "Make a booking" was why I was trying to call.
~oresteskid'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.
~oresteskid: poor notification of withdrawal of funds.*NO benefit for seniors*handicap plackards, even after I was told they would honor that*keeping my funds without applying interest
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?
~oresteskid: I'd give them a two 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?
~oresteskid: I'd give them a three out of five on communication.
GetHuman: And what about Bay Area Fastrak's ability to quickly and effectively address your problem?
~oresteskid: For that I would say two out of five.
GetHuman: And finally- any advice for other Bay Area Fastrak customers?
~oresteskid: 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 ~oresteskid taken from his Bay Area Fastrak customer service problem that occurred on November 11th, 2017.