Display
Ecosystem
About five minutes of reading
If you cannot point at the box that owns a function, you will build it twice.
The center is the contact. Around it: telephony, flows, routing, the CCP, profiles and cases, conversational analytics, WFM, recording, the CRM, E911, and agent assist. Lines are keys, not vibes: ContactId, profile id, agent event, civic address, S3 object.
Click a node in the lab. The panel says what you configure, what breaks, and which hook a future system should use.
Number on this page: Center Contact. Everything else references it
Picture from this room.
What usually goes wrong: A diagram that is only logos.
Which term matches this description? The key that ties the flow log, the CTR, the recording, the agent event, and the CRM activity. Lose it and the ecosystem cannot be audited.
The key that ties the flow log, the CTR, the recording, the agent event, and the CRM activity. Lose it and the ecosystem cannot be audited. The term is ContactId join.
Integrate Amazon Connect with Amazon Kinesis | AWS re:Post community. last checked 2026-10
Which term matches this description? The test number that reads back the originating number and the address. Use it instead of a real 911 test. A non-emergency 911 call is described as a 100 USD penalty.
The test number that reads back the originating number and the address. Use it instead of a real 911 test. A non-emergency 911 call is described as a 100 USD penalty. The term is 933.
Set up US emergency calling in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? The contact attribute that carries the E911 address as a JSON string. Keys include country, A1, A3, HNO, RD, STS, and PC.
The contact attribute that carries the E911 address as a JSON string. Keys include country, A1, A3, HNO, RD, STS, and PC. The term is CivicAddress.
Format a physical address for E911 to pass to Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
Connect Customer agent event streams - Amazon Connect Customer AWS docs. last checked 2026-10
The prose is a study paraphrase. The link is the source of the facts.
Connect answers the contact. Workforce, quality, emergency location, and the system of record sit beside it, and they only stay honest if they share ContactId.
A diagram that is only logos.
Adherence needs agent events, not a person refreshing a report. ResourceType AGENT_EVENTS and StorageType KINESIS_STREAM is the hook. A second consumer should read the stream, not a second delivery on the instance.
Resources:
AgentEvents:
Type: AWS::Connect::InstanceStorageConfig
Properties:
InstanceArn: !GetAtt CampusInstance.Arn
ResourceType: AGENT_EVENTS
StorageType: KINESIS_STREAM
KinesisStreamConfig:
StreamArn: !GetAtt AgentStream.Arn
Join records on ContactId. The integration map room lists the seams.
A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.
Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.