What AWS announced
In its October 22, 2026 announcement, AWS introduced support for customizing the Customer Profiles app in the Amazon Connect agent workspace. Administrators can use Profile Explorer to choose which customer information agents see and how that information is arranged.
AWS describes Customer Profiles as providing a real-time, unified customer view that brings together contact history and customer data from multiple sources. This update changes how administrators present that information to agents: they can create and save layouts, then assign those layouts to agents in place of the legacy Customer Profiles view.
The announcement identifies several elements administrators can use:
- Contact history widgets.
- Contact information widgets.
- Calculated attributes, such as customer lifetime value.
- An optional AI Profile Summary that summarizes the customer profile and highlights key insights.
The central change is configurable presentation inside the agent workspace. The announcement does not establish new data-source integrations or provide pricing details.
Different work can have different views
AWS illustrates the feature with two airline workflows. A baggage claims agent could see contact history, active flights, and baggage ticket information. A loyalty agent could instead see loyalty status, customer preferences, and upcoming flights.
These examples show why layout customization matters: agents performing different tasks do not necessarily need the same information in the same order. Administrators can build views around those differences rather than relying on a single legacy presentation.
The AI Profile Summary is another available layout element. AWS says it can direct attention to important customer insights by summarizing the profile. The announcement does not describe accuracy guarantees or make the summary a substitute for reviewing underlying customer information.
Business impact: a workflow opportunity, not a savings promise
SaveAWS analysis: Task-focused layouts could reduce the effort agents spend finding relevant information. They may also make workspace design more consistent for teams that handle similar requests. These are potential operational benefits, not outcomes established by the announcement.
Results will depend on the quality of the customer data, the suitability of each layout, and how well agents understand the revised workspace. An arrangement that helps one team may omit context another team needs. Adding more widgets can also increase visual complexity rather than reduce it.
For cost-conscious organizations, this is best evaluated as a workflow improvement. AWS has not supplied a discount, a quantified productivity benefit, or a cost-reduction guarantee in this announcement. Any financial case should use measured operating results and verified applicable charges.
Where Profile Explorer is available
The announcement lists Profile Explorer availability in these AWS Regions:
- US East (N. Virginia)
- US West (Oregon)
- Africa (Cape Town)
- Asia Pacific (Seoul)
- Asia Pacific (Singapore)
- Asia Pacific (Sydney)
- Canada (Central)
- Europe (Frankfurt)
- Europe (London)
This is the availability qualifier stated for Profile Explorer in the source. Organizations should confirm their deployment Region before planning adoption rather than assume availability elsewhere.
Practical next steps
Start with one agent workflow where the required customer information is clear. Compare the current view with the information agents actually consult during interactions.
A practical evaluation plan is to:
- Map information needs. Ask agents and supervisors which fields are essential, frequently used, or distracting.
- Check data quality. Verify that the information selected for the layout is reliable enough to support the intended workflow.
- Build a focused layout. Create and save a layout in Profile Explorer, then assign it to a pilot group of agents.
- Review summaries carefully. If including AI Profile Summary, assess whether its output helps agents and remains consistent with underlying records.
- Measure the result. Compare navigation effort, handling time, quality reviews, and agent feedback before expanding adoption.
- Validate the economics. Check current AWS pricing and account usage rather than treating the feature announcement as evidence of lower costs.
Use the pilot to refine the layout before wider assignment. The goal is relevant information at the right point in the interaction, not simply a more crowded customer profile.
Official source
AWS announcement: Amazon Connect Customer now supports customizing the Customer Profiles app on the agent workspace, published October 22, 2026. AWS also directs readers to the Profile Explorer section of the Amazon Connect Customer administrator guide.
Official AWS source
Amazon Connect Customer now supports customizing the Customer Profiles app on the agent workspace ยท 2026-10-22