Sherlock Calls
for Amazon Connect + Datadog
Amazon Connect routes customer contacts through AWS cloud infrastructure. Datadog monitors every layer of your infrastructure with metrics and traces. 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, Datadog 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 Datadog can answer alone. Amazon Connect shows interaction volume — not its downstream business impact. Datadog shows infrastructure events — not how they map to call failures or customer impact. 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 + observability query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Amazon Connect + Datadog without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Infrastructure incidents degrade contact center quality invisibly
A Datadog infrastructure event can manifest as elevated handle times, dropped calls, or IVR failures in Amazon Connect. Without correlating both, your contact center team diagnoses symptoms while engineering sees metrics — neither sees the full picture.
Contact center SLA depends on infrastructure health you don't track together
Your Amazon Connect SLA is partly a function of Datadog uptime. But when Amazon Connect SLAs breach, the root cause investigation starts in the wrong place if Datadog data isn't on the same timeline.
Post-incident analysis misses the infrastructure trigger
After a Amazon Connect quality incident, the Datadog event that caused it is rarely part of the post-mortem. The two teams work from different timelines — and the same degradation recurs next quarter.
Cross-Provider Questions
What teams ask Sherlock about Amazon Connect + Datadog
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Did any Datadog infrastructure events correlate with Amazon Connect interaction quality degradation yesterday?”
- SC“Show me all Amazon Connect interactions with elevated handle time during Datadog alert windows”
- SC“What's the Amazon Connect CSAT trend during periods of Datadog service degradation this month?”
- SC“Which Datadog services most frequently precede Amazon Connect contact center performance dips?”
- SC“Give me a joint timeline of Amazon Connect SLA breaches and Datadog incidents for the last 7 days”
Beta Setup
Connect Amazon Connect + Datadog 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 Datadog
Add your Datadog credentials. Sherlock indexes all infrastructure metrics, APM traces, logs, and alert events automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined Amazon Connect + Datadog 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 + Datadog
How does Sherlock Calls connect Amazon Connect and Datadog data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Amazon Connect, Datadog 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 Datadog?
- 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 + Datadog stack?
- You can investigate anything that spans both platforms — queue wait time and agent handle time, alert rate, latency, and service health, 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 Datadog 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 Datadog and is accessed only during an active investigation.
How long does it take to set up the Amazon Connect + Datadog 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 + Datadog
We're accepting a select group of beta users to shape the Amazon Connect + Datadog combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations