Looking past a lot of unnecessary verbiage, I think he's saying that everything that you might want a chatbot on your website to handle should instead be integr

Looking past a lot of unnecessary verbiage, I think he's saying that everything that you might want a chatbot on your website to handle should instead be integrated with ChatGPT (or its replacement) in the future. And that you should just have your web app, doing its thing, and not bolt on an isolated version of a chatbot that is only used for interacting with your specific site. The assumption is that people will want to talk to chatbots, just not your chatbot: they want a one-stop shop with every chatbot in the same app. I see the point, not sure I agree totally. I'm not someone who ever wants to talk to a chatbot, but sometimes I am forced to. I suppose that it is better in such cases to have a single place I go for that. On the other hand, if my confusion begins on your website, I would hope that your website would help me resolve it: if I have to go from yourwebapp.com, to a third party application, then type "how do I do X on yourwebapp.com?" that seems convoluted. Perhaps a browser-level integration, or at least replacing the proprietary chatbot with a doorway to that single, unified chatbot. Hmm, I dunno. Sounds like whoever runs such a chatbot would have their hands around the throat of the web, doesn't it?