The Evidence Room
Free debugging instruments, extracted from Sherlock's core investigation engine. Each one solves a single problem — instantly, in the browser, without an account.
“It is a capital mistake to theorise before one has data.” — These tools give you data.
Error Decoder
“Elementary, my dear developer.”
Paste any Twilio or ElevenLabs error — JSON payload, raw error code, or log snippet. Get the root cause, a plain-English explanation, and the first three fix steps in under ten seconds.
Why it exists
Decoding provider error codes at 11pm shouldn't require archaeology across five documentation tabs.
Who it's for
Any developer staring at a failed call log in production.
Latency Calculator
“The game is afoot — and the clock is ticking.”
Select your ElevenLabs model, voice type, and Twilio region. Get a p50/p95 latency estimate, a visual breakdown of every millisecond in the pipeline, and a warning if your silence timeout will drop calls before your agent speaks.
Why it exists
Most teams only discover their latency problem when callers start hanging up. This tells you before that happens.
Who it's for
Voice AI engineers configuring new deployments or debugging mysterious short-duration call drops.
Call Cost Calculator
“Every failed call leaves a financial trace.”
Enter your monthly call volume, average duration, Twilio rate, and ElevenLabs plan. See your true monthly cost — including exactly how much you are spending on calls that fail before delivering any value to the caller.
Why it exists
Twilio bills for failed calls too. Most teams have never calculated how much their failure rate is actually costing them per month.
Who it's for
Founders, CTOs, and ops leads doing voice AI unit economics for the first time — or the tenth.
Webhook Inspector
“A webhook payload is a crime scene. Every field is evidence.”
Paste any Twilio or ElevenLabs webhook JSON. Get the event type decoded in plain English, a table of every key field with its meaning, specific follow-up actions for this exact event, and where it sits in the Twilio → ElevenLabs → CRM chain.
Why it exists
Webhook payloads are dense, under-documented in context, and you only see them when something is already broken.
Who it's for
Developers debugging webhook delivery failures or building a new voice AI integration from scratch.
The full investigation
These tools show you one clue at a time.
Sherlock sees the whole case.
Connect your Twilio and ElevenLabs accounts once. Every time a call fails, Sherlock correlates the evidence across providers, reconstructs the timeline, identifies the root cause, and posts the complete case file directly in Slack — before you even know something went wrong.
Add Sherlock to Slack — free, 100 credits →No credit card. Connects in 2 minutes.
Also in the evidence room: Error Code Directory — autopsy pages for all 21 common Twilio, ElevenLabs, and Vapi errors.