Tuesday, January 21, 2020

Kinda saw this coming...

... since Richmond had been warning us for oh, about 2 years.



I'll be complimenting one of my institutions (Chase) for NOT allowing this to happen. There are two or three ways to prevent this error message, all of which cost a bit of money. And the Info Tech people have to get it from some level of - you guessed it - MANAGEMENT and the managers at Chase, to my knowledge, understood the issue and I haven't seen this goofup at any of their ATMs. I don't actually know where this machine is, but it's at one of their competitors.

If I were Chase, I'd milk this for all it's worth, never letting the cheaper banks forget it. Hard to sweep this one under the rug.