Yes, and the technology to improve the interface you described is already available to run hundreds of concurrent instances on a 1U server. The barrier to entry is getting the people who manage those systems to care enough to implement something better.

Fact. My company's largest partner is CoreWeave, and convincing leadership that we could run it ourselves on partner discounted hardware for a lot less money has gone nowhere.

Maybe you need to walk into the office with a $1000 server running a hundred instances of whatever your code does.

We got rid of all our offices, whole company is remote now.

> Most of that industry is still at "press 1 for sales, 2 for billing..." and needs something that will run locally on a 1U server.

Needs? Customers want something that immediately answers their question/solves their problem, but that’s far away, even ignoring the “run locally on a 1U server” and that that may not be in the company’s interest.

For many companies, that support line is a cost center, not a PR mechanism.

Also “Press 1 for sales, 2 for billing...” has the big advantage that it handles all accents, speech impediments, etc.

Long term I think a solution where a user’s agent trained on their voice, running on their phone communicates with the support agent of a company is where we will end up, and support phone lines will cease to exist.