It support · Production

Rootly saves months of engineering time building AI incident management with Recall.ai

The problem

Rootly needed a meeting bot that could pull live call data from multiple video platforms (Teams, Zoom, Webex) into its incident management platform, but building this in-house would have consumed many months of engineering time — time better spent on AI features for customers.

Workflow diagram · grounded in source

Incident triggers video call

trigger

“Collaboration during incidents most commonly occurs through a video call. When things are wrong, when your website is broken, it's 3AM, everyone is panicking, people tend to jump on a call and try to figure out what is going on”

Bot joins call across platforms

integration

“we've effectively built a bot that joins together your calls on any platform, whether that is Teams, Zoom, or Webex, and it serves as a scribe that we run our own AI features on top of”

AI processes call transcriptions

ai_action

“Recall.ai to rapidly process and analyze call transcriptions across meeting apps at scale”

Engineer queries for status

trigger

“you can just @rootly inside Slack, and say, 'What is going on? What did Amanda try?'”

AI generates catch-up answer

output

“All of those questions can be answered with a combination of the context occurring in the call, but also inside of your Slack or Teams conversations”

Reported outcome

Using the Recall.ai API, two Rootly engineers stood up the core product functions in just two days, saving many months of engineering work and enabling the team to focus on AI-driven incident response features for customers.

Reported metrics

Time to stand up core product functionstwo days

engineering time saved (estimated without Recall.ai)many months

Build time avoidedintegrate within days instead of spending quarters

Reported stack

Recall.aiSlackTeamsZoomWebex

Source

https://www.recall.ai/customers/rootly

Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

Using the Recall.ai API, two Rootly engineers stood up the core product functions in just two days, saving many months of engineering work and enabling the team to focus on AI-driven incident response features for cus…

What tools did this team use?

Recall.ai, Slack, Teams, Zoom, Webex.

What results were reported?

Time to stand up core product functions: two days; engineering time saved (estimated without Recall.ai): many months; Build time avoided: integrate within days instead of spending quarters (source-reported, not independently verified).

How is this it support AI workflow structured?

Incident triggers video call → Bot joins call across platforms → AI processes call transcriptions → Engineer queries for status → AI generates catch-up answer.