This is true of automated IT processes in general; for human-operated processes there's always a certain amount of "slack" between how the process is written and what needs to be done to make it actually work. The knowledge for the latter is concentrated in lower-ranking staff - the "NCOs" - and often unknown and unknowable to those running the system. Converting the system to automation only converts the known process, so it tends to fail hard until the slack can be taken up elsewhere or learned and incorporated.
The next layer of automation would involve people going through one of those call menus; ideally once the customer ends up at an agent, they will have all their data and files right in front of them already.
> algorithm costs $100k to run
I almost choked on my coffee. They used this line on multiple companies??
For those that need further explanation, HAL is the killer computer in the movie 2001, the name was picked for the movie because the letters are shifted by one from "IBM." IBM's product Watson is named after Sherlock Holmes's sidekick, Dr. Watson.
Edit: the product was named after a prominent, early CEO of IBM, not the character; Sherlock Holmes & Dr. Watson is what the commenter was referencing (I've thought the Watson name was a Holmes reference since it won Jeopardy).
Actually, the IBM/HAL thing is just a coincidence, according to both Kubrick and Clarke: https://en.wikipedia.org/wiki/HAL_9000#Origin_of_name
HAL is just IBM encypted using Caesar cipher / ROT25 :)
Holmes must be Watson (but "Holmes" is also the marketing name given by another tech vendor in this space to their own AI product inspired by Watson - very creative)
I had issues with this too. The only solution is to prep your CIO whenever you play hardball, and return the favor to the vendor.
They just had to be real...
So first issue: developing measures that measure real overall service productivity... this is hard, the gaming is intense.
Second issue: automation generates work. Yup. When your service workers get time they use it to address difficult cases and to do the work that removes regulatory and safety risks. The rest of the time this stuff is ignored, building hidden risk for the enterprise. Relieve the pressure, and it reemerges.
Third issue: peak demands. Ideally automation would help you deal with peak demands enabling human staffing at sensible levels to handle most of the traffic most of the time. Sadly it doesn't. Peak demand often seemed to be for the work that could least be automated.
Forth issue: the tech is a castle of lies. Ok, that's not quite true... but there is a lot of lying. In the academic work the lying is of the form of what is left out of the experiments and evaluations - for example that the algorithm cost $100k to run or something. In the commercial world there is flat out lying - HAL I look at you, you bastard. How many RFI's were derailed by some regional President at a supplier ringing my CIO or CEO and explaining that I was "a problem" and had "an attitude"... well, all of them. The issue is that there is no sanction. HAL is still pushing Holmes and winning contracts, and not delivering what they promise, because it's all a lie. All that happens is that they move to the next sucker and wait for management churn at the old sucker to erase the corporate memory, and this does not take long. In reality they should all be drummed out of the business and no one should ever speak to them again.
But, five years later I am still flogging my guts out and they are all on their boats and golf courses. One of the bastards had his own vineyard.
So, sigh