
Sherlock Calls
Your AI call detective for Voice Operations — in Slack
Product Description
Debugging a failed voice AI call means bouncing between at least three platforms: Twilio for telephony events, ElevenLabs for TTS and audio behaviour, your webhook logs, and often a CRM to understand what happened to the contact. Each system has different timestamps, different call identifiers, and no awareness of the others. Most teams spend 2–3 hours per incident just reconstructing the sequence of events — before they can even start identifying the root cause.
Sherlock Calls connects to your voice stack via OAuth and turns that investigation into a Slack question. Ask "why did calls fail yesterday?" and get back a structured case file in the same thread: a correlated cross-provider timeline, the most likely root cause with supporting evidence, and first checks in triage order. No new dashboards. No code changes. The investigation lives where your team already communicates and works: Slack.
It also answers the less urgent questions that nobody has time to dig into manually: which campaign drove the most qualified calls this week, where latency is coming from across providers, how much a specific call cost across all connected services, whether ElevenLabs is having issues right now. All in plain English, directly in Slack.
Free tier: 100 credits per workspace, no credit card required. Connect in 60 seconds.




