[ibejoeb]

I'm not familiar with Workflow Builder. Does it have a separate data retention scheme? Slack seems to have a big problem in that information quickly ages out, the search is pretty bad, and, in some cases, the data is actually ephemeral and will just disappear. Incident response is one of the categories that I want to preserve. Does Rootly address any of these problems?

OK, I see at the end of the demo that there is a chat transcript, so that's useful. Does it differentiate between incidents if there are multiple active incidents? Where is that archived stored?

[jjtang1]

Rootly would address that problem, we keep a database of all of your incidents and metadata (impact, timeline, participants, metrics, etc.) on our Web platform separate from Slack. You can customize a data retention policy with us if you want but it's helpful to be able to quickly search for similar incidents without trying to find it in Slack channels.

It does differentiate between incidents if there are multiple too. We'll even warn you if you're opening an incident and another one that could be related is also active to avoid duplications.

And of course we keep the garden walls low on the product. You can export any of this data out via CSV, JSON, API or via our integrations (Airtable, Google Sheets, Looker, etc.).

[derefr]

> information quickly ages out

Only on free plans. Corporations that have customers with SLAs that they're doing incident-response for probably aren't using Slack's free plan.

But even if they are, the data's also not actually purged from their systems. It's still in the Slack-workspace archive export, if/when you do one of those. They just hide it from you. Paying for a plan un-hides it.