Profiles are the customer, not the contact

About five minutes of reading

The contact ends. The profile is how the next contact knows who called.

Customer Profiles stores the customer and the objects you attach. Connect-only profiles are priced at 0 USD per daily use in the appendix. The moment you merge imported CRM data, daily use of that profile is 0.005 USD, with extra charges past each 100 objects, and a cap described in the appendix.

The flow block can get, create, and update a profile. Identity resolution decides when two records are one person. Get that rule wrong and agents see two half-customers.

• Keys on an object type default to 10.
• A profile object maxes at 250 KB in the quota table. All objects on one profile share a larger cap.
• Calculated attributes and event triggers have their own quotas.
• E911 addresses for agents are stored here on purpose. That is a different profile population from customers. Do not mix the matching rules carelessly.

Number on this page: Imported profile $0.005. Per profile, per day it is used

Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.

Picture from this room.

1. Key. Choose a stable id.
2. Get or create. In the flow.
3. Merge. Identity rules.
4. Show. In the workspace.

What usually goes wrong: Using the phone number as the only key when customers share a household line.

Amazon Connect Customer Pricing Appendix - AWS AWS docs. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Glossary

• Customer Profiles The profile store. Connect-generated profiles are priced differently from profiles that contain imported data.
• Identity resolution The rules that merge profile records from CRM, orders, and contacts into one customer.
• Case A durable issue that can span many contacts. Cases became generally available on 3 Oct 2022.
• Task A unit of work with no live media. Default concurrent quota is 2500. Tasks can be scheduled up to 90 days ahead.

Mind map

Open the Profiles, cases, tasks mind map

Sister technologies

A contact ends. A case, a task, and a profile are how the next person continues it.

Config and troubleshooting

Using the phone number as the only key when customers share a household line.

Profiles and cases use their own IAM prefixes. This template only shows the Connect instance those services attach to. Create the profile domain and the Cases domain in the same Region.

CfnInstance Customer Profiles

Resources:
  CampusInstance:
    Type: AWS::Connect::Instance
    Properties:
      IdentityManagementType: SAML
      InstanceAlias: campus-demo
      Attributes:
        InboundCalls: true
        OutboundCalls: true
        ContactflowLogs: true

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

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.

Open the mapping room

Future hooks

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.