ENGINEERING PRACTICES
ChatOps
A collaboration model that connects people, tools, and scripts into a transparent workflow (usually Slack/Teams).
By Niketa Sharma, Founder at Runframe·Last updated Mar 2026
ChatOps
A collaboration model that connects people, tools, and scripts into a transparent workflow (usually Slack/Teams).
"Conversation-Driven Development"
ChatOps pushes all your ops tools into the chat room. Instead of opening a terminal to run deploy, you type /deploy in Slack.
Why do this?
- Visibility: Everyone sees that you just deployed. No more "Who is touching prod?".
- Onboarding: Juniors see exactly what commands Seniors are running.
- Mobile: You can fix incidents from your phone.
The Stack
- Chat Platform: Slack, Microsoft Teams.
- Bot: Hubot, Slack App.
- Infrastructure: AWS, Kubernetes, PagerDuty.
Common Commands
/page on-call(Pages the on-call person)./status(Shows system status)./incident create(Starts an incident and war room).
ExThe GitHub Way
“GitHub invented ChatOps. They deployed GitHub.com using a bot called Hubot for years.”
Impact
Developers deployed hundreds of times a day using chat commands.
Resolution
It created a culture of transparency and fearlessness around deployment.
Why ChatOps Matters
ChatOps brings incident management into the place where teams already work.
Running commands from chat (e.g., `/incident resolve`) ensures everyone sees what is happening in real-time.
Common Pitfalls
Notification Spam
If the bot posts every git commit to the main channel, people will mute it. Use threaded replies or specific channels.
How to Use ChatOps
🤖
Integrate Bots: Slackbot, PagerDuty bot.
📜
Audit Trail: Chat history becomes the incident log.
🚀
Run Actions: Deploy or rollback from chat.