Display
Ecosystem
About five minutes of reading
If the object is not in S3, you do not have a recording, no matter what the flow block said.
Set the recording and analytics block on the contact, including outbound whisper flows if outbound must be recorded. The service role writes the WAV. The CTR carries the location. Screen recording is a separate decision and, on the Basic list, 0.006 USD per minute.
Tell people they are recorded if the law you operate under says so. The prompt is a block, not a policy PDF.
Number on this page: Proof S3. Plus Recording.Location on the CTR
Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.
Picture from this room.
What usually goes wrong: Recording only the inbound flow and wondering why outbound disputes have no audio.
Which term matches this description? The WAV Connect writes when recording is on. Third-party QM tools often import this object plus the CTR.
The WAV Connect writes when recording is on. Third-party QM tools often import this object plus the CTR. The term is S3 recording object.
Flow block in Connect Customer: Set recording and analytics behavior - Amazon Connect Customer AWS docs. last checked 2026-10
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? A flow that sets recording off 'for this queue' also kills the transcript.
A flow that sets recording off 'for this queue' also kills the transcript. The term is Configure conversational analytics and fix the empty transcript (1).
Connect Customer service quotas - Amazon Connect Customer AWS docs. last checked 2026-10
Flow block in Connect Customer: Set recording and analytics behavior - 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.
Recording only the inbound flow and wondering why outbound disputes have no audio.
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.