For a bank with many different ways to login, and a web application, mobile application and more, this isn't a simple task. There are many things that can go wrong. A well designed chatbot can troubleshoot the issue for a user step by step. If one of the paths fails or the problem is actually of a higher complexity, we just redirect the user to a real human.

Getting a regular non techinal user to search and read the documentation for this is just insane.

Yes, but how many buttons would you need to add?

Two buttons: 1.- Forgot password? 2.- Send

Forgot password, send password, change password, change contact info, check warranty status, estimate next release date, download product manual, how to replace the battery, does the license allow commercial use?, which product is better for an apartment?, I'm looking for more information about your upcoming event in Tulsa - or was it Toledo?

Sounds like your site has poor navigability. I would be irate if all those things weren't available.

The problem is how best to expose those and 100,000 other potential buttons to the user who has better things to do than "navigate".

An obvious solution is a search box, but most sites also have terrible search functionality, so users have learned to ignore it. For the rare gem that has useful search, dressing it up as a chatbot could get people to actually try it. Too bad it looks like a lot of devs are just dressing up their shitty search as chatbots, so users are being trained to ignore them as well.