Sherlock Calls
for Amazon Connect + Cognigy
Amazon Connect routes customer contacts through AWS cloud infrastructure. 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 Amazon Connect, Cognigy simultaneously — read-only, no code changes, no webhooks — and lets you query both with a single Slack message.
- 2
Ask questions that neither Amazon Connect nor Cognigy can answer alone. Amazon Connect shows interaction volume — not its downstream business impact. 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 contact center + voice AI query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Amazon Connect + Cognigy without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Voice quality impact on contact center outcomes is unmeasured
Amazon Connect logs interaction outcomes and CSAT. Cognigy provides the voice experience. Whether a specific Cognigy configuration improves or degrades your Amazon Connect containment rate is a question that only a joint investigation can answer.
The true cost per AI-voiced interaction is invisible
Amazon Connect charges per interaction or seat. Cognigy charges per character synthesized. Your true cost per customer interaction served by AI voice spans both bills — but nobody's looking at them together.
Escalation root cause straddles two platforms
When a Cognigy agent escalates within Amazon Connect, both platforms log the event differently. Determining whether escalations stem from voice quality, script errors, or routing requires evidence from both sides.
Cross-Provider Questions
What teams ask Sherlock about Amazon Connect + Cognigy
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Cognigy voice configurations produce the best Amazon Connect CSAT and containment scores?”
- SC“What's the Amazon Connect escalation rate for calls handled by Cognigy vs human agents this week?”
- SC“Show me all Amazon Connect interactions where the Cognigy agent failed to contain the call”
- SC“What's our blended cost per interaction across Amazon Connect and Cognigy this month?”
- SC“Which Amazon Connect queues see the highest Cognigy AI containment rate?”
Beta Setup
Connect Amazon Connect + Cognigy to Sherlock in 2 minutes
No code, no webhooks, no new dashboards. Beta users get direct onboarding support.
- 1
Connect Amazon Connect
Add your Amazon Connect credentials to Sherlock Calls. Read-only access — no code changes, no webhooks, no Amazon Connect 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 Amazon Connect + 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 + Amazon Connect + Cognigy
How does Sherlock Calls connect Amazon Connect and Cognigy data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Amazon Connect, 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 Amazon Connect 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 Amazon Connect + Cognigy stack?
- You can investigate anything that spans both platforms — queue wait time and agent handle time, 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 Amazon Connect 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 Amazon Connect and Cognigy and is accessed only during an active investigation.
How long does it take to set up the Amazon Connect + 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 + Amazon Connect + Cognigy
We're accepting a select group of beta users to shape the Amazon Connect + Cognigy combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations