"Rootly has been hugely beneficial. Our engineering team feels better prepared to deal with incidents. Before, it was a free-for-all with people throwing questions into Slack, hoping someone would answer. Now, it’s a very clean and sure process—when there’s an incident, you’re notified, you know who’s involved, the severity, what’s going on, and everything happens in one place."

George Dilthey

Head of Customer Support

Clay is about 50 people now. We just recently raised our series B funding about a month ago, and we’re mostly in person in New York City. We have a relatively relaxed policy, but everyone really likes being in the office.

Why did Clay need an incident management tool?

The pathway to adopting Rootly was actually kind of a funny one. I had used Rootly at a previous company, though I wasn't directly in charge of it.

When I joined Clay, Rootly reached out to see if we were interested in using the tool. Initially, our engineering team and I thought we were fine with just our Slack thread system. This worked until we experienced a few incidents, including one where our app went down, leading to four different Slack threads in separate channels. Information was getting lost, people's time was wasted jumping between threads, and updates were being missed.

It became clear we needed a more organized approach. From my past experience, I knew Rootly could solve these problems. That was when I decided it was time to implement Rootly, and within a few weeks, we started rolling it out.

What were you looking for in the incident management tool?

The biggest thing we needed was centralized communication, which is the core of what Rootly offers. Another major issue was our status page updates. It was unclear who was responsible for updating it, and it often fell through the cracks.