I submitted an FCC complaint.
A few days later, a customer service rep called me. She told me that I could contact the chatbot. I told her I'd never submit an FCC complaint if I could talk to a real person, because I don't trust the chatbot.
I submitted an FCC complaint.
A few days later, a customer service rep called me. She told me that I could contact the chatbot. I told her I'd never submit an FCC complaint if I could talk to a real person, because I don't trust the chatbot.
Can you elaborate on why you didn’t trust the chat it but would trust a human?
I’ve had human customer service members tell me things that I knew to be false. At least computers should be able to calculate confidence levels, like Watson was doing for Jeopardy a decade ago.
It's a horrible case for a chatbot. Basically, when you have a bunch of hopping mad customers, you don't want to rub salt in their wounds. Refusing to answer the phone in such a situation is horrible customer service.
Basically, if you refuse to answer the phone and stick out a chat bot, it looks like you're just hiding from your customers.
(This should be obvious if you've ever seen post mortems on customer service disasters, like the Intel Pentium bug.)
> Can you elaborate on why you didn’t trust the chat it but would trust a human?
Two reasons:
Basically, I don't know what kinds of integrations, or lack of, are in the system. So, for all I know, they could have something that just says, "don't worry, we're working on it," if it detects that my internet is offline. (IE, I don't know if anyone is actually working on it.)
No context: The system would only respond with a short, canned answer. First it said that everything was going to be fixed at 1:00, then a few hours after it kept saying "fixed soon."
(Again, this should be obvious if you've ever dealt with automations, or ever seen an error message.)
> So, for all I know, they could have something that just says, "don't worry, we're working on it," if it detects that my internet is offline. (IE, I don't know if anyone is actually working on it.)
Why would you trust this exact communication from a person over a computer?
That is the only reason why I call customer support in internet outages. I usually wait awhile before I call. (In this case, I called a few hours after their posted ETA.)
> Why would you trust this exact communication from a person over a computer?
This response in this thread explains it very well: https://news.ycombinator.com/item?id=36661196
> Conversely, a weasel worded chatbot could say "we are responding to outages as noted" or something similar, and that doesn't actually provide any evidence the utility is aware of the outage or its scope in the actual monitoring and management systems; your report of a failure could go straight to /dev/null.
Like I said, above, I called a few hours after their expected ETA. This is the situation where it's time to call a human who can call up the manager of a different department and say, "you said it was going to be done three hours ago, what's happening?"
It's basically a "Gall's Law" situation. The AI Chatbot is perfectly fine for a "normal" outage that's solved within the ETA; but once the published ETA has come and gone, we're in a corner case that's better handled by humans.
For a good explanation of this, see this recent article on Gall's Law that explains why it's better to let humans handle corner cases: https://bigthink.com/smart-skills/complex-project-galls-law/...
100% automated service, but as good if not better than anything I could get from a human.
Conversely, a weasel worded chatbot could say "we are responding to outages as noted" or something similar, and that doesn't actually provide any evidence the utility is aware of the outage or its scope in the actual monitoring and management systems; your report of a failure could go straight to /dev/null.