[jjtang1]

Thank you!

You're not alone, I've ran into quite a few cases where working from a thread will suffice (big and small companies). We are still team dedicated incident channel but there are a few things that threads do better.

For example, the number of incident channels that get spun up can get out of hand. Threads are a lot cleaner for that. So we built a workflow that'll let you specify an auto archive behaviour.

We also don't want you to lose context of your threads or conversations, you can run /incident convert in Slack and we'll pull that context over. Lastly, we often see people working from threads from a primary #incidents or #outage channel for better visibility. We'll actually let you specify exactly who you want to notify whenever an incident gets opened/closed.

But generally we found we can do a lot more powerful things in dedicated channels around integrations or even assigning roles if that is important :)

Happy to chat more on your use case tho!

[renewiltord]

Great stuff. Good luck with your product. I imagine we'll need it later but for the moment, I think we're too small to be worth your time.

Would have loved to have run into you guys when/if you were looking for seed investment though

[jjtang1]

Appreciate the kind words and agree on fit.

Happy to compare notes and stay in touch if you'd like to connect of course [e-mail].