Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by ceejayoz on Tuesday June 07, 2022 @10:24AM
(#31654804)
FireHydrant was my worst experience out of every incident manager I experimented with - literally nothing worked during our tests - and after two months of asking they're still refusing to remove our account; we still get a weekly email dashboard.
[ Parent
| on HN ]
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by btables on Tuesday June 07, 2022 @10:42AM
(#31655068)
Yikes! Never like seeing that. Can you email me directly and I will get this sorted? [email protected]
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by ceejayoz on Tuesday June 07, 2022 @10:49AM
(#31655186)
Tickets #1452, #1454, #1588. Was told "the account has been removed" on March 22nd, but I continue to receive "Last week on FireHydrant" emails specific to our org, most recently on May 29.
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by btables on Tuesday June 07, 2022 @11:03AM
(#31655413)
Thanks, emailed you as well. Sorry you ran into this!
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by kwent on Tuesday June 07, 2022 @10:41AM
(#31655045)
Sorry to hear that. I'll do my best to resist asking if you'd like to chat instead ;).
We try to take a very "partnership" centric approach. What that looks like day-to-day is our engineers/success/leadership team collaborating in a shared Slack Connect channel on new features. For a lot of our customers we get deep into the problem and bring in outside speakers from the industry to come do workshops, AMAs, etc. that might align well with the challenges.
This is the fun part about the job!
Re:Launch HN: Rootly (YC S21) – Manage Incidents in Slack
by macspoofing on Tuesday June 07, 2022 @01:24PM
(#31657494)
>Sorry to hear that. I'll do my best to resist asking if you'd like to chat instead ;).
Wow - you're looking for dirt on a company in the EXACT thread that calls out some shady things you've done against them.