Centralized incident workflows have improved visibility and streamlined communication across teamsRootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle. The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira, for example, automating many steps in the follow-up process, which helps to centralize all communications around issues. The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area. The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises. It is not just a notification; we create a group where all the relevant people can help solve the issue quickly. The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira or manage the metrics we need during the incident lifecycle, effectively automating many manual processes. Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period. With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly. Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.
