Sherlock Calls
for Amazon Connect + ClickHouse
Amazon Connect routes customer contacts through AWS cloud infrastructure. ClickHouse stores and queries high-volume event and operational data at 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, ClickHouse 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 ClickHouse can answer alone. Amazon Connect shows interaction volume — not its downstream business impact. ClickHouse holds the raw source of truth — but querying it for business questions requires SQL access and data engineering resources. 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 + database query
2
Connected platforms, 1 Slack question
0
Code changes or webhooks required
The Investigation Gap
What's invisible when you use Amazon Connect + ClickHouse without Sherlock
Each platform shows you its own data. But the questions that matter most live in the gaps between them.
Amazon Connect interaction outcomes are disconnected from ClickHouse application state
Amazon Connect logs what happened in the contact center. ClickHouse holds the application records the customer was calling about. Whether the Amazon Connect interaction resolved the ClickHouse issue — and updated the right record — is a question neither platform can answer alone.
ClickHouse application errors generate Amazon Connect contact volume that goes unattributed
When ClickHouse has a data error or an edge case that produces a bad customer experience, the resulting Amazon Connect contact volume is logged without the ClickHouse root cause. Engineering and operations work from different timelines on the same underlying problem.
Post-interaction Amazon Connect QA has no ClickHouse business impact context
Amazon Connect measures handle time, CSAT, and resolution rate. ClickHouse holds the downstream business outcome — did the ClickHouse record get updated correctly, did the customer actually churn? Without joining both, QA optimises the conversation, not the business result.
Cross-Provider Questions
What teams ask Sherlock about Amazon Connect + ClickHouse
Questions that would take hours to answer manually — answered in under 5 seconds from Slack.
- SC“Which Amazon Connect interaction topics correlate with specific ClickHouse application state changes?”
- SC“Show me Amazon Connect contact volume spikes and the ClickHouse events that triggered them”
- SC“Which ClickHouse records are most frequently referenced in Amazon Connect interactions this week?”
- SC“Find customers with high Amazon Connect contact frequency and their corresponding ClickHouse account status”
- SC“What ClickHouse application errors are generating the most Amazon Connect support interactions?”
Beta Setup
Connect Amazon Connect + ClickHouse 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 ClickHouse
Add your ClickHouse credentials. Sherlock indexes all event tables, query logs, operational records, and analytical datasets automatically.
- 3
Ask your first cross-provider question. The game is afoot.
Type any question about your combined Amazon Connect + ClickHouse 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 + ClickHouse
How does Sherlock Calls connect Amazon Connect and ClickHouse data?
- Sherlock uses read-only API access to both platforms simultaneously. When you ask a question, it queries Amazon Connect, ClickHouse 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 ClickHouse?
- 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 + ClickHouse stack?
- You can investigate anything that spans both platforms — queue wait time and agent handle time, query volume and event ingestion rate, 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 ClickHouse 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 ClickHouse and is accessed only during an active investigation.
How long does it take to set up the Amazon Connect + ClickHouse 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 + ClickHouse
We're accepting a select group of beta users to shape the Amazon Connect + ClickHouse combination. Tell us about your stack and we'll reach out personally if you're a fit.
Explore individual integrations