All changes that you usually introduce, you simply push to everyone's server without much previous communication of possible impacts.

This isn't the ideal way of rolling out the features, since you do not have the full visibility if your change will break the website of one of your customers (yes, it happened several times with us).

So, I would suggest that you let the customers take control of their own websites, and enable the new features only if they want to. (You can even give an option for who wants to participate in your rollouts).

The last change that broke our website was the rollout of the new Firewall feature:

I had the "bot protection" disabled because my WP instance acts as a headless CMS, which means that my frontend (hosted in another provider) consumes /wp-json API from server-2-server. My frontend server does not have a static IP.

The new Firewall does not have an option to disable the "bot protection", which means that, out of the blue, my frontend server got marked as a malicious bot and was blocked from accessing my own CMS.

This is only 1 example of how your changes can affect the customers applications.

I strongly advise you to improve in this area, to ensure the customers can trust that their apps are stable and reliable, and will not stop working without them touching it.

Thanks in advance.