Sherlock Calls
for Aircall + Cognigy
Aircall logs your sales team's calls, tags, and recordings in real time. Cognigy automates contact center conversations at enterprise scale. When you need to investigate across both, the evidence is split between two dashboards neither of which knows the other exists. Sherlock Calls bridges them — no code, no exports, no manual joins. Ask once from Slack and get a sourced answer in under 5 seconds.
TL;DR — What beta users get access to
- 1
Sherlock Calls connects to Aircall, Cognigy simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither Aircall nor Cognigy can answer alone. Aircall shows call counts — not which calls are actually moving deals forward. Cognigy shows automation metrics — not their impact on CRM pipeline or revenue. Sherlock deduces the complete picture from both.
- 3
No dashboard switching, no manual joins, no fog of uncertainty — ask in Slack and receive a sourced answer with evidence from every connected provider in under 5 seconds. The game is afoot.
<5s
Answer to any telephony + voice AI query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Aircall + Cognigy without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
The root cause of call failures is split between Aircall and Cognigy
Aircall logs the SIP error. Cognigy logs the agent session. But was it a carrier issue, a Cognigy logic fault, or both? Without correlating both case files, your team eliminates the wrong suspects every time.
Your true cost per AI-handled call spans two invoices
Aircall bills for minutes and phone numbers. Cognigy bills for agent runtime. The actual cost of each completed AI conversation lives across both bills — and neither platform shows you the combined figure.
Human escalation patterns vanish at the handoff boundary
When a Cognigy agent transfers to a human via Aircall, that event is recorded in both systems with different identifiers. Tracking escalation rates across your AI fleet requires a manual join that nobody has time to do.
Cross-Provider Questions
What teams ask Sherlock about Aircall + Cognigy
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Cognigy agents have the highest Aircall call failure rate in the last 7 days?”
- SC“What's our blended cost per AI-handled call across Aircall and Cognigy this month?”
- SC“Show me all calls where a Cognigy agent transferred to a human via Aircall”
- SC“Which Aircall phone numbers produce the most successful Cognigy conversation completions?”
- SC“Compare average call duration for Cognigy-handled vs human-handled calls on our Aircall numbers”
Beta Setup
Connect Aircall + Cognigy to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect Aircall
Add your Aircall credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no Aircall configuration required.
- 2
Connect Cognigy
Add your Cognigy credentials. Sherlock indexes all contact center AI interaction logs and escalation records automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined Aircall + Cognigy stack in Slack. Sherlock queries all connected platforms in parallel, correlates the evidence, and returns a sourced answer in under 5 seconds.
FAQ
Common questions about Sherlock + Aircall + Cognigy
How does Sherlock Calls connect Aircall and Cognigy data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Aircall, Cognigy in parallel, correlates the results by timestamp and shared identifiers, and produces a single sourced answer — the same way a good detective correlates evidence from multiple witnesses.
Do I need to set up any data pipelines between Aircall and Cognigy?
- No. Sherlock Calls is entirely pull-based — it queries both APIs on demand when you ask a question. There are no webhooks, no ETL pipelines, no data warehouses, and no code changes required in any of the connected platforms.
What kinds of questions can I ask about my Aircall + Cognigy stack?
- You can investigate anything that spans both platforms — rep call activity and talk-time per deal, automation rate and escalation pattern, cross-platform costs, handoff patterns, and performance comparisons. Sherlock translates your plain-English question into the right API calls and returns the deduced answer.
Is my Aircall and Cognigy data stored by Sherlock?
- No. Sherlock Calls queries your data in real time and returns results directly to Slack — nothing is stored, indexed, or replicated in any Sherlock database. All data remains in Aircall and Cognigy and is accessed only during an active investigation.
How long does it take to set up the Aircall + Cognigy integration?
- Elementary — typically under 5 minutes total. Connect each platform with read-only credentials, install the Sherlock Calls Slack app, and ask your first question. No engineering, no dashboards, no onboarding calls required.
Apply for early access to Sherlock + Aircall + Cognigy
We're accepting a select group of beta users to shape the Aircall + Cognigy combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations