SF Welcomes Me Home … Clipper, Not So Much
Photo by 0x0000org
1. Tara exits turnstiles at 24th and Mission BART station after a sleepy ride back from SFO. Clipper cash balance falls below threshold; Autoload triggered, just as it should.
2. On first commute back to work two days later, BART turnstiles say “see agent.” Agent shows, on his little machine thingie, a message that says, “BAD DEBT” (all caps, very scary). A customer-service call is in order. BART ticket must be purchased. (I am Tara’s boiling fit of not-really-contained public rage.)
3. Clipper Rep #1 says there’s nothing wrong with the account. Maybe the card itself is broken, she suggests? Add Fare machines couldn’t read it, so this seemed likely. (How much will it cost me if I don’t get a new card right away? Will I get a refund? I am Tara’s frustrated, tearful self-pity.)
4. Tara calls Clipper back to say, yes, something must be wrong with the card. Clipper Rep #2 checks into it further, and, at some point, mentions the last four digits of the credit card on file. This is an old card that does not exist! Ah: Clipper Rep #2 says this is why I have “bad debt,” triggered by the Autoload a couple days ago. But! It was updated! (Right? Hmm…)
5. Tara learns that she did, in fact, update her information in July. Tip: Always ALWAYS keep confirmation emails from Clipper when you update information; they contain reference numbers that should help if/when they don’t know what you’re talking about. She makes third call to Clipper that morning. (I am Tara’s violently flashing incompetency-radar.)
6. Clipper Rep #3 has no idea what Tara is talking about with this “bad debt” and “card not working” business. Everything looks fine, just as it did to Clipper Rep #1. No, no. Something is wrong. Look harder. Tara eventually gets the equivalent of, “Oh, there it is.” Info was updated correctly by the user, but it failed to be processed by Clipper.
