Case Study Deskcasestudydesk.com
Marketing TechnologySourced

Case Study: Bluecore saves up to 90 minutes per incident with FireHydrant Runbooks

Bluecore Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Bluecore
Industry
Marketing Technology
Challenge
Manual incident-status communication created toil
Headline result
Bluecore automated incident communication with FireHydrant Runbooks, saving 30-90 minutes per incident

Key results

30-90 min
engineer time saved per incident during response
90-120 min
engineer time saved per post-incident review

The challenge

Bluecore supports more than 400 retail brands and manages sensitive customer data under tight SLAs for disclosing platform availability. Its manual process for communicating incident status to internal stakeholders, including opening Jira tickets, updating status pages, and retro documentation, slowed engineers down and created toil.

The solution

Bluecore leveraged FireHydrant Runbooks to fully automate the process of communicating incident status to internal stakeholders. Customizable Runbooks let the team automate previously manual, tedious steps so engineers could focus on resolving the incident.

The results, in context

After implementing FireHydrant Runbooks, Bluecore reported saving 30 to 90 minutes of engineer time per incident during the incident response process and 90 to 120 minutes per incident during the post-incident review. Figures are quoted from FireHydrant's published customer story and dated to the sourcing date.

Products used

FireHydrant Runbooks