Amazon Connect allows organizations to build completely customized Contact Control Panels (CCPs). Whether it's adding CRM integrations, internal dashboards, or custom workflows, many companies replace the default CCP with their own web application.
But there's one question I kept hearing:
Can we still use the native Amazon Q Agent Assistance experience inside a custom CCP?
The answer is yes.
In this article, I'll walk through the architecture and implementation approach we used to embed the AWS-managed Amazon Q experience directly into a custom Contact Control Panel without recreating any AI functionality ourselves.
The Challenge
Many organizations build a custom CCP to integrate:
- CRM systems
- Customer information
- Internal business tools
- Custom workflows
However, once you move away from the standard CCP, agents still expect access to Amazon Q Agent Assistance.
Rather than opening another browser tab or creating a separate application, we wanted Amazon Q to feel like part of the same workspace.
Solution Overview
Instead of rebuilding Amazon Q, we embedded the native AWS-managed Amazon Q interface alongside our custom CCP.
The custom application simply hosts both experiences while Amazon Connect continues to manage:
- Authentication
- Contact context
- Amazon Q Agent Assistance
This keeps the solution lightweight while allowing agents to access AI-powered assistance without leaving the customer interaction.
Architecture
The solution follows a simple architecture:
- Agents access the application through Amazon CloudFront.
- CloudFront serves a static web application hosted in Amazon S3.
- The application loads the custom Contact Control Panel (CCP) in the browser.
- The authenticated Amazon Connect session initializes the CCP.
- The same authenticated session loads the native Amazon Q experience.
- During supported customer interactions, Amazon Q retrieves relevant information from configured enterprise knowledge sources.
- Agents can seamlessly switch between the CCP and Amazon Q without leaving the application.
Key takeaway: The application never manages Amazon Q itself. It simply provides a place for the native AWS-managed experience to run.
Why This Approach?
Keeping Amazon Q as an AWS-managed component offers several advantages.
Minimal Custom Code
The application only initializes the Amazon Q experience instead of implementing AI features.
Native Experience
Agents receive the same interface and functionality available in the standard Amazon Connect experience.
Shared Authentication
No additional login flow is required because Amazon Q uses the existing authenticated Amazon Connect session.
Easier Maintenance
As Amazon Q receives new features and improvements, the application automatically benefits without requiring UI updates.
Implementation Highlights
The implementation was intentionally simple.
The custom CCP:
- Initializes the Amazon Connect CCP.
- Adds a dedicated Amazon Q tab.
- Creates a responsive container for Amazon Q.
- Uses environment-aware configuration to support multiple Amazon Connect instances.
- Maintains accessibility and responsive layouts for agents.
Because the application is a static web application, deployment is straightforward using Amazon S3 and Amazon CloudFront.
Security Considerations
Security remains largely unchanged from a standard Amazon Connect deployment.
Since authentication is handled by Amazon Connect:
- AWS credentials are never stored in the browser.
- Existing IAM permissions continue to apply.
- Approved application origins control where the CCP can be embedded.
- Amazon Q respects the permissions configured within Amazon Connect.
- Enterprise knowledge sources remain protected behind existing AWS security controls.
Benefits for Contact Center Agents
Embedding Amazon Q directly into the CCP provides several operational benefits:
- Faster access to enterprise knowledge during live interactions.
- Reduced context switching between applications.
- A consistent agent experience.
- Lower training effort.
- Improved productivity.
- Better first-contact resolution through quicker access to relevant information.
Lessons Learned
A few design decisions made the implementation much simpler.
Keep Amazon Q Native
Avoid recreating the interface or duplicating functionality already provided by AWS.
Separate Responsibilities
The CCP should manage customer interactions, while Amazon Q focuses on knowledge assistance.
Design for Multiple Environments
Supporting development, testing, and production becomes much easier with environment-aware configuration.
Prioritize Responsive Layouts
Agents often resize their browser windows, so both the CCP and Amazon Q should remain usable across different screen sizes.
Final Thoughts
One of the biggest advantages of Amazon Connect is its flexibility. You can build a fully customized Contact Control Panel without sacrificing native AWS capabilities like Amazon Q Agent Assistance.
By embedding the AWS-managed Amazon Q experience into a custom CCP, organizations can provide agents with AI-powered knowledge assistance while keeping the application lightweight, secure, and easy to maintain.
Rather than rebuilding AI features, let Amazon Q handle the intelligence while you focus on creating a seamless, productive agent experience.
If you're building custom experiences on top of Amazon Connect, I'd love to hear how you're extending your agent workspace. Feel free to share your thoughts or questions in the comments!
Top comments (0)