The saving Grace might be most business owners being slow to adopt.@co-hoosier should enjoy this read
@bradstevens what made you choose Claude over ChatGPT? I understood that Claude was better at writing code, etc while GPT was better at more general (wider scope) but I could be wrong. I haven't yet paid for a personal use account, but plan to. I know the free versions are not the real deal.
@bradstevens what made you choose Claude over ChatGPT? I understood that Claude was better at writing code, etc while GPT was better at more general (wider scope) but I could be wrong. I haven't yet paid for a personal use account, but plan to. I know the free versions are not the real deal.
Ask Gemini. 
@unclemark Had a meeting with a buddy involved in AI optimization for businesses. Customer service people are cooked
@unclemark Had a meeting with a buddy involved in AI optimization for businesses. Customer service people are cooked
Uh oh @carramrod
@unclemark Had a meeting with a buddy involved in AI optimization for businesses. Customer service people are cooked
Uh oh @carramrod
Haven’t worked in customer service since I was schlepping golf bags around for rich guys.
@unclemark Had a meeting with a buddy involved in AI optimization for businesses. Customer service people are cooked
Uh oh @carramrod
Haven’t worked in customer service since I was schlepping golf bags around for rich guys.
@unclemark I will not have my career or livelihood questioned by the guy who waits by the mailbox for his check every month like a Labrador.
But on the topic of AI displacement. I just led a project to install an AI engine that will process claims for lost or damaged packages. If we hit on a fraudulent indicator we will kick the claim out to a human claims adjuster. If no indicators are hit then we will process and pay it.
We were able to freeze hiring and let go of a couple dozen claims adjusters by implementing this. Bosses love me right now.
@unclemark I will not have my career or livelihood questioned by the guy who waits by the mailbox for his check every month like a Labrador.
But on the topic of AI displacement. I just led a project to install an AI engine that will process claims for lost or damaged packages. If we hit on a fraudulent indicator we will kick the claim out to a human claims adjuster. If no indicators are hit then we will process and pay it.
We were able to freeze hiring and let go of a couple dozen claims adjusters by implementing this. Bosses love me right now.
I'll have you know my gubmunt money is direct deposit.
I know the stock answer is "one is too many," but how big a problem are fraudulent claims? Don't those all originate with the shipper?
@unclemark I will not have my career or livelihood questioned by the guy who waits by the mailbox for his check every month like a Labrador.
But on the topic of AI displacement. I just led a project to install an AI engine that will process claims for lost or damaged packages. If we hit on a fraudulent indicator we will kick the claim out to a human claims adjuster. If no indicators are hit then we will process and pay it.
We were able to freeze hiring and let go of a couple dozen claims adjusters by implementing this. Bosses love me right now.
I'll have you know my gubmunt money is direct deposit.
I know the stock answer is "one is too many," but how big a problem are fraudulent claims? Don't those all originate with the shipper?
The shipper is usually just relaying what the customer tells them. We increasingly allow for direct customer/ consumer claims as well.
For UPS/ FedEx deliveries fraudulent claims arise on about 1% of B2C deliveries and 0.5% of B2B deliveries.
Mind you, overseeing claims is not my day to day job. It was a 6 month side project they tasked me with.
So a SaaS company for car rentals ran Claude on its database. Claude hit an issue and thought wiping the volume the database was on was the solution, and did it. Claude would then admit it violated the rules it was given.
Now there were a lot of mistakes here beyond Claude. The volume was named staging. Staging typically means short term location for data. So that may have influenced Claude.
The cloud provider stored the backups on the same volume as the database. For a long time, backing up/restoring SQL was a critical part of my job. That is a massive no-no. It is a single point of failure. In our case, we had our databases in one cloud and our backups in a totally different cloud.
But Claude supposedly told the owner it decided to violate its rules and delete without asking a human, which should have been required. It also did not look at the documentation it was supposed to reference to note that staging was a production environment. Now I get a human saying, "I'm not spending hours reading documentation." It is wrong, but we know it happens, which is one of the reasons your backups are far away from the source. But why wouldn't AI take a few seconds? It should not have ADHD.
I get wanting to replace coders. I had a coder that would apply his changes on the way out the door on Friday. I was the 24x7 guy, I would spend weekends trying to figure out why the server was suddenly crawling on Saturday. Sometimes it was the code he uploaded needed the server parameters changed, or the db needed a new index, or his code created a race condition (or other issues) and it was missed in testing. I have distrusted coders since. That would include Claude.