That's a naive perspective of the role Slack plays in many organizations.
For example, much of the monitoring and alerting workflows in our company run through Slack. We use it more than email. We can rollback production deployments with Slack commands as well as interact with our staging environments - and that's just the tip of the iceberg for the workflows we've built out with Slack's APIs.
Not every integration makes sense. I know some companies doing business logic automation in Google Docs, and I'm also reminded of Twitch Plays Pokemon. Just because you make a choice to integrate with a product doesn't mean it's widely adopted, practical, or wise.
Or supported.
Edit: I want to clarify. I don't mean to be rude, and I wasn't in the room when y'all made these decisions. I just don't think Slack is the ship you want to tie yourselves to, especially not as your control plane.
Sorry, but I have to post this now:
https://github.com/learnk8s/xlskubectl
"xlskubectl integrates Google Spreadsheet with Kubernetes."
"You can finally administer your cluster from the same spreadsheet that you use to track your expenses."
It's a (working) joke of course, but a hilarious one.
I would never want my production deployment rollback tied to my instant messenger plugin working.