Instance Overview
Loading…
| Queue Name | Agents | Avg Wait | Status |
|---|
| Profile | Assigned Queues | Agents |
|---|
| Schedule | Hours | Timezone |
|---|
| Number | Type | Routes To | Status |
|---|---|---|---|
Call Flow Visualizer
Visual map of contact flows with routing path analysis
Routing Loop Detected
"Transfer to Billing" flow: option 3 (dispute) routes back to main menu, creating an infinite loop. 12 callers hit this last week, averaging 4 cycles before hanging up. Fix: add counter check after 2 transfers, route directly to live agent.
Dead End Found
"After Hours" flow: Spanish language branch doesn't connect to any queue or voicemail. Callers hear silence for 30 seconds then get disconnected. ~8 calls/week affected. Fix: connect to Spanish Support voicemail.
| Flow Name | Type | State | Description |
|---|---|---|---|
| Loading… | |||
Real-Time Metrics
Live performance data from your AWS Connect instance
Call Volume (Today by Hour)
847 total calls| Queue | In Queue | Wait Time | Agents | Trend |
|---|
Agent Performance
Real-time agent status and performance metrics
AI Diagnostics
Ask questions about your AWS Connect instance in plain English
Call History
Enriched call data via Amazon Connect Contact Lens — recordings, transcripts, sentiment, and summaries.
Connect Your Instance
Enter your AWS credentials to analyze your real AWS Connect data
Checking connection...
Loading credential status...
AWS Connect Configuration
We need read-only access to your AWS Connect instance. Credentials are encrypted with AES-256-GCM and never returned in API responses.
Recommended IAM Policy
Create a dedicated IAM user with read-only access. Attach the AmazonConnectReadOnlyAccess managed policy, or use this minimal custom policy:
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Action": [
"connect:DescribeInstance",
"connect:ListInstances",
"connect:ListQueues",
"connect:ListRoutingProfiles",
"connect:ListContactFlows",
"connect:ListHoursOfOperations",
"connect:ListUsers",
"connect:GetCurrentMetricData"
],
"Resource": "*"
}]
}
☁️ Salesforce Integration
Auto-push completed calls as Cases on matched Salesforce Accounts — with recording, transcript, summary, and sentiment attached.
Requires a Salesforce Connected App with OAuth 2.0 enabled.
Set SALESFORCE_CLIENT_ID and SALESFORCE_CLIENT_SECRET env vars.
Provision Demo Setup
Populate your test AWS Connect instance with realistic sample data — 4 queues, 3 routing profiles, 4 contact flows (including intentional routing bugs to diagnose), 2 hours-of-operation schedules, 5 sample agents, and ~75 historical contact records. Idempotent: safe to run multiple times.
connect:CreateQueue, connect:CreateRoutingProfile,
connect:CreateContactFlow, connect:CreateHoursOfOperation,
connect:CreateUser, connect:AssociateRoutingProfileQueues