Browser Notification Warnings in Amazon Connect CCP logs - Does it affect call quality or audio in Amazon Connect?
This article addresses a common misconception observed during customer audio quality troubleshooting: the CCP log warning "The user has requested to not receive notifications" being flagged as a potential cause of static noise. The purpose is to clarify that this warning has zero impact on audio quality, preventing engineers from wasting time on a red herring during call quality investigations.
Browser Notification Warnings in Amazon Connect CCP — What They Mean and Don't Mean
Question
What does the CCP log warning "The user has requested to not receive notifications" mean? Does it affect call quality or audio in Amazon Connect?
Short Answer
No. This warning has zero impact on audio quality, call connectivity, or CCP functionality. It simply means the agent's browser has not granted the CCP permission to show desktop notification pop-ups. It does not affect WebRTC audio streams, packet handling, or any call-related functionality.
Detailed Resolution
What the Warning Means
When you see this in CCP logs:
ccp WARN The user has requested to not receive notifications.
This indicates that the browser's Notification API permission is set to "denied" or "default" (not granted) for the CCP domain. The CCP attempted to show a desktop notification and the browser blocked it.
What Browser Notifications Do
Browser notifications are desktop pop-up alerts that appear outside the browser window. In the CCP context, they're used for:
- Alerting agents to incoming calls when the browser tab is not in focus
- Showing missed contact notifications
That's it. They are a convenience feature for multitasking agents.
What Browser Notifications Do NOT Affect
- WebRTC audio streams (media flows independently of the Notification API)
- Packet loss or jitter
- Call quality (static, robotic sound, one-way audio)
- Call connectivity or session establishment
- CCP functionality (answer, hold, transfer, disconnect all work normally)
- Call recording
- Contact flow execution
Why This Gets Confused with Audio Issues
When troubleshooting audio quality problems, engineers review CCP logs looking for anything abnormal. This warning appears frequently (since many agents don't enable notifications) and can be mistakenly correlated with audio issues simply because it's present in the logs during problematic calls. It's a coincidence — the warning is always there for agents who haven't enabled notifications.
Should Agents Enable Notifications?
It's optional and depends on workflow:
- Enable if: Agents multitask across browser tabs and need to be alerted to incoming contacts without watching the CCP tab.
- Don't bother if: Agents keep the CCP/Salesforce tab in focus during their shift.
- To enable: Click the lock icon in Chrome's address bar → Site settings → Notifications → Allow.
Key Takeaway
If you're investigating audio quality issues and see this warning in CCP logs, skip it and look elsewhere. Focus on:
- WebRTC metrics (packet loss, jitter, round-trip time)
- Network connectivity (endpoint test results)
- Audio device configuration
- Integration layer issues (if using embedded CCP in Salesforce or other platforms)
Resources
- Language
- English
Relevant content
- asked 3 years ago
